Transaction Catalog Limit
When you have either multi-levelled transactions (ie: Transaction 1 calls transaction 2 which calls transaction 3 etc), or high transaction re-use (even if it is conditional at runtime) is there a limit? I believe I have found one.
I have an application that has quite a few transaction calls embedded at various stages within various transactions.
However, when you access (eg: open) any transaction (or call to a transaction) where the pending "catalog" (that will be built) is large-ish, I see a blank grey box for a few seconds then nothing happens.....no error is returned......the transaction will just NOT load at all, and I am left with whatever transaction I was looking at rtaher than the one I wanted to open.
I see in the xMII log that there are multiple entries as follows;
INFO SessionHandler - Requested URL is http://localhost/Lighthammer/Catalog?Mode=Load&Class=Transaction&Object=<myTransaction>
which makes sense as I can see that the catalog is being built so I can use it within subsequent links etc.
But these entries just stop at a certain point in the logger. This certain point appears to be 10 secs after I triggered the initiating request to open the transaction.
During development it appears that the catalog building process spits the dummy at a certain point.
Any ideas what such a certain point might be?
I have scoured through the config and jsp's etc, but I cannot locate any parameter that could be causing this issue by imposing a limit and/or timeout.
Does anybody know of any such limits?
Limit by count?
Limit by memory?
Limit by time?