[seam-issues] [JBoss JIRA] (SEAMJMS-65) Ingress JMS bridging results in endless invocations of observer method
Thorsten Kunz (Commented) (JIRA)
jira-events at lists.jboss.org
Mon Dec 19 04:19:09 EST 2011
[ https://issues.jboss.org/browse/SEAMJMS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651882#comment-12651882 ]
Thorsten Kunz commented on SEAMJMS-65:
--------------------------------------
Well I only put the @Routing on the injected field to try different things. It was not there in the first version I wrote.
Anyway I changed what you suggested but I am afraid it is still looping.
Here is how the routing interface looks like now:
@Routing(RouteType.BOTH)
public void bidirectionalStringQueue(@Observes String string, @JmsDestination(jndiName = "queue/test") Queue queue);
And here is how the event generator injection looks like:
@Inject
@Outbound
private Event<String> stringEvent;
Everything else is still as it was in the attached classes. Don't know if it helps but here is the deployment log:
10:15:25,330 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "mdb-test.war"
10:15:25,588 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-1) Encountered invalid class name "implClass=org.jboss.seam.jms.test.descriptor.HornetQJMSDescriptorImpl" for service type "org.jboss.seam.jms.test.descriptor.HornetQJMSDescriptor"
10:15:25,588 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-1) Encountered invalid class name "importerClass=org.jboss.shrinkwrap.descriptor.impl.base.XMLImporter" for service type "org.jboss.seam.jms.test.descriptor.HornetQJMSDescriptor"
10:15:25,588 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-1) Encountered invalid class name "defaultName=hornetq-jms.xml" for service type "org.jboss.seam.jms.test.descriptor.HornetQJMSDescriptor"
10:15:25,761 INFO [org.jboss.weld] (MSC service thread 1-8) Processing CDI deployment: mdb-test.war
10:15:25,843 INFO [org.jboss.weld] (MSC service thread 1-3) Starting Services for CDI deployment: mdb-test.war
10:15:25,862 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 SNAPSHOT
10:15:25,881 INFO [org.jboss.weld] (MSC service thread 1-6) Starting weld service
10:15:26,035 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-6) Solder Config XML provider starting...
10:15:26,036 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-6) Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider
10:15:26,039 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-6) Reading XML file: vfs:/content/mdb-test.war/WEB-INF/lib/seam-jms-3.1.0.CR1.jar/META-INF/beans.xml
10:15:26,044 INFO [org.jboss.solder.Version] (MSC service thread 1-6) Solder null (build id: null)
10:15:26,214 INFO [org.jboss.solder.core.CoreExtension] (MSC service thread 1-6) Preventing class org.jboss.seam.jms.bridge.RouteManagerImpl from being installed as bean due to @Veto annotation
10:15:26,229 INFO [org.jboss.solder.core.CoreExtension] (MSC service thread 1-6) Preventing class org.jboss.seam.jms.bridge.EgressRoutingObserver from being installed as bean due to @Veto annotation
10:15:27,015 INFO [org.jboss.seam.jms.Seam3JmsExtension] (MSC service thread 1-6) Skipping annotation @javax.enterprise.event.Observes(during=IN_PROGRESS, notifyObserver=ALWAYS)
10:15:27,016 INFO [org.jboss.seam.jms.Seam3JmsExtension] (MSC service thread 1-6) Skipping annotation @javax.enterprise.event.Observes(during=IN_PROGRESS, notifyObserver=ALWAYS)
10:15:27,137 INFO [org.jboss.seam.jms.Seam3JmsExtension] (MSC service thread 1-2) Version: null (build id: null)
10:15:27,138 INFO [org.jboss.seam.jms.bridge.EgressRoutingObserver] (MSC service thread 1-2) Routing destinations: [[HornetQQueue[testQueue]]]
10:15:27,139 INFO [org.jboss.seam.jms.bridge.RouteImpl] (MSC service thread 1-2) Routing destinations: [[HornetQQueue[testQueue]]]
10:15:27,139 INFO [org.jboss.seam.jms.bridge.IngressMessageListener] (MSC service thread 1-2) Setting route. org.jboss.seam.jms.bridge.RouteImpl at cbbaf
10:15:27,139 INFO [org.jboss.seam.jms.bridge.IngressMessageListener] (MSC service thread 1-2) Qualifiers: [@org.jboss.seam.jms.annotations.Inbound(), @org.jboss.seam.jms.annotations.Routing(value=INGRESS)]
10:15:27,178 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Mojarra 2.1.3 (SNAPSHOT 20110825) für Kontext '/mdb-test' wird initialisiert.
10:15:27,657 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final
10:15:27,779 INFO [solder-servlet] (MSC service thread 1-2) Catch Integration for Servlets enabled
10:15:27,786 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /mdb-test
10:15:27,826 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "mdb-test.war"
> Ingress JMS bridging results in endless invocations of observer method
> ----------------------------------------------------------------------
>
> Key: SEAMJMS-65
> URL: https://issues.jboss.org/browse/SEAMJMS-65
> Project: Seam JMS
> Issue Type: Bug
> Components: Event Bridging
> Affects Versions: 3.1.0.CR1
> Environment: JBAS 7.1.0.Beta1b
> Reporter: Thorsten Kunz
> Assignee: John Ament
> Attachments: EventGenerator.java, RoutingInterface.java, TestMessageConsumer.java
>
>
> I have defined this interface method:
> @Outbound public void routeStringToQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue);
> @Inbound public void routeStringsFromQueue(@Observes String string, @JmsDestination(jndiName = "queue/pegasusMessage") Queue queue);
> Then create this observer method:
> public void inboundMessageTest(@Observes @Inbound String message) { ... }
> Once a String type event is fired this is being logged:
> 13:59:26,095 INFO [org.jboss.seam.jms.MessageManagerImpl] (http-localhost-127.0.0.1-8080-1) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> 13:59:26,108 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
> 13:59:26,110 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> 13:59:26,337 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
> 13:59:26,339 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> 13:59:26,386 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
> 13:59:26,387 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
> 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> 13:59:26,403 INFO [org.jboss.seam.jms.AbstractMessageListener] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Received a message
> 13:59:26,404 INFO [org.jboss.seam.jms.MessageManagerImpl] (Thread-1 (group:HornetQ-client-global-threads-1800568262)) Routing destination HornetQQueue[pegasusMessageQueue] with message HornetQMessage[null]:PERSISTENT
> [ ... and so on ... ]
> It works just fine if I replace the observer method with a regular MDB for this destination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list