PDA

View Full Version : 1.6 RC2 problem



nicoace
09-10-2007, 03:49 PM
Hi, I have downloaded pci 1.6 RC2 (mysql) and I can not acces to the server from another computer.
I can only acces from localhost, I have changed web.xml file but it does not work. In RC1 it works.

Any ideas??

Axel
09-11-2007, 10:27 AM
C'est la politique de sécurité par défault de JBoss 4.2.
Il faut le lancer avec l'option -b 0.0.0.0 pour qu'il soit accessible depuis n'importe quelle adresse.

Le plus simple c'est de transformer le start-pentaho.sh de ceci:


cd jboss/bin
sh run.sh
à cela:


cd jboss/bin
sh run.sh -b 0.0.0.0
Vu le nombre d'utilisateur qui vont être confrontés à ce problème, je pense qu'il faudrai que ça apparaisse quelque part sur le Wiki (à moins que ça y soit déjà).

nicoace
09-11-2007, 11:03 AM
Thanks it works!!

For the people that don't understando French (like me :confused:)

Google translated:

It is the policy of safety by default of JBoss 4.2.
It should be launched with the option - B 0.0.0.0 so that it is accessible since any address.

The simplest is to transform the start-pentaho.sh to
cd jboss/bin
sh run.sh -b 0.0.0.0

Considering the number of user which will be confronted with this problem, I think that it will be necessary that that appears some share on Wiki (unless that is there already).

Axel
09-11-2007, 11:45 AM
Oops, I didn't realized that I was writing my post in french.
Sorry.

mlowery
09-12-2007, 10:18 AM
Good find! I've documented this in BISERVER-318 (http://jira.pentaho.org/browse/BISERVER-318).

bugg_tb
09-25-2007, 04:43 AM
Yeah thanks for that, saved a few hours troubleshooting :)

fflex
09-25-2007, 11:48 PM
Do we need to add parameters to stop-pentaho.sh?

When I run 1.6RC2-820 "./stop-pentaho.sh" (on lLinux 2.6.9-5.ELsmp) , I get the following exceptions:


java.sql.SQLException: socket creation error
java.sql.SQLException: socket creation error
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
... 5 more
java.sql.SQLException: socket creation error

bugg_tb
10-25-2007, 04:51 AM
I've just downloaded 1.6GA and the problem still seems to persist? Was it no amended to a reason or just a slight oversight?


Cheers

Tom

mlowery
10-25-2007, 09:34 AM
It was an oversight. The Deployment Configuration (http://wiki.pentaho.org/display/PentahoDoc/Deployment+Configuration) documentation has been updated. Thank you for pointing this out.