When I rebuilt the web service in the EJBModule, I added the new web
service, but I did not remove the original web service - so, the
"interrupting idle thread.." remained.
I now removed the original web service and redeployed and ran. The
process in the EJBModule has now run for an hour without error. We will
see how this test runs over nite. Tomorrow, I will test further.
It appears that one should not expect web services built on a v2 project
in netbeans to run in a project that has been switched over to v3.
From: Martin, Ray
Sent: Monday, August 30, 2010 6:08 PM
To: users_at_glassfish.dev.java.net
Subject: RE: Interrupted idle thread
I rebuilt the web service in the EJBModule.
I rebuilt the web service client.
I cleaned up the database - got most of the errors out.
Reran glassfish v3.
Got the stupid "interrupting idle thread.." nonsense. Can't find any
information anywhere about this.
Database is totally frits'd - I hate V3!!!!
From: Martin, Ray
Sent: Monday, August 30, 2010 3:38 PM
To: users_at_glassfish.dev.java.net
Subject: Interrupted idle thread
Using glassfish build 74.2 and jdk1.6.0_20
Have one EJBModule using webservice and JPA deployed in a enterprise
app.
Had running very well in v2.
Changed to v3.
Get a "Warning: Interrupting idle Thread: http-threa-pool-8080-(x)"
where x appears to be a one up number.
On startup a SOAP message is sent one time to the EJBModule. The
EJBModule performs some processing and sends a response SOAP message.
In v2, the process could run for minutes, hours, or days without
failure.
In v3, after the warning message, something ( I am pretty sure that it
is not the web service client - because it is instrumented) causes a
SOAP messages and the processing starts over and corrupts my databases.
I don't know what to do.
Any help would be appreciated.
Thanx.