With visual age 302

Question

Hi,
I am using weblogic5.1 Integration Kit for VisualAge 302. After I
followed the instruction and try to start weblogic in VisualAge,
everything looks fine. But if I try to invoke http://localhost:7001/
from browser, I got the following error:
Fri Aug 25 15:30:04 EDT 2000:<I> <ListenThread> Listening on port: 7001
Fri Aug 25 15:30:04 EDT 2000:<I> <SSLListenThread> Listening on port:
7002
Fri Aug 25 15:30:05 EDT 2000:<I> <WebLogicServer> WebLogic Server
started
Fri Aug 25 15:30:25 EDT 2000:<I> <NT Performance Pack> Allocating: '2'
NT reader threads
Fri Aug 25 15:30:25 EDT 2000:<E> <Kernel> ExecuteRequest failed.
java.lang.RuntimeException: Socket:
'weblogic.socket.MuxableSocketHTTP@2111 - idle timeout: '60', socket
timeout: '5000'' is invalid.
java.lang.Throwable(java.lang.String)
java.lang.Exception(java.lang.String)
java.lang.RuntimeException(java.lang.String)
void
weblogic.socket.NTSocketMuxer.register(weblogic.socket.MuxableSocket)
void weblogic.socket.JVMSocketManager.accept(java.net.Socket)
void
weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(weblogic.kernel.ExecuteThread)
void weblogic.kernel.ExecuteThread.run()
Any idea?
Thanks
[email protected]

Answer 1

IBMs VAJ does not provide you with a JSP designer, but it does let you run JSPs under WebSPhere test environment.
Go to the folder
IBM/VisualAge For Java/ide/project_resources/IBM WebSphere Test Environment/hosts/default_hosts/default_app/webThis is the root directory for putting JSPs. If you make a directory called myjsps in here, and put myJsp.jsp in the directory then when you start the servlet engine of the WebShpere test environment you can put
"http://localhost:8080/myjsps/myJsp.jsp"in the URL and your JSP will be compiled into a servlet in the "JSP Page Compile Generated Code" project. You can enter JSP Execution Monitor options (in the WTE ControlCenter), which will bring up a split pane with the JSP on one side, and the compiled Java on the other and will allow you to debug the JSP.
You are a bit shafted if VAJ was unable to compile your JSP into a servlet - as you get no information on what exactly about the JSP is causing the problem. However, this is all integrated into the debugging environment so you can completely debug the servlet and any Java code it calls.
If you don't know about the WTE then let me know, but I'm assuming that you do.