|
From: Oliver N. <1b...@we...> - 2007-05-06 07:31:01
|
Hey Leif, thanks for the reply. >Did you copy the values from the web page or did you follow the steps to generate a file for the exact > version of JBoss you are using? The later is required. well i just changed the wrapper.conf according to: http://wrapper.tanukisoftware.org/doc/english/integrate-simple-win.html my original jboss.run bat starts this: ""c:\programme\java\jdk1.6.0"\bin\java" -Dprogram.name=run.bat -server -Xms 128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=c:\Programme\jboss-4.0.5.GA\bin\\..\lib\endorsed" -cla sspath ""c:\pr ogramme\java\jdk1.6.0"\lib\tools.jar;c:\Programme\jboss-4.0.5.GA\bin\\run.ja r" org.jboss.Main I changed my jboss.conf to this here but without result: wrapper.java.additional.1=-server wrapper.java.additional.2=-Xms128m wrapper.java.additional.3=-Xmx512m wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000 wrapper.java.additional.5=-Dsun.rmi.dgc.client.gcInterval=3600000 wrapper.java.additional.6=-Dprogram.name=run.bat wrapper.java.additional.7=-Djava.endorsed.dirs=%JBOSS_HOME%\bin\\..\lib\endo rsed My client still throws this: javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.0.2; nested exception is: java.net.ConnectException: Connection timed out: connect] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at ejb.session.MP3SessionUtil.lookupHome(MP3SessionUtil.java:22) ... The JMX-console is able to get reached from the very same remote machine as well as the deployed web-components. Thanks for the help, oliver ----- Original Message ----- From: "Leif Mortenson" <le...@ta...> To: <wra...@li...> Sent: Sunday, May 06, 2007 3:02 AM Subject: Re: [Wrapper-user] JBoss and Wrapper > Oliver, > There shouldn't be any reason why the Wrapper itself would be > affecting this. > How did you generate the wrapper.conf file? Did you copy the values > from the > web page or did you follow the steps to generate a file for the exact > version > of JBoss you are using? The later is required. > Another possible mistake is that you are not using the correct > version of java > when running as a service. > Try setting the wrapper.java.command.loglevel=INFO property and make > sure that the correct value of JAVA_HOME is being used. Also compare the > resulting command line to that of the original JBoss batch file. > > Cheers, > Leif > > beast wrote: > > Hey, > > > > im using the Java Service Wrapper 3.2.3 on a Windows Server 2003-Machine to > > setup a service for my JBoss Application Server 4.0.5GA. > > The Appserver and my ejb-apps run very fine when i start the jboss normally > > via run.bat (not by starting the service). When i start the service the > > appserver starts normally as well (checked by the log-files) but my remote > > clients are unable to connect to the deployed sessionbeans. The jboss itself > > stays unchanged, so i guess its nothing within jboss. The weird thing is, > > that the remote clients doesnt even catch up an exception - they just doing > > something without popping out any log or exception on the point of > > connecting to the server. The very same tools work well without starting > > jboss by the service. > > > > Does anybody got an idea what may be wrong here ? > > > > > > Any help would be appreciated... > > thanks, > > oliver > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |