Kbase P105589: Adapter for SonicMQ: Durable 4GL-JMS Subscriber hangs
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  10/1/2007 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
SonicMQ
SYMPTOM(s):
Adapter for SonicMQ
Durable 4GL-JMS Subscriber hangs
4GL-JMS Client hangs while consuming a message from the Adapter for SonicMQ
4GL-JMS Clients' JMS Durable Destination on the SonicMQ Broker grows as message processing on the client has stopped
The verbose <Adapter_Name>.server.log for the adapter for SonicMQ shows the message being delivered from the Adapter:
Thread-<#####>(MMM DD, YYYY HH:MM:SS:MS) <IP_Address>::<Adapter_Name>::<Adapter_Port>::<Connection_ID>: getNextMessage(): Sending DATA message to the client. Message ID is: ID:<Message_ID>
The message is never acknowledged by the 4GL-JMS Client as there is no "Acknowledged message: ID" statement in the log file for this message ID.
CAUSE:
Bug #: 20050606-029
FIX:
Upgrade to 9.1E02,10.0B03, or 10.1A