Kbase P19985: SonicMQ: java.net.UnknownHostException
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
SonicMQ 4.x
SYMPTOM(s):
java.net.UnknownHostException if trying to reconnect to remote node for DRA
CAUSE:
DEFAULT_ROUTING_ACCEPTOR was not specified in broker.ini
If a routing connection that has been established to the current broker by
another broker times out or fails, the current broker will not use the routing
connection information to resolve in-doubt messages. Instead, it will try to
reconnect to the original broker to resolve indoubt messages using the acceptor
specified by the other broker in its DEFAULT_ROUTING_ACCEPTOR property.
If the DEFAULT_ROUTING_ACCEPTOR information is not specified than the SonicMQ broker will try to reconnect using the other information it got while the handshaking. This will be both the IP-address but also the host name. If the host name is unknown within the domain the local broker is running in than a java.net.UnknownHostException will get thrown.
FIX:
The java.net.UnknownHostException gets catched by the SonicMQ broker but it can
fill the log file. Therefor it is better to specify the valid IP-address for the DEFAULT_ROUTING_ACCEPTOR of the remote node. There is not more harm. Making the remote node available again lets the local broker reconnect even after having thrown that exception and deliver the messages.