ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ConfigMgrProxyException: Could not send msg data to MQSeries

Post new topic  Reply to topic
 ConfigMgrProxyException: Could not send msg data to MQSeries « View previous topic :: View next topic » 
Author Message
sridhsri
PostPosted: Wed Mar 25, 2009 10:31 am    Post subject: ConfigMgrProxyException: Could not send msg data to MQSeries Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I have a CMP application with the following code:
Code:
         ConfigManagerProxy.enableConfigManagerProxyTracing("trace.txt");
                  
         MQConfigManagerConnectionParameters mqConfigMgrConnParams = new MQConfigManagerConnectionParameters(Server, Port, QueueManager);
         mqConfigMgrConnParams.disableDomainAwareness();
         
         mqConfigMgrConnParams.setAdvancedConnectionParameters("TEMP", null, null, 0, 0, "mqm", null);
         MQConfigManagerConnectionParameters.enableMQJavaClientTracing("mqtrace.txt");
         
         ConfigManagerProxy cmp = ConfigManagerProxy.getInstance(mqConfigMgrConnParams);


I do not want to use the default 'SYSTEM.BRK.CONFIG' server conn channel and instead I want to use a different channel. Hence the setAdvancedConnectionParameters().

When I run the application, the exception I get is:
Code:
com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: Could not send message data to MQSeries
   at com.ibm.broker.config.proxy.MQSender.send(MQSender.java:372)
   at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:163)
   at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithConfigManager(AdministeredObjectPool.java:1727)
   at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdministeredObject(AdministeredObjectPool.java:1530)
   at com.ibm.broker.config.proxy.ConfigManagerProxy.<init>(ConfigManagerProxy.java:229)
   at com.ibm.broker.config.proxy.ConfigManagerProxy.getInstance(ConfigManagerProxy.java:296)


I enabled CMP Tracing and MQ Client Tracing. The CMP Trace contained:
Code:

2009-03-25 14:16:03.0250 main...........         { com.ibm.broker.config.proxy.SendManager.send()
2009-03-25 14:16:03.0250 main...........           { com.ibm.broker.config.proxy.SendManager.checkForSpecialRequests()
2009-03-25 14:16:03.0250 main...........           } com.ibm.broker.config.proxy.SendManager.checkForSpecialRequests()
2009-03-25 14:16:03.0265 main...........           i: CMP sending:
DUMBLEDORE
serializer.version=1.0
commsmessage.type=com.ibm.broker.config.common.Request
...
configmanagerproxy.hostname=XXXX
userid=sridhsri
commsmessage.operationtype=register
uuid=
commsmessage.configobjecttype=ConfigManagerProxy
configmanagerproxy.version=61
configmanagerproxy.noeventlog=false
configmanagerproxy.osname=Windows XP

2009-03-25 14:16:03.0265 main...........           { com.ibm.broker.config.proxy.SendManager.isReplyRequired()
2009-03-25 14:16:03.0265 main...........           } com.ibm.broker.config.proxy.SendManager.isReplyRequired() true
2009-03-25 14:16:03.0265 main...........           { com.ibm.broker.config.proxy.MQSender.send(replyRequired=true)
2009-03-25 14:16:03.0265 main...........             { com.ibm.broker.config.proxy.MQConnectionHelper.disconnect()
2009-03-25 14:16:03.0265 main...........             } com.ibm.broker.config.proxy.MQConnectionHelper.disconnect()
2009-03-25 14:16:03.0265 main...........             com.ibm.broker.config.proxy.MQSender.send() threw an exception: Could not send message data to MQSeries. Stack trace follows.
com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: Could not send message data to MQSeries
   at com.ibm.broker.config.proxy.MQSender.send(MQSender.java:372)
   at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:163)
   at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithConfigManager(AdministeredObjectPool.java:1727)
   at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdministeredObject(AdministeredObjectPool.java:1530)
   at com.ibm.broker.config.proxy.ConfigManagerProxy.<init>(ConfigManagerProxy.java:229)
   at com.ibm.broker.config.proxy.ConfigManagerProxy.getInstance(ConfigManagerProxy.java:296)



The MQ Client Trace did not contain anything. It just had the initial JVM information.

Does anybody have any ideas what might be the problem ?
Back to top
View user's profile Send private message
WMBDEV1
PostPosted: Thu Mar 26, 2009 2:20 am    Post subject: Reply with quote

Sentinel

Joined: 05 Mar 2009
Posts: 888
Location: UK

I dont know based on the information provided as it doesnt seem to hint to anything in particular.

Does it work if you dont try and set the AdvancedConnectionParameters?

Are you able to connect over this channel as the mqm user from another application

Do the MQ logs show an attempted connection?
Back to top
View user's profile Send private message
sridhsri
PostPosted: Thu Mar 26, 2009 5:39 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I was able to write a java application to connect to the queue manager and the SYSTEM BROKER queue.

The same java code works if I do not use the TEMP channel and instead use the SYS.BRK.CONFIG channel.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Thu Mar 26, 2009 6:32 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

The problem is (probably) that you're passing '0' to the advanced connection parameters you don't want to set; this sets the values to the literal '0' rather than leaving them default.
Use -1 instead. Also, for the deployid parameter you shouldn't use mqm.

So in other words, you should just be calling:
Code:
mqConfigMgrConnParams.setAdvancedConnectionParameters("TEMP", null, null, -1, -1, null, null);
Back to top
View user's profile Send private message
sridhsri
PostPosted: Thu Mar 26, 2009 6:38 am    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

That worked perfectly! Thanks so much Matt.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ConfigMgrProxyException: Could not send msg data to MQSeries
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.