Search...
FAQs Subscribe
Pie
FAQs
Recent topics Flagged topics Hot topics Best topics
Search...
Search within BEA/Weblogic Search Coderanch
Advance search Google search
Register / Login
permaculture playing cards
  • 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 Pie Elite all forums
thread boost book review grid advertise on coderanch building better world book meaningless drivel
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Bridge/Connector Error in Weblogic and MQSeries integration

 
Susmitha Metlapalli
Ranch Hand
Posts: 50
posted 16 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi,

I am integrating weblogic 9 and MQ Series 7 for JMS.

MQ Configuration

1. Created MQ QueueManager and Queues.
2. Created InitialContext, ConnectionFactory and Destinations.

Weblogic configuration

1. Created JMS Server, Store, Distributed queues, connection factory.
2. Created JMS bridge destinations with
a. Adapter jndi name - eis.jms.WLSConnectionFactoryJNDINoTX
b. Initial context factory for weblogic queue destination
weblogic.jndi.WLInitialContextFactory
c. Initial context factory for MQ queue destination
com.sun.jndi.fscontext.RefFSContextFactory
d. Connection url for weblogic queue destination
t3://localhost:7001
e. Connection url for MQ queue destination
file:/C:/JNDI-Directory
3. Created two bridges with source and target destinations.

I am getting following error.

<Dec 4, 2008 9:45:42 AM GMT+05:30> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">

Any thing more to be included?

Thanks,
Susmitha.
 
Susmitha Metlapalli
Ranch Hand
Posts: 50
posted 16 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi,

I could resolve the error mentioned in my previous post...

Now i am getting the following... Can anyone please help on this?

Error

<Dec 4, 2008 6:21:02 PM GMT+05:30> <Warning> <MessagingBridge> <BEA-200026> <Bri
dge "WLMQBridgeRec" encountered some problems in one of its adapters or underlyi
ng systems. It stopped transferring messages and will try to reconnect to the ad
apters shortly. (The exception caught was java.lang.Exception: javax.resource.Re
sourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
Connection.java:1457)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:70
5)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.jav
a:144)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(Messag
ingBridge.java:1284)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridg
e.java:1210)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:
2052)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.ja
va:2048)
at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMe
ssageConsumer.java:399)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMes
sageListener.onMessage(JmsMessageConsumerImpl.java:893)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.honourNoLocal(
WMQAsyncConsumerShadow.java:544)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.consumer(WMQAs
yncConsumerShadow.java:366)
at com.ibm.mq.jmqi.remote.internal.RemoteAsyncConsume.driveConsumer(Remo
teAsyncConsume.java:1444)
at com.ibm.mq.jmqi.remote.internal.RemoteDispatchThread.run(RemoteDispat
chThread.java:372)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(Wor
kQueueItem.java:209)
at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runIt
em(SimpleWorkQueueItem.java:100)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQue
ueItem.java:224)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQ
ueueItem(WorkQueueManager.java:296)
at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImpl
ementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1190)
-------------- Linked Exception ------------
javax.resource.ResourceException: Error creating producer or sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
Connection.java:1457)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection
.java:802)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.j
ava:84)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:6
98)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:69
5)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.jav
a:144)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(Messag
ingBridge.java:1284)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridg
e.java:1210)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:
2052)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.ja
va:2048)
at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMe
ssageConsumer.java:399)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMes
sageListener.onMessage(JmsMessageConsumerImpl.java:893)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.honourNoLocal(
WMQAsyncConsumerShadow.java:544)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.consumer(WMQAs
yncConsumerShadow.java:366)
at com.ibm.mq.jmqi.remote.internal.RemoteAsyncConsume.driveConsumer(Remo
teAsyncConsume.java:1444)
at com.ibm.mq.jmqi.remote.internal.RemoteDispatchThread.run(RemoteDispat
chThread.java:372)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(Wor
kQueueItem.java:209)
at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runIt
em(SimpleWorkQueueItem.java:100)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQue
ueItem.java:224)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQ
ueueItem(WorkQueueManager.java:296)
at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImpl
ementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1190)
-------------- Linked Exception 2 ------------
com.ibm.msg.client.jms.DetailedJMSException: JMSCC0005: The specified value 'MyS
ystemModule!WLDistributedQueueRec' is not allowed for 'XMSC_DESTINATION_NAME'. T
he given value is not allowed for the property specified. Change the value to a
value that is supported for the property.
at jrockit.reflect.NativeConstructorInvoker.newInstance([Ljava.lang.Obje
ct Ljava.lang.Object;(Unknown Source)
at jrockit.reflect.InitialConstructorInvoker.newInstance([Ljava.lang.Obj
ect Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Constructor.newInstance([Ljava.lang.Object;I)Ljava.
lang.Object;(Unknown Source)
at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NL
SServices.java:411)
at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLS
Services.java:390)
at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErro
rUtils.java:104)
at com.ibm.msg.client.jms.internal.JmsPropertyContextImpl.setObjectPrope
rtyInternal(JmsPropertyContextImpl.java:514)
at com.ibm.msg.client.jms.internal.JmsPropertyContextImpl.setObjectPrope
rty(JmsPropertyContextImpl.java:668)
at com.ibm.msg.client.wmq.common.internal.WMQPropertyContext.setObjectPr
operty(WMQPropertyContext.java:589)
at com.ibm.msg.client.wmq.common.internal.WMQPropertyContext.setStringPr
operty(WMQPropertyContext.java:641)
at com.ibm.msg.client.wmq.common.internal.WMQDestination.<init>(WMQDesti
nation.java:2972)
at com.ibm.msg.client.wmq.common.internal.WMQDestination.<init>(WMQDesti
nation.java:2926)
at com.ibm.msg.client.wmq.factories.WMQFactoryFactory.createProviderDest
ination(WMQFactoryFactory.java:418)
at com.ibm.msg.client.jms.admin.JmsDestinationImpl.setProviderDestinatio
n(JmsDestinationImpl.java:323)
at com.ibm.msg.client.jms.admin.JmsDestinationImpl.initialise(JmsDestina
tionImpl.java:221)
at com.ibm.msg.client.jms.admin.JmsDestinationImpl.<init>(JmsDestination
Impl.java:187)
at com.ibm.msg.client.jms.internal.JmsMessageImpl.setJMSDestination(JmsM
essageImpl.java:748)
at com.ibm.jms.JMSMessage.setJMSDestination(JMSMessage.java:1183)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:464
)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:336)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:218)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection
.java:781)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.j
ava:84)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:6
98)
.)>
 
juergen vorba
Greenhorn
Posts: 1
posted 16 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi Susmitha,

did you solve the problem? If not, please read the following prerequisite for MQ V7 (see Application row e.g for Linux systems http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27011924). I think MQ V7 is only supported working with BEA Weblogic Server 9.2.

Regards
Juergen
 
Samadhan Gudekar
Greenhorn
Posts: 2
posted 16 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator

Susmitha Metlapalli wrote:Hi,

I am integrating weblogic 9 and MQ Series 7 for JMS.

MQ Configuration

1. Created MQ QueueManager and Queues.
2. Created InitialContext, ConnectionFactory and Destinations.

Weblogic configuration

1. Created JMS Server, Store, Distributed queues, connection factory.
2. Created JMS bridge destinations with
a. Adapter jndi name - eis.jms.WLSConnectionFactoryJNDINoTX
b. Initial context factory for weblogic queue destination
weblogic.jndi.WLInitialContextFactory
c. Initial context factory for MQ queue destination
com.sun.jndi.fscontext.RefFSContextFactory
d. Connection url for weblogic queue destination
t3://localhost:7001
e. Connection url for MQ queue destination
file:/C:/JNDI-Directory
3. Created two bridges with source and target destinations.

I am getting following error.

<Dec 4, 2008 9:45:42 AM GMT+05:30> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">

Any thing more to be included?

Thanks,
Susmitha.





What was solution for your first post???

Thanks.
- Samadhan
 
Samadhan Gudekar
Greenhorn
Posts: 2
posted 16 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
What was solution for your first post???

Thanks.
- Samadhan
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
reply
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!
Similar Threads
More...