Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Websphere 6.1.0.9 + RAD 7 - JSPG0049E: /jsp/test.jsp failed to compile :

232 views
Skip to first unread message

ponsu...@yahoo.co.in

unread,
Sep 5, 2008, 12:10:57 PM9/5/08
to
Attached the source jsp file also.When running it in the WAS 6.1,I am getting the following exception : (In source,else condition,
the bean define variable is not defined.Can you let me why its happening


[9/5/08 10:35:35:307 EDT] 00000028 WebApp E [Servlet Error]-[/jsp/test.jsp]: com.ibm.ws.jsp.JspCoreException: JSPG0049E: /jsp/test.jsp failed to compile :

JSPG0091E: An error occurred at line: 36 in the file: /jsp/test.jsp
JSPG0093E: Generated servlet error from file: /jsp/test.jsp

C:\RAD70\runtimes\base_v61\profiles\AppSrv01\temp\AIGM-WLM-12481ANode01\server1\TestWebEAR\TestWeb.war\jsp\_test.java : 133 : lengthWithoutInsuranceOptions cannot be resolved

at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:389)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:354)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:263)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:137)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:277)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3252)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:264)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

ponsu...@yahoo.co.in

unread,
Sep 5, 2008, 12:13:18 PM9/5/08
to
attached _test.java file.

Bruce

unread,
Sep 6, 2008, 5:56:10 AM9/6/08
to
The reference to lengthWithoutInsuranceOptions at line 133 cannot see the lengthWithoutInsuranceOptions declaration at line 109 because the declaration is in a block that is not visible to the reference. You need to move the declaration outside of the inner blocks.

I could not open the jsp attachment.

ponsu...@yahoo.co.in

unread,
Sep 8, 2008, 2:28:08 PM9/8/08
to
Attached the source file of test.jsp

trin-i...@trinition.org

unread,
Mar 2, 2009, 4:19:58 PM3/2/09
to
We're upgrading from WebSphere Portal 5.1 to WebSphere Portal 6.1, and we're encountering a similar problem. Our JSPs worked fine in 5.1, but now that we're moving to 6.1, we're encountering problems.

We've found other places where the 6.1 JSP compiler is more strict, but we've also found custom properties for the web container to make it work in a more forgiving 5.1 mode -- except for this one issue.

Did you find a solution?

0 new messages