| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| migrating JMS app from WAS 4 to WAS5.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| lfindlater |
 Posted: Fri Jun 17, 2005 7:16 am Post subject: migrating JMS app from WAS 4 to WAS5.1 |
 |
|
Newbie
Joined: 15 Jun 2005
Posts: 2
|
Hi
We are currently migrating a JMS application from WAS4 to WAS5.1, and have been unable to get the application to work. As far as I understood, the only difference in configuring WAS was that in WAS4 you used JMSadmin, but in WAS5.1 I would have to use the adminconsole to define the queue connection factory and the queue destinations.
We are running websphere mq 5.3 (csd06) on a seperate server to the WAS boxes, and have installed the MQ client onto the WAS boxes
I have configured the QCF and Q destination using the WAS adminconsole, and i have set the MQ_INSTALL_ROOT to point to the installation directory for the websphere MQ client libraries.
The application itself places a message on a remote queue definition on the Websphere MQ server, which is transmitted to another queue manager running on our mainframe, the application then sets up some sort of receiver to wait for a reply message on a temporary queue. However after migrating to WAS5.1, the receiver times out (as the message seems to arrive on the transmission queue, but does not go any further) . On further investigation (and after changing the remote queue to a local queue on the MQ server) I noticed that the queue depth for the queue that the message was being sent to was incrementing by one, but on trying to browse the message in MQ explorer, there appear to be no message on the queue? There are also no errors being generated either on the appserver side, or in websphere MQ?
Unfortunately I am posing this question from a WAS administrator point of view, as I have not developed the java application myself, so I am wondering if perhaps changes to the code might be required when migrating the app from WAS4 to WAS5.1(has the JMS API changed??), or if there is some further configuration required in WAS5? Any help or suggestions would be greatly appreciated.
regards
Lisa  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jun 17, 2005 7:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I suspect you either have a transactional boundary problem (waiting for a response within the same transaction that is supposed to send the request), or an expiration problem.
These are both app issues, not admin issues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lfindlater |
| Posted: Sat Jun 18, 2005 10:07 pm Post subject: |
|
|
Newbie
Joined: 15 Jun 2005
Posts: 2
|
Hi
Thanks for the quick reply. Is there a specific reason this problem may have raised its head after the migration to WAS5.1? As the developers are fond of telling me, their code was working fine under WAS4. Is there a specific change in the JMS API that I maybe able to refer them to?
Thanks again for your advice.
regards Lisa |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jun 19, 2005 2:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are relatively huge differences between WAS4 and 5.1.
But like I said, the most likely candidates are a) writing the code in such a way that it tries to wait for the reply in the same transaction that was supposed to have *committed* the request, and b) setting the message expiration time too low (for example, in milliseconds rather than seconds).
So concentrate on the expiration first - if they aren't using it at all then you can eliminate this one right off, and if they are using it then try increasing the expiration time by a factor of 10 (just for testing).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
