Re: [Wrapper-user] JBoss and Wrapper

[Leif M. <le...@ta...>]

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
>