[User] Name [COMM_TEST_JNDI] is not bound in this Context. Unable to find [COMM_TEST_JNDI]
Sachin Mallarappa
sachin.m at inspirage.com
Fri Dec 4 11:47:57 GMT 2020
Dave,
it is the same error I see at the start up time,
Am i missing some configuration here, or the changes should be done at
product level ?
-------------------------------- Log --------------------------------------
2020-12-04T10:38:19.510+0000 INFO
[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcessor]
(Thread-50) Received in-only message.
2020-12-04T10:38:19.511+0000 INFO
[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcessor]
(Thread-50) Throttling configuration is not defined on the endpoint
2020-12-04T10:38:19.512+0000 INFO
[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcessor]
(Thread-50) Using Jndi Name:: COMM_TEST_JNDI
2020-12-04T10:38:19.512+0000 SEVERE
[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcessor]
(Thread-50) Error occured while looking up jndi resource with jndi
name.COMM_TEST_JNDI
javax.naming.NameNotFoundException: Name [COMM_TEST_JNDI] is not bound in
this Context. Unable to find [COMM_TEST_JNDI].
at org.apache.naming.NamingContext.lookup(NamingContext.java:819)
at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataSourceFromContext(InboundMessageProcessor.java:1146)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDatabaseConnection(InboundMessageProcessor.java:1156)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataAccessObject(InboundMessageProcessor.java:678)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.processInOnly(InboundMessageProcessor.java:410)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.execute(InboundMessageProcessor.java:334)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.run(InboundMessageProcessor.java:251)
at java.lang.Thread.run(Thread.java:745)
2020-12-04T10:38:19.513+0000 SEVERE
[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcessor]
(Thread-50) Unexpected exception Occured while processing the MEP.
javax.jbi.messaging.MessagingException: Error occured while looking up jndi
resource with jndi name.COMM_TEST_JNDI
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataAccessObject(InboundMessageProcessor.java:728)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.processInOnly(InboundMessageProcessor.java:410)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.execute(InboundMessageProcessor.java:334)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.run(InboundMessageProcessor.java:251)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.naming.NameNotFoundException: Name [COMM_TEST_JNDI] is not
bound in this Context. Unable to find [COMM_TEST_JNDI].
at org.apache.naming.NamingContext.lookup(NamingContext.java:819)
at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataSourceFromContext(InboundMessageProcessor.java:1146)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDatabaseConnection(InboundMessageProcessor.java:1156)
at
org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataAccessObject(InboundMessageProcessor.java:678)
... 4 more
--
Sent from: http://openesb-community-forum.794670.n2.nabble.com/
More information about the User
mailing list