|
From: Leif M. <le...@ta...> - 2005-08-12 16:28:14
|
Anil,
The Wrapper process reads the wrapper.conf file long before the JVM
is ever
launched. The integration method that you use will have no effect on
that. What
is the problem you are seeing. If you could post your wrapper.conf as well
as the wrapper.log output for a SINGLE JVM invocation with
wrapper.debug=true
set in the wrapper.conf file, then I should be able to tell you what
problem you
are having.
The most common mistake that users make when using Integration
method 3 is
that their WrapperListener.start method is not returning. As described
in the
javadocs for that method, it is critical that that method return in a timely
manner.
Cheers,
Leif
Anil N. Juthani wrote:
>Hi,
>I have been running the 1st method successfully for quite some time.
>However, I am currently trying to use the 3rd integration method and it
>seems to be causing major issues. I implement the WrapperListener in the
>main class and call the WrapperManager.start(), which eventually starts
>everything. However, it seems that it does not read the wrapper.conf file in
>this case. No matter what changes I make to the wrapper.conf file, the
>application starts fine. It is as if the WrapperManager.start() does not
>look for the wrapper.conf file at all.
>I would appreciate if someone could help me out soon.
>Thanks,
>---Anil
>
>
>-------------------------------------------------------
>SF.Net email is Sponsored by the Better Software Conference & EXPO September
>19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|