[
http://jira.jboss.com/jira/browse/JBESB-1492?page=comments#action_12398444 ]
Martin Vecera commented on JBESB-1492:
--------------------------------------
The problem is still here.
Steps to reproduce:
1) Follow the instructions on
http://intranet.corp.redhat.com/ic/intranet/SOAPerformanceTestsHowTo.html (use dbinstall
to switch to Oracle, and do steps 1. - 2.)
2) Make identical copy of your installation to another machine, and change ServerPeerID in
server/oracle/deploy/jboss-messaging.sar/messaging-service.xml
3) unpack the attached archive and look into Performance1_?.esb:/META-INF/jboss-esb.xml -
you must change jndi-URL in jms-jca-provider tag to reflect your machines' hostnames
4) Start the nodes and deploy the archives there.
5) Use attached jmsmock application to generate messages (don't forget to configure
jndi.properties, and variables in run_gener_jms.sh to point to your installation at the
node where you will run it).
6) After a while you should be able to see some output on consoles.
7) Undeploy (delete) the ESB archive from the node you are not sending messages to.
Don't forget that the services use NotifyQueues so queue/A get full without cleaning.
If you are not able to simulate it, just give me a ping on IRC.
"JMSException: Failed to route Reference" during failover
---------------------------------------------------------
Key: JBESB-1492
URL:
http://jira.jboss.com/jira/browse/JBESB-1492
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Environment: SOA-P 4.2.1.beta1, Oracle DB
Reporter: Martin Vecera
Assigned To: Martin Vecera
Fix For: 4.3
Attachments: JBESB-1492.tar.bz2, jmsmock.tar.bz2
First see atached archive for all the referenced files.
Problem:
I deployed the same service to two nodes in JMS cluster (see scen1_supported.png). Then I
started to generate messages to the queue quickstart_helloworld_Request_gw. I tried
several times to undeploy and deploy again the service on both nodes (not at both nodes at
the same time). It isn't so easy to reproduce this issue when I start with clean DB
and fresh server instances. But once the error appeared you can reach it 100%. The node
where the service is currently undeployed shows the errors (see below and node1.log)
unfinitely (for more then 1 minute). The second node stops processing the messages during
the errors. Once the service is deployed again on the first node the normal processing
continues.
2008-01-16 14:24:56,028 ERROR [org.jboss.messaging.util.ExceptionUtil]
SessionEndpoint[yeg-zagowhbf-1-45evvhbf-5vn4jb-a4wya] send
[c3j-c4sowhbf-1-45evvhbf-5vn4jb-a4wya]
javax.jms.JMSException: Failed to route Reference[62704]:RELIABLE to
quickstart_helloworld_Request_esb
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:743)
at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:383)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at
org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at
org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
at
org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
I also tried scen1_unsupported.png configuration with the same result. I was not able to
reach this problem when all the queues were deployed independently on the server.
For instructions on how to switch ESB to use Oracle DB see dbinstall.howto.txt.
To be able to deploy the Performance1 service you need to deploy test-result-service.sar
first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira