[User] Name [COMM_TEST_JNDI] is not bound in this Context. Unable to find [COMM_TEST_JNDI]

Dave Woodman dave at naffnet.org.uk
Fri Dec 4 23:51:52 GMT 2020


Hi Sachin,

 

Looking at your context.xml I see that you have defined hostName - so far as
I recall this should be serverName. This may or may not be your issue but
you would not supply the startup logs - starting at a line that looks
similar to:

 

2020-12-04T23:23:27.289+0000 INFO
[net.openesb.standalone.naming.ContextProvider] (main) OESE-1400: Preparing
JNDI Naming Context from D:\R&Dtranings\OpenESB Cummunity edition\
OpenESB-SE-3.2.4\OE-Instance /config/context.xml.

 

and probably ending at a line that looks like:

 

2020-12-04T23:23:34.945+0000 INFO
[net.openesb.standalone.node.internal.InstanceNode] (main) OESE-1002:
Instance server initialized.

 

This is where you will find any errors arising from the processing of
context.xml and thus is where you may be able to learn what has happened - I
suggest that you look there. 

 

I have taken your path from the previous issue that you had - although I
would suggest avoiding paths with spaces or special characters such as &. 

 

I should point out that there are both training and professional support
available from Pymma - if you are using OpenESB professionally then at least
one of the two would be a sensible investment. 

 

Dave.

 

-----Original Message-----
From: User <user-bounces at lists.open-esb.net> On Behalf Of Sachin Mallarappa
Sent: 04 December 2020 11:48
To: user at lists.open-esb.net
Subject: Re: [User] Name [COMM_TEST_JNDI] is not bound in this Context.
Unable to find [COMM_TEST_JNDI]

 

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.InboundMessageProcess
or]

(Thread-50) Received in-only message.

2020-12-04T10:38:19.511+0000 INFO

[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcess
or]

(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.InboundMessageProcess
or]

(Thread-50) Using Jndi Name:: COMM_TEST_JNDI

2020-12-04T10:38:19.512+0000 SEVERE

[sun-database-binding.org.glassfish.openesb.databasebc.InboundMessageProcess
or]

(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.getDataSourceFromCo
ntext(InboundMessageProcessor.java:1146)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.getDatabaseConnecti
on(InboundMessageProcessor.java:1156)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.getDataAccessObject
(InboundMessageProcessor.java:678)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.processInOnly(Inbou
ndMessageProcessor.java:410)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.execute(InboundMess
ageProcessor.java:334)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.run(InboundMessageP
rocessor.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.InboundMessageProcess
or]

(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(Inbou
ndMessageProcessor.java:410)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.execute(InboundMess
ageProcessor.java:334)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.run(InboundMessageP
rocessor.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.getDataSourceFromCo
ntext(InboundMessageProcessor.java:1146)

                at

org.glassfish.openesb.databasebc.InboundMessageProcessor.getDatabaseConnecti
on(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/>
http://openesb-community-forum.794670.n2.nabble.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open-esb.net/pipermail/user/attachments/20201204/f4a9c160/attachment.htm>


More information about the User mailing list