Originally posted by: Myggiz

Hello all

I got a application that writes via JMS to a regular IBM MQ queue.
that are triggered in normal ways on incoming messages so far so god.

But here is the catch.
When the application doing the JMS posting does what it do, the Launcher stops responding and need to be restarted.
It is like the messages themself are killing it.

But if I with a map post 1000+ messages (or 1 at a time) to the queue it works flowless.

The difference beeing JMS from the custom app and MQ adapter from WTX.

Been banging my head against this for a few days and have no idea on where to look for a solution.

To make things worse there are no or little information on whats happening when the launcher system stops reading from the queue.
It might or might not create a ABORT file. But in logs all looks fine, MQ trace shows no unusally... so ideas ?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: phil2030

I take it your app enqueues messages using the MQMD and not the MQRFH (or whatever it is for JMS)?

Have you tried a simple put to the queue when the launcher is running from MQ Explorer? Does it work? Does it crash the launcher?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: phil2030

(hit send to early)

What happens if you kill your app having put 1 or more messages? Does the launcher continue? Does it process the messages? ...or does it still need bouncing? When you bounce the launcher, are the messages visible that your app put to the queue? ...are they processed?
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: Myggiz

Hmm..

Yes, using the MQMD ie setTargetClient = MQ in the app.

It does work putting things on the queue with MQ Explorer and the problem doesnt occure.

Yes, the messages are visable in the queue after the launcher stopped reading them. If I rebounce the
launcher it happily reads the message.

I see what you are going with this, and are also something we have had up for discussion.
There could be some form of ACK or commit thats lacking from the spplication side.
Thee question then is, how do i bring this topic to the developer to get it corrected ,and what should
be corrected. I do read and understand java code but its not what I do in general. So any help would be great.
Can even post the source thats used to post messages here for review if it helps ;)

// R
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: phil2030

...and if you kill the Java app, does the launcher continue or is it still hung up?

Do the messages appear in MQ Explorer if the Java app is running? I would try getting a message from the queue (whilst the Java app is running) that it has enqueued in the same session.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: Myggiz

Trying the kill app approach right now.

And yes the messages appear in the queue even if the java app is running.

// R
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: phil2030

If you run your Java app and enqueue one or more messages and the launcher "ignores" them ... what happens if you then put a message to the same queue using MQ Explorer? Does the launcher process the message from MQ Explorer?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender