martin mucha [
http://community.jboss.org/people/alfonz19] created the discussion
"configuring JMS in JBoss 5 to use oracle db."
To view the discussion, visit:
http://community.jboss.org/message/594177#594177
--------------------------------------------------------------
Hi, I'm trying to configure JMS without much success.
My simple example works fine with hsqldb. Next I replaced content of
hsqldb-persistence-service.xml with configuration for oracle from doc/examples. Next I
defined new datasource for oracle db, and replaced all occurences of "DefaultDS"
with jndi name of new datasource.
In my datasource is this:
<local-tx-datasource>
<jndi-name>testingDS</jndi-name>
so in my hsqldb-persistence-service.xml went this
<depends>jboss.jca:service=DataSourceBinding,name=testingDS</depends>
<attribute name="DataSource">java:/testingDS</attribute>
sounded reasonable to me, but server startup started complaining about missing DQL in jndi
(see lower). I've got no idea why is this occuring, since I consider made changes
irelevant to this. When hsqldb was used, there was no misconfiguration with dlq.
That's for started, and secondly, I do not understand, why DLQ is being looked up,
when there is <attribute
name="DefaultQueueJNDIContext">/queue</attribute>
Do you have any ideas what's wrong?
20:25:30,720 WARN [JmsActivation] Failure in jms activation
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@64e3f9(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)c99007
destination=java:/jms/queues/EiraNotificationQueue destinationType=javax.jms.Queue 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: DLQ not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.util.naming.Util.lookup(Util.java:222)
at
org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106)
at
org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82)
at
org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
at
org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)
at
org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)
at
org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/594177#594177]
Start a new discussion in JBoss Messaging at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]