[jboss-user] [JBoss Messaging] - Re: Running jboss-messaging client in the JBoss AppServer
We have same issue. We are using EJB3 MDBs and a servlet that creates a local listerner in the same server instance as JBM (1.2.0.GA). Could you please let me us know what finally worked for you? I have tried replacing remoting jar but EJB3 seems to stop working then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032146#4032146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032146 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Error running standalone configuration
Will it help if we upgrade to JBoss AS 4.0.5? We need a very slim version of JBoss Messaging. Should we instead of trying to make "standalone" work, try slim down the default messaging configuration? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030582#4030582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030582 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Error running standalone configuration
We are running JBM 1.2.0.GA on JBoss AS 4.0.4.GA. On using the "standalone" installation for installing bare minimum configuration we get the following error | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss:service=invoker,type=jrmp | State: NOTYETINSTALLED | Depends On Me: | jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory | | ObjectName: jboss:service=TransactionManager | State: NOTYETINSTALLED | Depends On Me: | jboss.web:service=WebServer | jboss.messaging:service=PersistenceManager | jboss.messaging:service=PostOffice | jboss.messaging:service=JMSUserManager | jboss.jca:service=WorkManager | jboss.jca:service=RARDeployer | jboss.jca:service=CachedConnectionManager | jboss.jca:service=LocalTxCM,name=DefaultDS | | ObjectName: jboss.security:service=JaasSecurityManager | State: NOTYETINSTALLED | Depends On Me: | jboss.web:service=WebServer | | ObjectName: jboss:service=Naming | State: NOTYETINSTALLED | Depends On Me: | jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory | jboss.jmx:alias=jmx/rmi/RMIAdaptor | | ObjectName: jboss.jdbc:service=metadata | State: NOTYETINSTALLED | Depends On Me: | jboss.jdbc:service=metadata,datasource=DefaultDS | | ObjectName: jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar' | State: NOTYETINSTALLED | Depends On Me: | jboss.jca:service=ManagedConnectionFactory,name=DefaultDS | | Also looking at the logs, we see the following exception | java.lang.NoSuchMethodException: org.jboss.jmx.connector.invoker.AuthenticationInterceptor.(org.jboss.mx.server.MBeanInvoker) | at java.lang.Class.getConstructor0(Class.java:2647) | at java.lang.Class.getConstructor(Class.java:1629) | at org.jboss.mx.modelmbean.ModelMBeanInvoker.getInterceptors(ModelMBeanInvoker.java:739) | at | org.jboss.mx.modelmbean.ModelMBeanInvoker.configureInterceptorStack(ModelMBeanInvoker.java:678) | at org.jboss.mx.modelmbean.XMBean.configureInterceptorStack(XMBean.java:400) | at org.jboss.mx.modelmbean.ModelMBeanInvoker.init(ModelMBeanInvoker.java:504) | at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:486) | at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654) | | Its seems like there is a mismatch somewhere but we have not been able to nail it down. Thanks for the help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030235#4030235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030235 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Authentication failure after JBM 1.2.0.GA installation
Hi, We were using JBoss AS 4.0.4.GA and JBM 1.0.1.SP2. Due to some messaging issue we decided to move on to 1.2.0.GA. In doing so, our NT authentication module required for one of our web applications broke. We are using tagish and simple NTSystemLogin module from an earlier post http://www.jboss.org/index.html?module=bb&op=viewtopic&t=58750 Authentication works fine if the earlier configuration is used but fails for the new configuration with JBM 1.2.0.GA. We are using the non-cluster installation. This is very puzzling since the configuration seems to be okay. Thanks for the help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028176#4028176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028176 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - EJB3 MDB stopped working
Hi, Tried posting this on EJB3.0 forum but may be this is better forum for this issue Basically, EJB3 MDBs which were working fine with JBoss 4.0.4.GA, JBoss Messaging1.0.1.CR5 and EJB3 RC8 have stopped working with EJB3 RC9. Tried also running the example EJB3MDB that comes with JBoss Messaging and got the same exception 10:49:25,242 WARN [ServiceController] Problem starting service jboss.j2ee:jar=m db-example.ejb3,name=EJB3MDBExample,service=EJB3 java.lang.NullPointerException at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:85) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.resolveMessageL istener(JBossMessageEndpointFactory.java:241) The MDB implements just the MessageListener interface so this really puzzling. Thanks for the help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983003#3983003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983003 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - EJB3 MDB with JBoss Messaging
Hi,
I have some EJB3 MDBs which were working fine with JBoss 4.0.4.GA, JBoss
Messaging1.0.1.CR5 and EJB3 RC8. The only issue was that I could not start/stop
the MDBs using JMX. Reading through the forums it looked like this was fixed in
RC9 build of EJB3.
I installed the EJB3 RC9 using the ant script and followed the migration (RC8 -
RC9) notes. On restarting initially got the error saying the jms-ra.rar was
already registered. To fix that, copied the deploy/jms/jms-ra.rar to
deploy/jms-ra.rar replacing the existing jms-ra.rar and deleted the jms
directory.
That got rid of that problem but I keep getting the following:
MIPServer.jar,name=TestMDB,service=EJB3
java.lang.NullPointerException
at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:85)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.resolveMessageL
istener(JBossMessageEndpointFactory.java:241)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMess
ageEndpointFactory.java:184)
at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer
.java:185)
at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:1
51)
at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
I am sure I am missing some step here but cannot find what exactly it is. MDB
looks like the following
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Topic"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="topic/topicname"),
@ActivationConfigProperty(propertyName="durability",propertyValue="Durable"),
@ActivationConfigProperty(propertyName="clientId",propertyValue="ClientID"),
@ActivationConfigProperty(propertyName="noLocal",propertyValue="true"),
@ActivationConfigProperty(propertyName="subscriptionName",propertyValue="SubName")
})
Thanks for the help.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982962#3982962
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982962
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: EJB 3 MDB and Messaging
Apologize for the typo. @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic"), @ActivationConfigProperty(propertyName="destination", propertyValue="topic/testTopic") Here is the stack trace again 07:33:51,776 INFO [Ejb3Deployment] EJB3 deployment time took: 20 07:33:52,077 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=mdb-e xample.ejb3,name=EJB3MDBExample,service=EJB3 with dependencies: 07:33:52,087 INFO [EJBContainer] STARTED EJB: org.jboss.example.jms.ejb3mdb.EJB 3MDBExample ejbName: EJB3MDBExample 07:33:52,117 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.0.4.GA/server/messa ging/deploy/mdb-example.ejb3 07:33:52,117 WARN [MDB] JMS provider failure detected: javax.jms.JMSException: Error creating the dlq connection: null at org.jboss.ejb3.mdb.DLQHandler.createService(DLQHandler.java:153) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBean Support.java:260) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java: 188) at org.jboss.ejb3.mdb.MDB.setupDLQ(MDB.java:791) at org.jboss.ejb3.mdb.MDB.innerCreate(MDB.java:294) at org.jboss.ejb3.mdb.MDB.innerStart(MDB.java:225) at org.jboss.ejb3.mdb.MDB.start(MDB.java:214) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973534#3973534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973534 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - EJB 3 MDB and Messaging
Hi, We are using JBoss 4.0.4 and Messaging 1.0.1.CR3. We need to implement EJB3 MDBs and are in process of prototyping. We can make the example MDB run with Queues. If Queues are replaced by Topic in the annotations the MDB does not deploy. @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic"), @ActivationConfigProperty(propertyName="destination", propertyValue="queue/testTopic") We get the following exception 21:31:56,032 WARN [MDB] JMS provider failure detected: javax.jms.JMSException: Error creating the dlq connection: null at org.jboss.ejb3.mdb.DLQHandler.createService(DLQHandler.java:153) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBean Support.java:260) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java: 188) at org.jboss.ejb3.mdb.MDB.setupDLQ(MDB.java:791) at org.jboss.ejb3.mdb.MDB.innerCreate(MDB.java:294) at org.jboss.ejb3.mdb.MDB.innerStart(MDB.java:225) at org.jboss.ejb3.mdb.MDB.start(MDB.java:214) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWra pper.java:99) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy68.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java :82) at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.jav a:439) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:486) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:139) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jbo
[jboss-user] [JBoss Messaging] - Re: Wildcard support
I wish I could. Currently working on gov. project with delivery this dec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970727#3970727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970727 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Wildcard support
Thanks for the quick reply. This seems to be part of 1.2.1 release. Any chance it will be done earlier? This is very crucial for us. Should we be using MQ instead and move to Messaging later next year. What does Jboss recommend? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970721#3970721 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970721 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Wildcard support
Hi, Does Jboss Messaging support wildcards in destination name for federated name hierarchies? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970714#3970714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970714 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: messages working only in one node of cluster
Clarification question. Are you using JBoss Messaging or JBoss MQ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964590#3964590 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964590 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
