| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| JMS Session timeout |
« View previous topic :: View next topic » |
| Author |
Message
|
| balareddy |
 Posted: Tue Jan 09, 2007 5:04 am Post subject: |
 |
|
Acolyte
Joined: 06 Feb 2006
Posts: 54
|
Hello, very good discussion...
Well, my application will dequeue msg and transfer data to some other server thru FTP socket. Remote server is not my control at all and i dont know its functionality, it is completely block box for me. My work is to Tranfer data which is dequeued from my servers MQ Queue.
Deueue msg and transfer to remote servers should be done in single transaction so that no msg loss or no duplicates can happen.
And my servers load is very high, i have 40 Java threads running always.. every thread is using its own JMS session and to create FTP session to transfer data to other server.
_________________
bala |
|
| Back to top |
|
 |
| balareddy |
| Posted: Tue Jan 09, 2007 5:08 am Post subject: |
|
|
Acolyte
Joined: 06 Feb 2006
Posts: 54
|
| jefflowrey wrote: |
balareddy - are you able to build a test setup that will reliably hang the FTP transfer? If not... you're going to have a very hard time debugging this.
If you can, then turn on MQ trace, start your program, and hang the FTP session. Then wait until the transaction is rolled back and stop the tracing. Then look at the trace output and see what it says. |
I am not able to simulate this problem with my test program. I mean, FTP socket is working fine.
FTP session hangs when there is heavy load, when all threads are busy in dequeueing msg from Q and sending data to remote server thru FTP.
when FTP session hangs, that jms msg is going back to Q and some other thread is processing...
_________________
bala |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 09, 2007 5:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, if it's happening under heavy load, then it may be that MQ is rolling back your transaction in order to handle other things that it thinks are more important.
You can look at the MQ logs and you will see error messages that tell you this is being done.
You should look at tuning your queue manager - in this case probably by making the log files as large as possible. And you should look at distributing the work more. Put up another queue manager and implement MQ clustering to distribute messages going to your FTP sender program, and run another copy of your FTP sender program against that queue manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
