Re: JNDI lookup on WAS

We ran into something similar at a client site. Actually our HTTP Server was
having trouble accessing an external name server, rather than WAS. It turned out
that a firewall was blocking it. The client had a policy against allowing their
IBM i server to connect to other servers on the Internet.

-Nathan




----- Original Message ----
From: "TAllen@xxxxxxxxxxxx" <TAllen@xxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Tue, February 15, 2011 10:56:43 AM
Subject: [WEB400] JNDI lookup on WAS

Has anyone successfully used a JNDI lookup on a Websphere application
server (WAS)?
I've got it running fine in the Websphere Studio development environment
but get a javax.naming.NameNotFoundException error when deployed to WAS.

It seems to have something to do with the scope but it looks right to me.
I noticed that the stack trace has the context as:
<Servername>/nodes/<Servername>/servers/<Servername>

When I look at the name space bindings in the WAS console I see:
cells/<Servername>/nodes/<Servername>/servers/<Servername>

Note the prepended "cells" in the scope. I don't know where that came
from.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx



This communication and any transmitted documents are intended to be
confidential. If there is a problem with this transmission, please contact the
sender. If the reader of this message is not the intended recipient, or the
employee or agent responsible to deliver it to the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.