|
Quick Lists
|
|
Bug ID:
|
4430840
|
|
Votes
|
0
|
|
Synopsis
|
linux system could not connect to cluster server
|
|
Category
|
jmq:broker
|
|
Reported Against
|
2.0beta
|
|
Release Fixed
|
2.0(2.0fcs)
|
|
State
|
11-Closed,
Unverified,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4344135
|
|
Submit Date
|
28-MAR-2001
|
|
Description
|
After a reboot we attempted to connect ouch into the cluster
From the master broker it appeared that ouch was in the cluster however
ouch still saw:
[27/Mar/2001:16:01:39 PST] WARNING [B2061]: Still trying to connect to the master broker [ Address = cochin/129.144.252.109:7676 (jmqbroker) ]. Client connections will not be accepted until the master broker is ready.
(NOTE: ouch is a linux system)
ouch could ypmatch cochin
added to /etc/host file and were still unable to attach
|
|
Work Around
|
N/A
|
|
Evaluation
|
This problem is caused because the service will
not restart because of a hotspot bug ..
Workaround for bug 4344135: Linux: close is not preemptive
This is a linux hotspot JDK bug in which the thread waiting
on serversocket.accept() is never notified (through IOException)
when the socket is close
The workaround is to keep the serversocket open, but explicitly
close any new connections as they come in
(NOTE: the JDK bug was supposed to be fixed in 1.3.1 .. however
I was still able to duplicate the problem in 1.3.1-r1 ...)
xxxxx@xxxxx 2001-03-28
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
