Session IDbs on Remote Invoke services

In wM v4.01 we had a problem with session ID’s created on one IS server being Identical. This problem was highlighted once the connection to the next IS server tried to interact with a database. Once we understood the issue, it was easy enough to solve.

We run about 8000 transactions a day. Has anyone seen this issue with 6.01? Is wM handling session ID’s any differently now?

Thanks in advance,

If the service that had a common session ID was started by the scheduler, than Yes - the problem has been fixed in 6.0.1 and there is a fix available for at least one of the 4.x releases.

The problem was multiple threads where using the same session, therefore, the same session ID. This is the core scenario that caused the problem.