sreekailas balan

Greenhorn
+ Follow
since Sep 30, 2002
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by sreekailas balan

Hi All,
My Application is running on WebSphere Application Server 4.0.1 with DB2 as back end. I tried to install an Ear file which is running fine with WSAD test environment into WAS . I get the home page correctly with out any errors. When I click on a link which instantiates a EJB i am getting a naming exception. The exact error is as given below.

NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.java.javaURLContextRoot
Context method: lookup(Name)
Context name: java:
Target name: comp/env/ejb/QuickQuote
Other data:
Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while attempting to get an instance of the object for the specified reference object. Root exception is javax.naming.NameNotFoundException: ejb/com/aig/aandh/quickquote/bus/ejb/QuickQuoteHome
at com.ibm.ejs.ns.jndi.CNContextImpl.doLookup(CNContextImpl.java:1435)
at com.ibm.ejs.ns.jndi.CNContextImpl.lookup(CNContextImpl.java:1115)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:193)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:308)
at com.ibm.ws.naming.urlbase.UrlContextHelper.isReference(UrlContextHelper.java:115)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:229)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1181)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1158)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1210)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.aig.aandh.util.ServiceLocator.getHome(ServiceLocator.java:152)
at com.aig.aandh.bus.QuickQuoteBD.<init>(QuickQuoteBD.java:55)
at com.aig.aandh.quickquote.presentation.actions.InitialQuestionsAction.performNew(InitialQuestionsAction.java:124)
at com.aig.aandh.quickquote.presentation.actions.InitialQuestionsAction.perform(InitialQuestionsAction.java:72)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:499)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:278)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:105)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:123)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

Can anyone throw light on to this probelem. I tried almost all options but could not get any solution. Please help me out.
Thanks in advance
Regards
17 years ago
We have detected the problem as a problem with the page editor. If we are changing the page editor to other editors like Textpad or Edit plus the jsp works fine. Can any one tell why the problem with the page editor in WSAD?
Thanks
17 years ago
I am getting the following error while doing ejbc. Can anyone tell me ehy this error is coming? I am using weblogic 6.0

ERROR: Error from ejbc: Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml
'. The error was:
weblogic.ejb20.cmp.rdbms.finders.IllegalExpressionException:
While trying to process Finder
Method Name: findByName
Parameter Types: (java.lang.String)
EJB Query: SELECT OBJECT(a) FROM CourseBean As a WHERE courseName = ?1
)
Could not parse EJB QL expression: SELECT OBJECT(a) FROM CourseBean As a WHERE courseName = ?1

Thanks
Thanks for the replies. Note that I am using WSAD and not WAS. The file name is given as .jsp only. It is also strange that if I develop a Jsp in any other editor and drag it into wsad it is working fine. But once I make any change and save the file it stops the jsp compilation and ignores all the jsp tags. It considers the file as a normal html file and prints out all the jsp code in the source. Does any body of you notice this with WSAD? In our office a lot of us are facing the problem.. I want to know whether it is a problem with WSAD or something has gone wrong in my settings
Thanks
17 years ago
Thanks for the reply.
It is already in the jsp scriplet tag.
My jsp is like this
<HTML>
<HEAD>
<TITLE>TestJsp</TITLE>
</HEAD>
<BODY>
<% out.println("THIS IS A SIMPLE JSP");%>
</BODY>
</HTML>
But the page generated does not compile the jsp and generates the html with the source code as below
<HTML>
<HEAD>
<TITLE>TestJsp</TITLE>
</HEAD>
<BODY>
<% out.println("THIS IS A SIMPLE JSP");%>
</BODY>
</HTML>
There is no jsp comiplation occuring. Can you tell me what could be the reason?
Thanks
17 years ago
I am noticing a strange problem with WSAD while working with JSP files.
I have created a simple JSP file and try running it on the server, the result is a HTML page even with the JSP tags.
Eg:
My JSP File Looks like
HEAD
TITLE
TestJsp
/TITLE
/HEAD
BODY
out.println("THIS IS A SIMPLE JSP");
/BODY

(please ignore the syntax)
If we try running this file using a server configured in WSAD the result page will be blank and the source of the HTML file generated looks the same as the JSP file .
Does any one has a solution to this??
Thanks in Advance
17 years ago