| Author |
Message
|
| akidase |
 Posted: Wed Feb 19, 2014 11:02 pm Post subject: Message Flow Hung. Please help determining root cause. |
 |
|
Centurion
Joined: 10 Jan 2011
Posts: 124
|
8.0.0.3
Message Flow doesn't respond. It cannot be redeployed/stopped/removed.
Not sure what is causing it to hang. Please help in how to determine the same.
Service uses two different JDBC configurable services with JDBC_TransactionType.MB_TRANSACTION_AUTO Database Oracle
Input from a queue with Transaction Mode as Yes. After retrieval from database, creates xml (as many as database retrievals) and propagates each of it to be placed in another queue - Transaction Mode- Automatic.
Let me know of any queries. Thanks! |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Wed Feb 19, 2014 11:56 pm Post subject: Re: Message Flow Hung. Please help determining root cause. |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
"My Computer isn't working. Please help me in finding the root cause"
(Did you try rebooting  )
Broker thinks you may do an important transaction (e.g. wire 19billion to somewhere). If this is not the case, then kill the process "kill -9" (dataflow engine).
First thing I would do: Check if you have (programmed) an endless loop ?
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| akidase |
| Posted: Wed Feb 19, 2014 11:59 pm Post subject: |
|
|
Centurion
Joined: 10 Jan 2011
Posts: 124
|
No Loops
Presently I am doing kill -9 on the EG repeatedly. Checking if Database has any locks. None found. What else can hold up.. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Feb 20, 2014 12:12 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Play around with the flow (implementation) with focus on it's transactional behaviour (including dead locks) to find out where the problem is
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Feb 20, 2014 12:28 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| akidase wrote: |
No Loops
Presently I am doing kill -9 on the EG repeatedly. Checking if Database has any locks. None found. What else can hold up.. |
It's a good idea to inhibit get on the input queue before killing the execution group process. Otherwise the loop will immediately restart when the broker automatically restarts the execution group, depending on backout treshold settings and depth of the input queue.
Then enable user trace on the flow, unlock the input queue, inhibit get it again and kill the EG. Examine the user trace. |
|
| Back to top |
|
|
| akidase |
| Posted: Thu Feb 20, 2014 2:10 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011
Posts: 124
|
Got the problem..
My JCN isn't committing the update statement to Oracle causing the issue.
After multiple propagate statements.
| Code: |
conn = getJDBCType4Connection("ESBDB", JDBC_TransactionType.MB_TRANSACTION_AUTO);
ps = conn.prepareStatement(updateQuery);
ps.setString(1, timestamp);
int s = ps.executeUpdate(); |
|
|
| Back to top |
|
|
|
|
