This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have to deploy to a websphere box at another location. I am testing an application, developed with Jboss3.2.1 as application server, where it works just fine in my websphere18.104.22.168 environment on my desktop. I have a datasource that I set up in the administrative console with the JNDI name of jdbc/oel. I have tested the connection and it tests fine. As soon as I do something on the application that I am testing that has to access the database I get the following errors. If you look at the code below you will see why there are so many.
javax.naming.NameNotFoundException: Name not found in context "java:". . . javax.naming.NameNotFoundException: Name jdbc not found in context "java:". . . javax.naming.NameNotFoundException: Name jdbc not found in context "java:". . . A NamingException is being thrown from a javax.naming.Context implementation. Details follow: Context implementation: com.ibm.ws.naming.java.javaURLContextRoot Context method: wookup(Name) Context name: java: Target name: comp/env/jdbc/oel/ Other data: Exception stack trace: javax.naming.NotContextException: The object bound to comp/env/jdbc/oel in the context "java:" is not a context. . . javax.naming.NotContextException: The object bound to comp/env/jdbc/oel in the context "java:" is not a context. . . javax.naming.NameNotFoundException: Name not found in context "java:". . . A Reference object looked up from the context "java:" with the name "comp/env/jdbc/oel" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows: Reference Factory Class Name: com.ibm.ws.util.ResRefJndiLookupObjectFactory Reference Factory Class Location URLs: null Reference Class Name: java.lang.Object Type: ResRefJndiLookupInfo Content: com.ibm.ws.util.ResRefJndiLookupInfo@6e3151f4 ResRefJndiLookupInfo: Look up Name="jdbc/oel";JndiLookupInfo: jndiName="java:/jdbc/oel"; providerURL=""; initialContextFactory=""
One other question for anybody out there. Jboss has a web-console where I can look and see all kinds of settings on the app server and invoke some Mbean methods. Does Websphere have something like this?
Vijay S. Rathore
Joined: Oct 29, 2001
For WSAD you can use UTC to lookup JNDI references, and for Websphere Application server the information can be customized using Admin Console. I am not sure about any JMX support available with Websphere.
One more question, where are you testing your app, WSAD or after deploying it on Websphere. [ August 20, 2004: Message edited by: Vijay S. Rathore ]
Joined: Dec 12, 2003
I don't have WSAD. I am testing it after deploying to WAS.
We have an application running fine in WAS 5.1. Recently we have migrated the application to WAS 22.214.171.124. Since then, whenever I try to load the application in 6.1, I get the following error.
A Reference object looked up from the context "uat-rubis-1Node01Cell/nodes/uat-rubis-1Node01/servers/server1" with the name "ext/gedom" was sent to the JNDI Naming Manager and was returned unprocessed. Reference data follows:
Reference Factory Class Name: com.sun.jndi.fscontext.FSContextFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: com.sun.jndi.fscontext.FSContext
I have not changed anything on the application, and the application is still running fine in 5.1 environment.