Invalid Sequence Number (ISS.0098.0036E) in Server Log

, ,
1

On March 6,2007 we upgraded a IS 6.1/Broker 6.1 environment to IS v6.5 SP1 / Broker 6.5.2. After this upgrade we are consistantly seeing the following message in our Server Log:

[ISS.0098.0036E] webM IS RequestReplyHandler encountered Transport Exception: com.wm.app.b2b.server.dispatcher.exceptions.TransportException: Invalid Sequence Number (277-1773): Invalid sequence number was passed in.

Both the IS instance and Broker were shut down during the upgrade. Prior to restart the following IS data directories were cleared out:
[Integration Server]/DocumentStore
[Integration Server]/WmRepository2
[Integration Server]/WmRepository4
[Integration Server]/audit/data

After the system came back up on line the broker documents were “re-syncd”.

At this point in time also, I have created a brand new broker and attached to integration instance to this clean broker. Even after this, I still get the same error message.

Any ideas or help would be welcome!

2

I have a client that has encountered this same error. How did you resolve it?

3

Hi,

We are getting the same exception, its filling up our server logs. We are using IS 7.1.2. Has anybody got this error and able to resolve too?

Thanks

4

this typical happens when your doc published to broker and ack goes out of sequence generally in case of problem b/w IS and broker… do you see any connection issues b/w your Integration server and broker?

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.