[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3429) Build for chatroom example needs to deploy chatroom-service.xml on AS5

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-3429:
------------------------------

    Fix Version/s: 2.1.0.CR1
         Assignee: Shane Bryzak


> Build for chatroom example needs to deploy chatroom-service.xml on AS5
> ----------------------------------------------------------------------
>
>                 Key: JBSEAM-3429
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3429
>             Project: Seam
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 2.1.0.CR1
>            Reporter: Stan Silvert
>            Assignee: Shane Bryzak
>             Fix For: 2.1.0.CR1
>
>
> The build for the chatroom example fails to deploy chatroom-service.xml.  It must do this for AS5 to avoid startup errors.  In AS4.2, you will only get warning messages about creating a temporary topic.
> On AS5, you see this:
> 13:10:56,487 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 40eb2a(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 14ecfa4 destination=topic/chatroomTopic destinationType=javax.jms.Topic tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
> javax.naming.NameNotFoundException: chatroomTopic not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:564)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:572)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:578)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:317)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:291)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.util.naming.Util.lookup(Util.java:222)
>         at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)
>         at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
>         at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
>         at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
>         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
>         at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira