[JBoss Messaging] - JMS Messaging problem between multiple Jboss Instance.
by sandeepu
Hello All,
I am facing a problem when creating a Topic receiver. I have 2 jboss(Jboss1 and Jboss2) instance running in my local machine. Topic is deployed in the Jboss2. I am trying to create a receiver for the topic in the Jboss1 process. But i get the following error "Destination doesnot exist".
The JNDI look up is fine for connection factory as well as for topic. But when i create the receiver from the session it fails.
>From the trace it looks like it is searching for the destination in the jboss1 only(JVMServerIL). But i dont know why.
Please find the trace
org.jboss.mq.server.TracingInterceptor.subscribe EXCEPTION : subscribe:
javax.jms.InvalidDestinationException: The destination TOPIC.XXX does not exist !
at org.jboss.mq.server.ClientConsumer.addSubscription(ClientConsumer.java:140)
at org.jboss.mq.server.JMSDestinationManager.subscribe(JMSDestinationManager.java:572)
at org.jboss.mq.server.JMSServerInterceptorSupport.subscribe(JMSServerInterceptorSupport.java:171)
at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:157)
at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:651)
at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:177)
at org.jboss.mq.il.jvm.JVMServerIL.subscribe(JVMServerIL.java:170)
at org.jboss.mq.Connection.addConsumer(Connection.java:791)
at org.jboss.mq.SpySession.addConsumer(SpySession.java:947)
at org.jboss.mq.SpySession.createSubscriber(SpySession.java:710)
at .......
Can any body please help me out?
I am using Jboss4.04GA.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159319#4159319
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159319
18 years
[JBoss Tools (users)] - Missing jboss-seam.jar on deploy of EAR app.
by rgordon
Hi,
I have just upgraded to the latest version of Eclipse 3.2.2, jboss tools 2.1.1.GA and Seam 2.0.2.SP1 and am getting problems deploying my EAR application.
The error below is shown when the project is deployed due to jboss-seam.jar not getting copied, although all the other jar files are successfully deployed. Any ideas where I have gone wrong?
Richard
My application.xml only contains :-
| <?xml version="1.0" encoding="UTF-8"?>
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
| version="5">
|
| <display-name>SymNet-ear</display-name>
|
| <module>
| <web>
| <web-uri>SymNet.war</web-uri>
| <context-root>/SymNet</context-root>
| </web>
| </module>
|
| <module>
| <ejb>SymNet-ejb.jar</ejb>
| </module>
|
| <module>
| <ejb>jboss-seam.jar</ejb>
| </module>
|
| </application>
|
Error deploying app is :-
| 15:41:21,000 ERROR [MainDeployer] Could not initialise deployment: file:/D:/Java/jboss-4.2.2.GA/server/default/deploy/SymNet-ear.ear/
| org.jboss.deployment.DeploymentException: url file:/D:/Java/jboss-4.2.2.GA/server/default/deploy/SymNet-ear.ear/jboss-seam.jar could not be opened, does it exist?
| at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
| at org.jboss.deployment.EARDeployer.init(EARDeployer.java:288)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| 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 $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| 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 $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159313#4159313
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159313
18 years
[JBoss Messaging] - Message Consumer fails when using messageSelector
by mbreuer
I am evaluating JBoss 4.2.2 and JBoss Messaging 1.4.0SP3. When using MessageConsumer with a messageSelector, the communication hangs.
The response ObjectMessage is build in the right way, msg.setJMSCorrelationID() and msg.setJMSType() are set. The MessageProducer sends
the message, but the receiver doesn't receive it.
The messageSelector looks like this: (JMSCorrelationID = '1213880979122' AND JMSType='java.lang.String')
It seems to be okay. (mistakes will produce an exception)
cfB = (ConnectionFactory) ic.lookup("/ConnectionFactory");
| connectionB = (Connection) cfB.createConnection();
| sessionB = connectionB.createSession(false, Session.AUTO_ACKNOWLEDGE );
| queue = (Queue) ic.lookup("queue/B"); // one of the example queues
| consumer = sessionB.createConsumer(queue, messagleSelector );
| Message msg = consumer.receive();
Note: the code works when running outside JBossAS, but does not receive messages from inside the container.
After setting messageSelector=null a message is received. The debug-inspector shows there are no message headers (JMSCorrelationID,JMSType) are set. I verified the sender, while sending the jms header attributes are set (checked with debugging inspector).
It seems the headers are lost during transport ....
Differences:
Outside JBossAS the inspector indicates a SpyObjectMessage while inside the container a JbossObjectMessage is used.
Any ideas what's wrong? JBoss Messaging was installed with ant (messaging-node1). A cluster configuration (based on all) is used with a single node.
In the past the code was used with jboss 4.0.3 and JBossMQ. In run fine, but after switching to jboss-messaging the hangs occur.
Questions:
1.) How can i solve the problem?
2.) Is there a difference in these lines or are they equivalent?
msg.setJMSCorrelationID(correlationId); // 1
msg.setStringProperty("JMSCorrelationID", correlationId ); //2
markus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159310#4159310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159310
18 years