[JNDI and Naming] New message: "Re: ConnectionFactory JNDI no found in JNDI view"
by Sridevi KA
User development,
A new message was posted in the thread "ConnectionFactory JNDI no found in JNDI view":
http://community.jboss.org/message/530733#530733
Author : Sridevi KA
Profile : http://community.jboss.org/people/sri1083
Message:
--------------------------------------------------------------
The log which i get on start up of node1 is as follows:
[JmsActivation] Unable to reconnect org.jboss.resource.adapte
r.jms.inflow.JmsActivationSpec(a)43a498b6(ra=org.jboss.resource.adapter.jms.JmsRes
ourceAdapter@18862d13 destination=queue/CallbackQueue isTopic=false tx=true dura
ble=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1
minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.reso
urce.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null
DLQMaxResent=5)
javax.naming.NameNotFoundException: XAConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.util.naming.Util.lookup(Util.java:215)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQ
Connection(AbstractDLQHandler.java:131)
at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(Ab
stractDLQHandler.java:83)
at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBo
ssMQDLQHandler.java:48)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActiv
ation.java:355)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivati
on.java:301)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(Jms
Activation.java:249)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.r
un(JmsActivation.java:589)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:
275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:756)
at java.lang.Thread.run(Thread.java:619)
I am using Jboss esb server.. JBoss AS version is Jboss AS 4.2.1 GA
Java version 1,6,0_18..
OS is Windows 7 64 bit
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530733#530733
16 years, 1 month
[JBoss Microcontainer] New message: "Re: Sub deployer not kicking in on CreateDestinationDeployer"
by Ales Justin
User development,
A new message was posted in the thread "Sub deployer not kicking in on CreateDestinationDeployer":
http://community.jboss.org/message/530724#530724
Author : Ales Justin
Profile : http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
> I have tried adding a dependency on HornetQJMSRealDeployer to the HornetQDestinationCreator and it still didn't work.
>
>
> <bean name="HornetQJMSRealDeployer" class="org.jboss.as.integration.hornetq.deployers.HornetQJMSRealDeployer">
> <depends>HornetQDestinationCreator</depends>
> </bean>
>
You need demand, not depends.
Depends does this -- legacy style depends -- B depends on A:
* B waits until A is created
* A is created, now B can be created
* B now waits until A is started
* A is started, hence B can be as well
Where "demand" is simple one state dependency, by default in Installed.
In our case we need the A to be fully installed, since this is when it is automagically picked up and its output added to deployer.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530724#530724
16 years, 1 month