Hey all - we’ve been really struggling with an upgrade.
We have a 6.01 SP2 IS environment (60+ production servers) and one production 6.01 Broker.
We installed a new 6.5.2 Broker and upgraded three of the minor role ISs to 6.5 SP2. Everything worked okay, though we did get some odd errors around the Broker decoder when the newly upgraded ISs connected for the first time. Synchronization resolved this error only temporarily - it appears the Broker and the Dispatcher can’t seem to agree on the document version, even if it has not changed.
Several weekends ago, we took three IS servers that represent a major business initiative and upgraded them to 6.5 SP2 and connected them to the 6.5.2 Broker. Everything seemed to be okay, until Monday rolled around and we placed a load on the Broker (normal load is around 1,000 <5K documents per minute - the peak load is around 20,000 <5K documents).
This load, by the way, is tolerated by the 6.01 Broker with no problems.
As a load was introduced, the Broker CPU utilization went really high (jumped from 1.8% to 20+%) and our IS dispatchers start throwing timeout and disconnect errors.
Our 6.5.2 Broker has sufficient stor files and a good sized RAM cache. We didn’t see any errors in the syslog or Broker logs - it just didn’t handle the document load. webMethods support hasn’t really had any ideas for us, they want us to trace and debug, etc - but of course we had to roll back ASAP for the business and have not been able to duplicate this problem in test (mainly because we can’t successfully duplicate the load.)
So we’ve all been asking around, and one of the guys heard that Brokers above 6.5 SP1 have issues. I’d find that hard to believe, but I know software companies sometimes release version they wish they had not (such as the 6.01 IS version.)
Has anyone had these kind of issues with 6.5.2 or Brokers above 6.5 SP1?