Server too busy, cannot force server shutdown

Question

Hi!
I am running WLS6.1 SP2 on W2K SP2, with Cloudscape 4.0.
I am unable to access the console (after waiting a couple minutes) nor to force
a server shutdown through the command
line, which results in the following exception:
Failed to connect to t3://127.0.0.1:7001 due to:[t3://127.0.0.1:7001: Destination
unreachable; nested exception is:
        java.io.InterruptedIOException: Read timed out; No available router to
destination]
It seems to be because the server is in heavy processing of
JMS messages which, when consumed, result in bulk inserts
in the database. However, I need to force a "clean" server
shutdown to be sure that the database does a checkpoint and flushes all the commited
data.
Any hint would be greatly appreciated,
Guillaume Bedard

Answer 1

Hi.
Ok - thanks for that. Please open a case with support.
Thanks,
Michael
Guillaume Bedard wrote:
It only happens when the server is running my application. As
for JMS, it is processing because I am doing outputting a
comment in the console whenever a message was processed.
I found out that when changing the <Transaction-Attribute> of
my message-driven beans to "none" instead of "Required", the
server is able to display the console promptly. Otherwise,
it takes about five minutes to show up...
Guillaume
Michael Young <[email protected]> wrote:
Hi.
Hmm. Definitely not correct behavior. Does this only happen when your
server is
running your application, or does it also happen when your server is
idle (application
undeployed)?
How do you know that your server is processing JMS messages when this
is occuring? Have
you taken a thread dump? If not please take one (ctrl-break if memory
serves) and post
it here.
Thanks,
Michael
Guillaume Bedard wrote:
Hi!
I am running WLS6.1 SP2 on W2K SP2, with Cloudscape 4.0.
I am unable to access the console (after waiting a couple minutes)nor to force
a server shutdown through the command
line, which results in the following exception:
Failed to connect to t3://127.0.0.1:7001 due to:[t3://127.0.0.1:7001:Destination
unreachable; nested exception is:
java.io.InterruptedIOException: Read timed out; No availablerouter to
destination]
It seems to be because the server is in heavy processing of
JMS messages which, when consumed, result in bulk inserts
in the database. However, I need to force a "clean" server
shutdown to be sure that the database does a checkpoint and flushesall the commited
data.
Any hint would be greatly appreciated,
Guillaume Bedard--
Michael Young
Developer Relations Engineer
BEA Support
Michael Young
Developer Relations Engineer
BEA Support