-
1. Messages was not delivered
slogger Jul 3, 2008 4:57 AM (in response to slogger)Additional info:
I am using jms resource adapter and External JNDI on client:<connection-factories> <!-- ==================================================================== --> <!-- JMS Stuff --> <!-- ==================================================================== --> <!-- The JMS provider loader --> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProviderRemote"> <attribute name="ProviderName">RemoteJMSProvider</attribute> <attribute name="ProviderAdapterClass"> org.jboss.jms.jndi.JNDIProviderAdapter </attribute> <!-- The combined connection factory --> <attribute name="FactoryRef">XAConnectionFactory</attribute> <!-- The queue connection factory --> <attribute name="QueueFactoryRef">XAConnectionFactory</attribute> <!-- The topic factory --> <attribute name="TopicFactoryRef">XAConnectionFactory</attribute> <!-- Uncomment to use HAJNDI to access JMS--> <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=10.0.0.166:1199 </attribute> </mbean> <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader" name="jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool"> <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends> <attribute name="PoolName">StdJMSPool</attribute> <attribute name="PoolFactoryClass"> org.jboss.jms.asf.StdServerSessionPoolFactory </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:/RemoteJMSProvider</config-property> <min-pool-size>10</min-pool-size> <max-pool-size>50</max-pool-size> <application-managed-security/> </tx-connection-factory> <mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=remoteJndi"> <attribute name="JndiName">remoteJndi</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://10.0.0.166:1199 </attribute> <attribute name="InitialContext">javax.naming.InitialContext</attribute> <depends>jboss:service=Naming</depends> </mbean> </connection-factories>
-
2. Re: Messages was not delivered
ataylor Jul 4, 2008 8:57 AM (in response to slogger)I'm not really sure what you're problem is, obviously if you unplug the network this will cause errors on either the client or server.
JBM works by sending messages to a client side buffer from which the client will consume messages from. This is for performance reasons. If you close the connection the consumer will wait to receive any messages that are still in the client side buffer, if at this point the server is unreachable the client will probably timeout waiting to ack the messages. -
3. Re: Messages was not delivered
slogger Jul 7, 2008 5:08 AM (in response to slogger)"ataylor" wrote:
I'm not really sure what you're problem is, obviously if you unplug the network this will cause errors on either the client or server.
JBM works by sending messages to a client side buffer from which the client will consume messages from. This is for performance reasons. If you close the connection the consumer will wait to receive any messages that are still in the client side buffer, if at this point the server is unreachable the client will probably timeout waiting to ack the messages.
Hi, Andy!
Thank you very much for answer!
Yes, it throws exception like 'connection reset', but after this 'WARN [org.jboss.jms.client.container.ClientConsumer] Timed out waiting for
last delivery 4 got -1 ' issued and messages delivering is not working :-0(.
Did feature request http://jira.jboss.com/jira/browse/JBREM-891 fix this problem?
Please, sorry my English! -
4. Re: Messages was not delivered
ataylor Jul 7, 2008 5:28 AM (in response to slogger)Again, i'm not sure what your problem is, I would expect these errors when unplugging a network cable.
-
5. Re: Messages was not delivered
slogger Jul 7, 2008 11:07 AM (in response to slogger)"ataylor" wrote:
Again, i'm not sure what your problem is, I would expect these errors when unplugging a network cable.
It necessary for us to provide correctness of work on unstable network connections and recovery of delivering after losing connection.
I was found like one in http://jira.jboss.com/jira/browse/JBREM-947. It is solution of this problem? -
6. Re: Messages was not delivered
ataylor Jul 7, 2008 11:22 AM (in response to slogger)JBM supports failover when clients lose connection to a node. This is all documented in the user docs. http://www.jboss.org/jbossmessaging/docs/index.html