transaction server in 8.98.1.1

The install was nice once I have a stand-alone WAS61 installation.  Not problems.  Almost worked out of the box – amazed yes.

I did try and copy my old 8.96 config files over the top of the existing ones, that WAS a mistake.  Just fix the ones that are shipped.

It probably worked this way in the old release, but the e1transvr makes extensive use of the internal WebSphere queueing mechanisms for reliable delivery.

The messages are stored in the F98710 table until a transaction server is available to receive all of the messages.  Once the transaction server is started, it lists the subscribers that are subscribing to it for messages. (This is really nice and can be seen in server manager).  This is also really nice because it shows you how many messages are queues to each of the subscribers.

You need to count the rows in the F90710 to see how many messages are yet to make it to the transaction server.

This is the view from SM of some subscribers.

If you had a situation like me with 16500 queued messages, you might need to clear the cache – but OF COURSE this does not work in the current 8.98.1.1 tools release.  So, a sneaky way I found was the following:

Find the dir that has the filestore for the logs and pending transactions and delete the files.

Viola, you no longer have 16500 messages queued to be delivered.