• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

JMS Listener Port  RSS feed

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have listener Port for Topic

When I run the server it's giving error like



The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/TCF. The exception which was received is com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008 Reason code 3008
[10/9/04 19:16:33:688 IST] 3ccc7031 MDBListenerIm W WMSG0019E: Unable to start MDB Listener Subscriber, JMSDestination jms/T : com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008 Reason code 3008



anybody have come across this problem
 
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would check out IBM's MQ documentation to see what that error code means.
 
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i think the problem is with WSAD configuration
 
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by rakkesh kumar:
I have listener Port for Topic

When I run the server it's giving error like



The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/TCF. The exception which was received is com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008 Reason code 3008
[10/9/04 19:16:33:688 IST] 3ccc7031 MDBListenerIm W WMSG0019E: Unable to start MDB Listener Subscriber, JMSDestination jms/T : com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008 Reason code 3008

anybody have come across this problem



Hi Rakesh,

I am not sure, but I think you have to start the listener service through the admin tool(I have used MQSeries5.1).

Regards,
M.S.Raman
 
rakkesh kumar
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi
raman

i have installed embedded messaging client and server

the listener state is not getting started while changing it's state through adminstrative console.
 
Malli Raman
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Following answer is given in the IBM site...

When starting my MDB Listener, why am I getting the message, 'The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$TopicConnectionFactory. The exception which was received is com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008 Reason code 3008'?

A: The 3008 reason code for the Broker command can occur when the userid has an incorrect length. The Event Broker only allows a 12 character userid on the MS Windows platform and 8 characters on the UNIX platforms. It is recommended that your userids be a maximum of 8 characters, unless you know for certain that your network only consists of Windows machines. Then you could have a maximum of 12 characters.

Refer URL:http://www.developer.ibm.com/tech/faq/results/0,1322,1%253A401%253A406%253A60%253AWebSphere%2BMQ%2BIntegrator%2B%2528WBI%2BBrokers%2529,00.html#q60
 
siva kumar
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HI RAMAN

IF USER ID USED TO LOGIN WINDOWS ABOVE 12 CHARACTERS

THEN THE BROKER COMMAND FAILED.
 
siva kumar
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
it's working 4 normal JMS Topic applications .

Only in case of MDB it's giving that error for me.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!