Mr. Lubke,
I did the following:
...
<http request-timeout-seconds="-1" ...
...
I assume that -1 means to disable.
After restarting glassfish and deploying the EJBModule in an Enterprise
app (so it will see the third party jars) - still got the "interrupting
idle thread.."
But, worse than that is the fact that something causes the SOAP message
to be repeated - then my process is not protected against that repeat
SOAP message again kicks off and stomps all over the database records
that it just wrote before the timeout.
I am going to try an asynchronous client to see if that will take care
of the problem.
Thanx for your help.
-----Original Message-----
From: Ryan Lubke [mailto:ryan.lubke_at_oracle.com]
Sent: Monday, August 30, 2010 8:51 PM
To: Martin, Ray
Cc: users_at_glassfish.dev.java.net
Subject: RE: Interrupted idle thread
Hello Martin,
I believe you'll be able to resolve this issue by either increasing the
request-timeout-seconds property or disabling
the feature altogether.
This can be done by backing up your
GF_HOME/domains/domain1/config/domain.xml and then modify the http
element
associated with the protocol your listener is using.
For example, if you're using the out-of-the-box configuration, you can
change the timeout for requests made to port 8080 like
so:
<protocol name="http-listener-1">
<http request-timeout-seconds="60" default-virtual-server="server"
max-connections="250" />
</protocol>
It doesn't appear that this value can currently be set to -1 via asadmin
command line, so I'll be looking into resolving
that shortly.
Could you please try updating the domain.xml using the above xml snippet
as a guide and let us know if it resolves your problem?
Thanks,
-rl