-
1. Re: PreAcknowledge active?
clebert.suconic Oct 20, 2010 11:09 PM (in response to swany)For MDBS you need to set properties through the activation. You won't affect anything if you set the connection factories on jms-ds.xml only.
This is probably a cross-reference of our other post? you should have kept a single thread.
-
2. Re: PreAcknowledge active?
swany Oct 21, 2010 9:08 AM (in response to clebert.suconic)OK, so I uncommented the following invoker activation config in my JBoss 4.2.3 standardjboss.xml configuration file, added the PreAcknowledge property, and still the ServerSessionImpl class shows preAcknowledge = false. But anyway this would only affect the consumer side of the ack configuration, right? Does the MDB activation config affect how the publisher operates? Wouldn't the server session still get that from the connection factory (which I've already configured?). How else would the server side / publisher know which ack mode to use?
(BTW regarding my other post, I'm still thinking that these are two separate issues. Regardless of acknowledge mode, the MDB / J2EE server should ack the message automatically. And the J2EE spec does say that auto-acknowledge is the default).
<!-- Uncomment to use JMS message inflow from jmsra.rar --><invoker-proxy-binding><name>message-driven-bean</name><invoker-mbean>default</invoker-mbean><proxy-factory>org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory</proxy-factory><proxy-factory-config><activation-config><activation-config-property><activation-config-property-name>providerAdapterJNDI</activation-config-property-name><activation-config-property-value>DefaultJMSProvider</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>minSession</activation-config-property-name><activation-config-property-value>1</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>maxSession</activation-config-property-name><activation-config-property-value>15</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>keepAlive</activation-config-property-name><activation-config-property-value>60000</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>maxMessages</activation-config-property-name><activation-config-property-value>1</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>reconnectInterval</activation-config-property-name><activation-config-property-value>10</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>useDLQ</activation-config-property-name><activation-config-property-value>false</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>DLQHandler</activation-config-property-name><activation-config-property-value>org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>DLQJNDIName</activation-config-property-name><activation-config-property-value>queue/DLQ</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>DLQMaxResent</activation-config-property-name><activation-config-property-value>1</activation-config-property-value></activation-config-property><activation-config-property><activation-config-property-name>PreAcknowledge</activation-config-property-name><activation-config-property-value>true</activation-config-property-value></activation-config-property></activation-config><endpoint-interceptors><interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor><interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor><interceptor>org.jboss.proxy.TransactionInterceptor</interceptor><interceptor>org.jboss.invocation.InvokerInterceptor</interceptor></endpoint-interceptors></proxy-factory-config></invoker-proxy-binding><!-- Uncomment to use JMS message inflow from jmsra.rar -->
<invoker-proxy-binding>
<name>message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory</proxy-factory>
<proxy-factory-config>
<activation-config>
<activation-config-property>
<activation-config-property-name>providerAdapterJNDI</activation-config-property-name>
<activation-config-property-value>DefaultJMSProvider</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>minSession</activation-config-property-name>
<activation-config-property-value>1</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>maxSession</activation-config-property-name>
<activation-config-property-value>15</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>keepAlive</activation-config-property-name>
<activation-config-property-value>60000</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>maxMessages</activation-config-property-name>
<activation-config-property-value>1</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>reconnectInterval</activation-config-property-name>
<activation-config-property-value>10</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>useDLQ</activation-config-property-name>
<activation-config-property-value>false</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>DLQHandler</activation-config-property-name>
<activation-config-property-value>org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>DLQJNDIName</activation-config-property-name>
<activation-config-property-value>queue/DLQ</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>DLQMaxResent</activation-config-property-name>
<activation-config-property-value>1</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>PreAcknowledge</activation-config-property-name>
<activation-config-property-value>true</activation-config-property-value>
</activation-config-property>
</activation-config>
<endpoint-interceptors>
<interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
<interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor>
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
</endpoint-interceptors>
</proxy-factory-config>
</invoker-proxy-binding>