| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RC 2298 |
« View previous topic :: View next topic » |
| Author |
Message
|
| p.cradwick |
 Posted: Mon Sep 29, 2008 3:34 pm Post subject: RC 2298 |
 |
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Hi,
I have a Java app that runs on MQ7 on Windows and connects to a local QM directly or, if a channel is provided, using a client connection. The app connects correctly on Windows, but when I moved it to Linux (MQ7), I got rc=2298 when trying to connect directly, but it connected ok using the client connection. The relevant connection code is shown below:
Hashtable connectionProperties = new Hashtable();
connectionProperties.put(MQConstants.HOST_NAME_PROPERTY, hostname);
connectionProperties.put(MQConstants.PORT_PROPERTY, portInt);
try {
logger.logDebug(false, threadName + ": Channel name = " + channel);
if (channel.length() == 0) {
connectionProperties.put(MQConstants.TRANSPORT_PROPERTY, MQConstants.TRANSPORT_MQSERIES_BINDINGS);
mQQManager = new MQQueueManager(qManager, connectionProperties); // Connect to local QM
logger.logInfo(true, threadName + ": Connected directly to local QueueManager: " + qManager + " on port: " + portStr + " on host: " + hostname);
} else { // Client connection
When no channel is specified (length()==0) the log shows the 'debug' line but throws 2298 before getting to the 'info' line. 2298 is MQRC_FUNCTION_NOT_SUPPORTED - so which function is it referring to and why?
Thanks in advance
Peter |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Sep 29, 2008 6:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I would expect it to be the client connection because you did not provide enough parameters and the bindings connection has nowhere to connect to...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Tue Sep 30, 2008 11:12 am Post subject: RC 2298 |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Not sure what you mean by that.
The client connection works fine on MQ6 and MQ7 (Linux & Win), and the bindings connection works fine on MQ6 - Linux & Windows. The problem is that using the bindings connection on Linux MQ7 I get 2298.
The bindings connection connects to the queue manager specified in 'qManager'.
Peter |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 30, 2008 12:54 pm Post subject: Re: RC 2298 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| p.cradwick wrote: |
Not sure what you mean by that.
The client connection works fine on MQ6 and MQ7 (Linux & Win), and the bindings connection works fine on MQ6 - Linux & Windows. The problem is that using the bindings connection on Linux MQ7 I get 2298.
The bindings connection connects to the queue manager specified in 'qManager'.
Peter |
The connection parms checking might be more restrictive in V7.
You are passing a host and port which is not necessary for a bindings connection and you are not passing a channel which is needed for a client connection. So which ever way I look at it, one way you are passing too much info (conflicting), on the other way not enough.
Have you looked up differences between V6 and V7 in that area? What does the manual say ?
Enjoy
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
