Thanks Chris, I'll have a look at that now...but my thread-pool-1 has a max of 500 connections, and the loop only runs once before it errors, so I'd be surprised if I was running out of connections...but I'll do jstack and have a look.
Interestingly, last night I ran the following code which starts with a one minute sleep and continues to increment the sleep by one minute each time:
System.out.println("running test");
for(int i = 0; i < 45; i++){
System.out.println("run " + i);
InitialContext remoteContext = RemoteContextLookup.lookup();
String opsJndi = "ejb/UnsecuredOperationsBean";
System.out.println("looking up ops");
UnsecuredOperationsRemote ops = (UnsecuredOperationsRemote)remoteContext.lookup(opsJndi);
System.out.println("executing method");
System.out.println("Response: " + ops.isReadyForReportGeneration(30000l));
System.out.println("finsihed run " + i);
remoteContext.close();
long sleepTime = i * 60 * 1000;
System.out.println("Sleeping for " + i + " minutes");
Thread.sleep(sleepTime);
}
System.out.println("Finished test");
Again, exactly at a 20 minute sleep I got an error, but this time it said "Connection forcibly closed by remote host".
I'll keep investigating today, however it seems very strongly tied to 20 minutes sleep time (which coincidentally is the repeat delay I'm using for the timer thread). I'm going to drop my timer thread down to a 10 minute schedule and see if that solves the problem. It seems as long as I maintain a continuous (at least once every 19 minutes) link to the ejb server it's fine, which is odd, because non of my settings on the ejb server (pool or cache timeouts or anything like that) are set to 20 minutes that I can see anyway.
--- On Wed, 24/6/09, glassfish@javadesktop.org <glassfish@javadesktop.org> wrote:
> From: glassfish@javadesktop.org <glassfish@javadesktop.org>
> Subject: Re: Urgent - EJB SSB Timeouts!
> To: users@glassfish.dev.java.net
> Received: Wednesday, 24 June, 2009, 10:22 PM
> > by the way, I think whatever's
> happening is happening
> > on the ejb server not the client, as I just tried to
> > run the command line program below again and it
> > didn't even get through the first loop, so JNDI on
> > that server seems to have locked up
>
> Hi,
>
> seems to reflect my assumption that maybe the ORB has no
> more connections/threads. I looked again at the domain.xml
> and saw that the default orb listener uses thread-pool-1
> which has the maximum thread number of 200. Maybe you can do
> a jstack on the PID of the Glassfish and check if there are
> a large number of suspicious threads. As a start you could
> look for lines containing "thread-pool-1", e.g. "p:
> thread-pool-1; w: 2" daemon prio=10 tid=0x0844d400
> nid=0x3516 runnable [0x65773000..0x65773fc0]".
>
> Cheers
> Chris.
> [Message sent by forum member 'chrjohn' (chrjohn)]
>
>
http://forums.java.net/jive/thread.jspa?messageID=352714
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how:
http://au.mobile.yahoo.com/mail