-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
What steps will reproduce the problem?
1. Followed instructions for deployment (wrote a socket-invoked MDB, etc.)
2. Send a few messages from a client
3. The first few fail to garner responses; eventually one will get through and
get some responses, but these dry up quickly.
What is the expected output? What do you see instead?
I am expecting the first client to get connected. I am also not expecting the
sudden failures.
What version of the product are you using? On what operating system?
Using the most recent version (1.2.3) on OS X, my app server is Glassfish 3.
Please provide any additional information below.
I am also seeing blanket failures with the following exception:
"SEVERE: Error while accepting a socket request and scheduling work on the
request. See linked exception
javax.resource.spi.work.WorkRejectedException: error code: 1
at com.sun.enterprise.connectors.work.WorkCoordinator.workTimedOut
..."
This occurs just after an accept (I'm seeing "INFO: Allocated endpoint,
poolsize 1 of 5" immediately prior in the logs.)
Original issue reported on code.google.com by jweissma...@gmail.com on 21 Jun 2011 at 5:57