We have recently upgraded our webMethods Broker from 6.1 to 6.5.2. (with I.S. on 6.1 SP1) in our Production Environment
Since then, we have experienced an excessive increase in number of Unable to ack document exception (as below)
2007-03-26 03:14:12 CDT [ISS.0098.0049C] Exception:com.wm.app.b2b.server.dispatcher.exceptions.EndpointUnavailableException: [ISS.0098.9014] BrokerException: Timeout (112-1450): The request timed out.
while executing trigger. Unable to ack Document for TriggerStore:CRMS4POrderAcknowledgementSUB.S4P:trigger.
and also a significant increase in the number of “duplicate documents”
We try turn on Exactly-Once procesisng (with Document History Databae) - the Detect Duplicate (with Redelivery count does not work) - but the system performance becomes ridiculously slow.
We end up roll-back the upgrade (and back to Broker 6.1)
However, does any one have any idea what can be the possible explanation of the issue ? Does Broker 6.5.2 require more resources (like Socket Connection, Inbound Connection, or something else) from the OS that may cause the issue ?
We are running on 32 bit Windows 2003 Server with I.S. 6.1 SP1 with Broker 6.5.2 (and now back to Broker 6.1)
[FONT=Arial]we have experienced same exception Unable to ack document exception (see below from server log) with [COLOR=red]EndpointavailableException[/font][/color]
[FONT=Arial][B][/font][/b] 2007-08-30 12:06:23 EDT [ISS.0098.0049C] Exception:com.wm.app.b2b.server.dispatcher.exceptions.EndpointUnavailableException: [ISS.0098.9014] BrokerException: Timeout (112-1450): The request timed out.
while executing trigger. Unable to ack Document for TriggerStore:bright.triggers:EventdayTrigger.
2007-08-30 12:06:23 EDT [ISS.0098.0036E] DefaultProducer encountered Transport Exception: com.wm.app.b2b.server.dispatcher.exceptions.EndpointUnavailableException: [ISS.0098.9014] BrokerException: Timeout (112-1450): The request timed out. 2007-08-30 12:06:23 EDT [ISS.0098.0064D] Publishing delayed while outbound store is draining. Service: wm.server.publish:publish Error: while executing trigger. Unable to ack Document for TriggerStore:Bright.triggers:EventdayTrigger. Error explanation from Advantage site; Informed the customer that the specific error was benign and that happens when the broker receives duplicate acks for documents that have already been previously acknowledged. The ack document is just dropped by the broker in such a case without any known side effects at this time. Broker system log-no error found 2007-08-30 12:11:42 EDT 1268 - Warning: Disconnecting session id 34 because it is not responding to keep alive requests. webMethods Broker in our Production Environment Version Product webMethods Broker Administrator Version 6.5.0.0.288 060605 [FONT=Arial]API Version 6.5 [/font]
[B][/b] If any one have any idea what can be the possible explanation of this issue? This exception we are getting almost everyday’s. Thanks