MII Workbench Freezes

[Former Member]

I have it that the MII workbench will freeze randomly when I open BLS Transactions.

It happens all the time but never on the same transaction. The only way to fix it is to kill the javaw.exe in task manager.

Java Version: 6 update 24 build 1.6.0_24-b07

MII Workbench: 12.1.7.50

Windows: XP sp3

Internet Explorer: 8

[agentry_src]

Hi Jasper,

Have you had any problems with the Java Virtual Machine locking up outside of the workbench (through the same transactions executed through Scheduler, Message Listeners, or web pages)?

Have you turned Trace on or increased your logging level?

How many transactions do you have in your transaction calls path?

How large are the blocks of data that you are processing?

Are you trying to connect to an outside data source which may not be responding promptly (timing out)?

If you export your transactions, how large are the saved files?

What does the NW log viewer show happening at the time of the locking up?

How do you restart the workbench?

Have you looked at the transaction manager function to see what the logs there show?

This is a start.

Regards,

Mike

[Former Member]

>

> Have you turned Trace on or increased your logging level?

I turned the Trace level to 5 but the java console freezes with MII so the last message I see is the fetch from the server.

>

> How many transactions do you have in your transaction calls path?
> How large are the blocks of data that you are processing?
> Are you trying to connect to an outside data source which may not be responding promptly (timing out)?

This is happening on the load of the transaction, I've never had it freeze durring execution

>

> If you export your transactions, how large are the saved files?

It varies from 50 - 100k it not the same transaction all the time.

>

> What does the NW log viewer show happening at the time of the locking up?
> How do you restart the workbench?

Open task manager and kill the javaw.exe process

>

> Have you looked at the transaction manager function to see what the logs there show?

Doesn't show anything since it's on load and not on execution. Mii works fine when I call the transactions from the runner or through xacute queries. This only happens in the workbench.

[jcgood25]

Jasper,

You're not alone in this - there is an open customer ticket relating to the same thing, and I don't think any formidable pattern can be identified. The only consistent pattern is that is keeps happening (opening a trx) - an annoying and challenging thing to track down.

I put an internal memo into the ticket referencing this thread, and I would encourage you to log a customer support ticket as well so that perhaps we can get to the bottom of things with a pattern and route cause.

Regards,

Jeremy

[agentry_src]

What are your memory allocations to the JVM? I suggest you make sure it is set to 2GB minimum.

And getting back to one of my questions (How many transactions do you have in your transaction calls path?), I have seen instances where the transaction calls path (transactions calling other transactions calling other transactions) which have somehow gotten into a recursion loop or simply had too many calls in the chain. The workbench loads the entire chain of transactions when you load a single one, even though you don't see it. (NOTE: there has been discussion about changing this behavior, but I have not heard of implementation).

There are two options towards changing this. First, use the dynamic transaction call to break the chain (the workbench does not load the transactions called from a dynamic transaction call). Second and not as useful, is to simplify your transaction chains. Frequently there are too many small transactions (each with their own overhead) in a chain. You may want to look at them with the idea of combining several together. There is a certain amount of overhead associated with each transaction loaded.

Regards,

Mike

Edited by: Michael Appleby on Mar 13, 2011 6:20 PM