| Author |
Message
|
| paulgroo |
 Posted: Wed Jul 05, 2006 6:23 am Post subject: Reason Code 2085 on Remote Queues for Java App |
 |
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hi everyone.
Okay I have a real brain teaser: I have WebSphere MQ 5.3 running on iSeries. Using a java application (home grown), messages are put from the file system onto a remote queue in MQSeries and passed across onto a Windows machine.
When I run the java program, the error logs are giving me loads of 2085 messages (cannot find queue...). When I specify an alias queue, and point that alias queue at the remote queue, the java application posts the message across onto the central windows server but it's simply 'null' instead of having text content. I've checked permissions, compared the configuration with several other servers that use the same utility, recreated all MQ objects...(more or less everything except put a hammer through the side of the server).
Has anyone ever come across a simular problem? |
|
| Back to top |
|
 |
| Hassan |
| Posted: Wed Jul 05, 2006 7:30 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
| I know it sounds kinda simple but have you made sure that case is not the culprit here. iSeries automatically reverts to upppercase so if there is mixed case or lower case then ' ' have to be used. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Fri Jul 07, 2006 2:59 am Post subject: Workaround |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
| I ended up using a workaround for this one. I couldnt get the java app to connect to any of the remote queues, so I created a few alias queues which in turn pointed to the remote queues. Everything's working fine now. Still don't understand what the problem was though... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 07, 2006 3:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A 2085 on a put, when you know the queue exists, usually means that you've specified a queue manager name incorrectly on the put. Like you've connected to qmgr A and put to a qlocal on A, but specified qmgr B in the put call.
Working with remote queues, it probably means that your remote queue definition isn't quite right - maybe you spelled the transmission queue name wrong?
On the other hand, if that were true, then using an alias queue instead shouldn't fix the problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Fri Jul 07, 2006 3:28 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Yes, that's the thing... I recreated the queue manager objects to make sure that they were pristine, but still it wouldnt through the messages onto the RemoteQ. I would have thought the same problem would arise with the Alias queues, but it's grand! Pah, I dunno. Maybe it's more of a java issue (?!). I'm going to recreate everything on a test box on Monday and see what's really going with this malarcky.
Thanks for the feedback though! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 07, 2006 3:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, yeah, "maybe it's a java issue" is what I mean. Your java code might be specifying a queue manager name somewhere that it shouldn't be.
This is extremely easy to do with JMS - just put one in the queue destination instead of just the QCF.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
