[JBoss Messaging] - Re: Queue attributes not being implemented
by timfox
Just to clarify the above email.
If you *do not* wish to use the MDB container DLQ (this is the one configured here http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMDB and has nothing to do with JBM), and would rather use the JBM DLQ and benefit from the ability to specify different DLQs per queue with different values of MaxDeliveryAttempts, then you can comment out the DLQ section from http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMDB, to give something like:
| <invoker-proxy-binding>
| <name>message-driven-bean</name>
| <invoker-mbean>default</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <CreateJBossMQDestination>true</CreateJBossMQDestination>
| <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <!-- This is commented out - JBM dlq will be used instead
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| -->
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
Note that this will allow you to use the JBM DLQ, ExpiryQueue and MaxDeliveryAttempts values, but it *will not* allow you to use the JBM redelivery delay, since redelivery is implemented by the MDB container as explained in the previous post.
There's not really much we can do about other than change the MDB container to implement redelivery delay.
JBM Redelivery delay will only have an effect when *not* using MDBs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047981#4047981
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047981
19 years, 1 month
[Remoting] - JBoss 4.2.0GA
by MarcReis
Hi,
I am looking at the 4.2.0 Server and am hence trying to figuring out the http communication config (we had it at 4.0.4).
Its been a while so I might just be missing something, but at the moment all I get is a
| java.lang.reflect.UndeclaredThrowableException
| at $Proxy1.sayHello(Unknown Source)
| at com.somewhere.ejb3.client.TestClient.main(TestClient.java:22)
| Caused by: java.lang.Exception: Can not make remoting client invocation due to not being connected to server.
| at org.jboss.remoting.Client.invoke(Client.java:1555)
| at org.jboss.remoting.Client.invoke(Client.java:530)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:41)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:46)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:40)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
| ... 2 more
First of, do I still need the servlet-invoker.war ?. (http://jira.jboss.com/jira/browse/JBREM-407 )
Second do I still need the apache*jars as in http://jira.jboss.com/jira/browse/JBAS-2766?
I had hoped that I would just need to configure
1) ejb3.deployer\META-INF\jboss-service.xml like
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="InvokerLocator">servlet://${jboss.bind.address}:8080/invoker/EJBInvokerServlet</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
2.)Set the hostname of the server (not sure about the default client bind url, so I tried with an without)
3.) and of course the jndi.properties for the client.
| java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=http://MYPC-281:8080/invoker/JNDIFactory
|
I tried the differnt configs, from what I thought is needed in 4.2.0 to one matching that of the 4.0.4 config (with ServletServerInvoker for the ejb and default client bind url) and between. Still leaves me with the same error. Did I miss some obvious steps?
Sincerly
marc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047980#4047980
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047980
19 years, 1 month