New Version - HTTP 500 error

christopherb

New install with derby to test the new version i am getting a HTTP 500 errors when loading the sample applications or even a simple test one. Here is the error.....
org.apache.jasper.JasperException: Unable to compile class for JSP:

An error occurred at line: 8 in the generated java file
Only a type can be imported. com.bas.webapp.actions.ActionUtils resolves to a package

An error occurred at line: 8 in the jsp file: /standardStartHead.jsp
ActionUtils cannot be resolved
5: -->
6:
7: <%
8: ActionUtils.generateJavaScriptInitFunction (pageContext);
9: %>

An error occurred at line: 36 in the jsp file: /standardStartTail.jsp
ActionUtils cannot be resolved
33: String contextId = request.getParameter ("UIContextId");
34: if (contextId != null)
35: {
36: UIContext baseCtx = ActionUtils.getBaseContext (contextId, session);
37: if (baseCtx != null && baseCtx.isInProcessFrame ())
38: {
39: pageContext.setAttribute("inProcessFrame_bean", "true", PageContext.PAGE_SCOPE);

Stacktrace:
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:93)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:435)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:298-)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:277)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:265)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:302)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
com.cc.framework.adapter.struts.FWRequestProcessor.processForwardConfig(Unknown Source)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs.

/////////////////////////////////////////////////////

Here is the Server log

/////////////////////////////////////////////////////
2008-07-16 12:28:46,252 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2008-07-16 12:28:46,252 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.CloseMsg7261893[msgType: m_connectionClosing, msgID: 194, error: null]
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
at org.jboss.mq.il.uil2.SocketManager.sendReply(SocketManager.java:239)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:128-)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:396)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:392)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748-)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,283 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
at org.jboss.mq.il.uil2.SocketManager.access$800(SocketManager.java:52)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:409)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:392)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748-)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,298 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2313)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2380)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2452)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2601)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:317)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,298 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2008-07-16 12:28:46,345 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.CloseMsg18611390[msgType: m_connectionClosing, msgID: 197, error: null]
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
at org.jboss.mq.il.uil2.SocketManager.sendReply(SocketManager.java:239)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:128-)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:396)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:392)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748-)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,345 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2008-07-16 12:28:46,345 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2313)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2380)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2452)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2601)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:317)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,345 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
at org.jboss.mq.il.uil2.SocketManager.access$800(SocketManager.java:52)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:409)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:392)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748-)
at java.lang.Thread.run(Thread.java:534)
2008-07-16 12:28:46,377 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run

christopherb

Nevermind.... i was using the incorrect login url

My bad!

aware_support

Just a note for all other users of the beta version as we are getting many reports like this.

THE LOGIN URL HAS CHANGED! Please read the release notes.

The old URL will still be supported and your old applications will retain exactly the same look and feel and functionality as before if you login using the old URL. The current beta version, though, has a bug that prevents the old URL from opening the startup screen. This will be fixed in the final release.

This is what many beta testers are experiencing now - they log in using the old URL expecting to see the new version and see the above mentioned bug instead.

So once again PLEASE READ THE RELEASE NOTES IN THE ROOT FOLDER!

jclark58

Just a note for all other Developers of the beta version - if you are getting many reports like this....

ITS TIME THE README mechanism IS CHANGED!
Apart from the fact that Real Programmers dont read the release notes anyway, well not until they have to - Readme files would be better of displayed as part of the install process or Immediately on startup .

Maybe the decision to display an application should be a command line option - to vary from the normal expectation or a system setting to set the default.

Remember the the core of user interface design (of anything) is to identify and meet the users expectations

So once again PLEASE READ THE FEEDBACK YOU ARE GETTING!

<GRIN>

aware_support

The Readme mechanism is for NEW users of the system and will continue to be so. Release Notes is for EXISTING users of the system.

Many people do not read these notes anyway. But beta testers have to! This is a beta version only and as we said in the release notes the official documentation has not been updated yet, nor the README notes. The only piece of documentation that has been updated specifically for beta testers is Release Notes and this is why we ask you to read them because otherwise there is no way for us to say to BETA TESTERS ONLY what we want to say about this version.

Thanks for understanding.