| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Jboss integration with WS MQ... Fault Test failed |
« View previous topic :: View next topic » |
| Author |
Message
|
| Shetty_Ritesh |
 Posted: Mon Aug 11, 2008 2:04 pm Post subject: Jboss integration with WS MQ... Fault Test failed |
 |
|
Newbie
Joined: 08 Aug 2008
Posts: 3
|
Hi,
I have integrated Jboss appservers with WSMQ using the following configurations
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<!-- The WSMQ JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=RemoteWSMQJMSProvider">
<attribute name="ProviderName">RemoteWSMQJMSProvider</attribute>
<attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
<attribute name="QueueFactoryRef">remotewsmq/ABCCON</attribute>
<attribute name="TopicFactoryRef">remotewsmq/ABCCON</attribute>
</mbean>
<!-- The WSMQ JMS connection factory -->
<no-tx-connection-factory>
<jndi-name>RemoteWSMQJms</jndi-name>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/RemoteWSMQJMSProvider</config-property>
<max-pool-size>5</max-pool-size>
</no-tx-connection-factory>
<!-- Bind a remote IBM MQ server -->
<mbean code="org.jboss.naming.ExternalContext"
name="jboss.jndi:service=ExternalContext,jndiName=remotewsmq">
<attribute name="JndiName">remotewsmq</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:///dnbusr1/app/deploy/sunjndi
</attribute>
<attribute name="InitialContext">javax.naming.InitialContext</attribute>
</mbean>
</connection-factories>
It works fine when i publish messages but when we conducted fault tests by making the Queuemanager unavailable and then making it available again the jboss resource adaptor was not able to connect back to the MQ.
It started throwing
javax.jms.JMSException||MQJMS2008: failed to open MQ queue SYSTEM.JMS.D.MYQUEUE||Stack Trace : javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.JMS.D.MYQUEUE |
|
| Back to top |
|
 |
| LeRiton |
| Posted: Tue Dec 01, 2009 7:17 am Post subject: |
|
|
Newbie
Joined: 01 Dec 2009
Posts: 1
|
Hi,
I got the same issue, JBoss 5.0.1GA.
Exception appens when MQ server reboot and unfortunately, I got no access to MQ server log files / configuration.
Did you finally find something ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 02, 2009 10:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| LeRiton wrote: |
Hi,
I got the same issue, JBoss 5.0.1GA.
Exception appens when MQ server reboot and unfortunately, I got no access to MQ server log files / configuration.
Did you finally find something ? |
What is your connection pool purge policy?
You realize of course that non durable pub/sub does not survive a connection interruption, yes? You need to unsubscribe the current subscription, the current resource (connection), reacquire it and resubscribe...
_________________
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
|
|
|
|
