APAR status |
Closed as program error.
| Error description
system environment is:
Server Windows 2000 Server SP1
WebSphere Application Server Advanced Edition 3.5.3
IBM Distributed Debugger 8.5.8
Client Windows 2000 Professional SP1
WebSphere Studio Advanced Edition 3.5.3
IBM Distributed Debugger 8.5.8
When try to debug .jsp file, OLT debugger requests
"service:org.apache.jasper.runtime.JspServlet:machine_name:system environment is:Server Windows 2000 Server SP1WebSphere Application Server Advanced Edition 3.5.3IBM Distributed Debugger 8.5.8Client Windows 2000 Professional SP1WebSphere Studio Advanced Edition 3.5.3IBM Distributed Debugger 8.5.8When try to debug .jsp file, OLT debugger requests
_1978646696:0" for stepin breadkpoint. If CANCEL this request,
it requests us .java file (.jsp compiled source code).
And furthermore, debugger process does not shutdown correctly.
.
Here's summary by Developer:"service:org.apache.jasper.runtime.JspServlet:machine_name:_1978646696:0" for stepin breadkpoint. If CANCEL this request,it requests us .java file (.jsp compiled source code).And furthermore, debugger process does not shutdown correctly..
1. Debugging JSP1.1 - on 3.5.3, while debugger requests for the
JspServlet, browse and pick the JSP file. Initially, it would
not allow you to set break-points. However, Double-click on the
first line "with a red-dot + green arrow" to remove the red dot.
Now, would be able to set break points.
However, initially Debugger should not be requesting for the
servlet - this should be a bug. This seems more like Distributed
Debugger issue and WAS may not be involved here.
2. Debugger Hanging with a message "application busy/running"- Here's summary by Developer:1. Debugging JSP1.1 - on 3.5.3, while debugger requests for theJspServlet, browse and pick the JSP file. Initially, it wouldnot allow you to set break-points. However, Double-click on thefirst line "with a red-dot + green arrow" to remove the red dot.Now, would be able to set break points.However, initially Debugger should not be requesting for theservlet - this should be a bug. This seems more like DistributedDebugger issue and WAS may not be involved here.2. Debugger Hanging with a message "application busy/running"- Local fix
Use .java file Problem summary
Debug support is needed in JSP 1.1 page compiler for standard
and advanced edition in 3.5 fixpack 4. Problem conclusion
the following:
com/ibm/servlet/debug/OLTHash.java
com/ibm/servlet/debug/OLTManager.java
org/apache/jasper/compiler/Compiler.java
org/apache/jasper/compiler/JspReader.java
com/ibm/servlet/debug/OLTServletManager.java
The defect number is 90363 the following:com/ibm/servlet/debug/OLTHash.javacom/ibm/servlet/debug/OLTManager.javaorg/apache/jasper/compiler/Compiler.javaorg/apache/jasper/compiler/JspReader.javacom/ibm/servlet/debug/OLTServletManager.javaThe defect number is 90363 Temporary fixComments
APAR information | APAR number | PQ48831 | Reported component name | WAS STANDARD NT | Reported component ID | 5648C8301 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-05-17 | Closed date | 2001-05-24 | Last modified date | 2001-05-24 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS STANDARD NT | Fixed component ID | 5648C8301 |
Applicable component levels | R350 PSY | UP |
|