Re: [Wrapper-user] Wrapper stopped after startup

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

Elias,
Can you answer a few questions?

1) You have said that it fails when run as a service, but that it
works from the command line.   Have you tried running under the
Wrapper in console mode?  Ie by running as follows: wrapper.exe -c
..¥conf¥wrapper.conf
What happens?

2) Please post the java command line you are using when it works, and
the one generated by the Wrapper.  You can get the command line
generated by the Wrapper by running in debug mode or by setting
wrapper.java.command.loglevel=INFO

2) Have you seen the FAQ entry on this subject?
http://wrapper.tanukisoftware.org/doc/english/faq.html#4
The win32com.dll needs to be on your java library path.  By default,
Java searches the PATH, but when running under the Wrapper, this is
disabled because a library path is specified.  It is necessary to add
the location of win32com.dll to your library path in the wrapper.conf
file.

Cheers,
Leif

2009/3/20 Elías Manchón López <eli...@gm...>:
> Hi Leif,
>
> The problem was the creation of instance of the class wrap by
> WrapperListener. Now I haven't problem with the start of Service. But it's
> not work yet. I think that the problem is very difficult of resolve.
> Although my level of English not is very good, I will try to explain the
> better possible for if you can help me.
>
> My application is made with Spring Framework. This application use Jetty
> embedded to publish it through 8080 port and use the remote feature of
> Spring to the web server can do request to it. This application is
> communicated with my ERP throught COM+ and translate the request of web
> server to my ERP using JACOB
> (http://sourceforge.net/projects/jacob-project/).
>
> When I use Java Service Wrapper, I can see that I have problems with the
> Initialization of COM Object, and I get NullPointer to object instantiated
> with JACOB. I thought that problem was by permission on the COM of
> Microsoft, but I checked this issue and there isn't problems. As well as, If
> I run my application throught command line, with the same command that Java
> Service Wrapper and using the same jar packet, the curious is that it works
> fine.
>
> I don't know to think, I don't know if it is problem of COM+ or If it is
> problem of Java Service Wrapper?. Could you give me some indication?.
>
> Thanks again!!.
> 2009/3/18 Leif Mortenson <lei...@ta...>
>>
>> Elias,
>> What does the content of your WrapperListener.start method look like?
>>
>> If you create a new thread, it will be non-daemon unless you
>> specifically call the thread.setDaemon(true) method.  If you are using
>> existing class to start your application then it will be more
>> difficult to check.   One solution is to add a wait for 1 second at
>> the end of your start method then call
>> WrapperManager.requestThreadDump().  That will let you see all of your
>> threads as well as see easily which have their daemon flag set.
>>
>> Cheers,
>> Leif

(snip)