[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta

rnicholson10 do-not-reply at jboss.com
Sun Jun 14 09:29:58 EDT 2009


Howard,

Are you running the bridge across two physically different boxes? I have the default JMS Provider (localhost) and a remote JMS Provider to a separate box with a different IP Address.

If your remote provider is also localhost you might not see the issue.

Here are my JMS providers (jms-ds.xml):


  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <connection-factories>
  | 
  |   <!-- ==================================================================== -->
  |   <!-- JMS Stuff                                                            -->
  |   <!-- ==================================================================== -->
  | 
  |    <!--
  |        The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to
  |        be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available.
  |        See http://jira.jboss.org/jira/browse/JBMESSAGING-843.
  |    -->
  |    <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
  |           name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
  |       <attribute name="ProviderName">DefaultJMSProvider</attribute>
  |       <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
  |       <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
  |       <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
  |       <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
  |    </mbean>
  | 
  |    <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
  |        name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider">
  |       <attribute name="ProviderName">RemoteJMSProvider</attribute>
  |       <attribute name="ProviderAdapterClass">
  |           org.jboss.jms.jndi.JNDIProviderAdapter
  |       </attribute>
  |       <attribute name="FactoryRef">/XAConnectionFactory</attribute>
  |       <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute>
  |       <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute>
  |       <attribute name="Properties">
  |           java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
  |           java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
  |           java.naming.provider.url=jnp://jbdevapp1:1099
  |       </attribute>
  |    </mbean>
  | 
  |    <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
  |    <tx-connection-factory>
  |       <jndi-name>JmsXA</jndi-name>
  |       <xa-transaction/>
  |       <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:/DefaultJMSProvider</config-property>
  |       <max-pool-size>20</max-pool-size>
  |       <security-domain-and-application>JmsXARealm</security-domain-and-application>
  |       <depends>jboss.messaging:service=ServerPeer</depends>
  |    </tx-connection-factory>
  | 
  | </connection-factories>
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237486#4237486

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237486



More information about the jboss-user mailing list