facebook

JSP debugging with JBOSS3.2.3 with embedded Tomcat5.0

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #207079 Reply

    I have Eclipse 2.1 and MyEclipse plugin.

    The application compiles and is getting deployed in the JBOSS3.2.3. But when I have a break point in JSP, the app hangs for ever. May I know any pitfalls in this approach?

    #207080 Reply

    Scott Anderson
    Participant

    It’s most likely a problem with the version of the JVM you’re launching either Eclipse or JBoss with. Please post all the information we request in the Posting Guidelines thread and we’ll be able to help more.

    #207083 Reply

    thanks for your reply. Here are the details.

    – System Setup ——————————-
    Operating System and version: WinXP professional
    Eclipse version: 2.1.3
    Eclipse build id: 200403101828
    Fresh Eclipse install (y/n): Y
    If not, was it upgraded to its current version using the update manager?
    Other installed external plugins:
    Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: Seven (7)
    MyEclipse version: 2.7.1 build id 200403241200-2.7.1-GA
    Eclipse JDK version: 1.4.2_03
    Application Server JDK version: 1.4.2_03
    Are there any exceptions in the Eclipse log file?

    – Message Body ——————————-

    #207084 Reply

    I found the following error in the ECLIPSE log:

    !ENTRY org.eclipse.core.runtime 4 2 May 17, 2004 12:03:56.228
    !MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.core.runtime”.
    !STACK 0
    java.lang.UnsatisfiedLinkError: no net in java.library.path
    at java.lang.ClassLoader.loadLibrary(Unknown Source)
    at java.lang.Runtime.loadLibrary0(Unknown Source)
    at java.lang.System.loadLibrary(Unknown Source)
    at sun.security.action.LoadLibraryAction.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.PlainSocketImpl.<clinit>(Unknown Source)
    at java.net.ServerSocket.<init>(Unknown Source)
    at java.net.ServerSocket.<init>(Unknown Source)
    at java.net.ServerSocket.<init>(Unknown Source)
    at org.eclipse.tomcat.internal.PortTrackingServerSocketFactory.createSocket(PortTrackingServerSocketFactory.java:27)
    at org.apache.catalina.connector.http.HttpConnector.open(HttpConnector.java:948)
    at org.apache.catalina.connector.http.HttpConnector.initialize(HttpConnector.java:1128)
    at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:437)
    at org.eclipse.tomcat.internal.TomcatAppServer.start(TomcatAppServer.java:148)
    at org.eclipse.help.internal.appserver.AppserverPlugin.startWebappServer(AppserverPlugin.java:171)
    at org.eclipse.help.internal.appserver.AppserverPlugin.getAppServer(AppserverPlugin.java:53)
    at org.eclipse.help.internal.appserver.WebappManager.stop(WebappManager.java:58)
    at org.eclipse.help.internal.HelpSystem.shutdown(HelpSystem.java:160)
    at org.eclipse.help.internal.HelpPlugin.shutdown(HelpPlugin.java:100)
    at org.eclipse.core.internal.plugins.PluginRegistry$2.run(PluginRegistry.java:295)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
    at org.eclipse.core.internal.plugins.PluginRegistry$1.visit(PluginRegistry.java:308)
    at org.eclipse.core.internal.plugins.PluginRegistry.accept(PluginRegistry.java:58)
    at org.eclipse.core.internal.plugins.PluginRegistry.shutdownPlugins(PluginRegistry.java:311)
    at org.eclipse.core.internal.plugins.PluginRegistry.shutdown(PluginRegistry.java:277)
    at org.eclipse.core.internal.runtime.InternalPlatform.loaderShutdown(InternalPlatform.java:630)
    at java.lang.reflect.Method.invoke(Native Method)
    at org.eclipse.core.internal.boot.InternalBootLoader.shutdown(InternalBootLoader.java:1008)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:863)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at java.lang.reflect.Method.invoke(Native Method)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)

    #207085 Reply

    Scott Anderson
    Participant

    There have been some reported issues with certain versions of JDK 1.4.2 and the Eclipse debugger. Can you try running JBoss with JDK 1.4.1?

    Also, JBoss 3.2.3 doens’t come with Tomcat 5.0, so I assume you integrated it yourself? Is that correct? If not, that’s the reason that debugging isn’t working as Tomcat 4 does not support source level JSP debug.

    #207087 Reply

    Yes, you are absolutely right. I built the TOMCAT5.0 version with JBOss3.2.3. I have also attached the ERROR in eclipse log some minutes back. Doyou find anything there I have done wrong? If no, I will try to switch the JDK.

    thanks a million for our lightning response.
    S

    #207096 Reply

    Scott Anderson
    Participant

    The error log above is just some problem with Help not being able to spin up in Eclipse properly. It’s unrelated to what you’re seeing. I’d suggest JDk 1.4.1 because we’ve seen exactly the same problem with WebLogic and certain versions of 1.4.2. Changing to 1.4.1 fixed the issue. Perhaps a later version of 1.4.2 would also. As another approach, you can download the source for JBoss 3.2.4 which already has Tomcat 5 integrated. You’ll need to compile it yourself, but it’s quite easy as I’ve even done it. 😉 The instructions are located here: https://www.genuitec.com/forums/topic/tomcat-5-jboss-3-2-4-jsp-debugging-support-closed/

    Also, some additional insight on doing the 3.2.3 / Tomcat 5 work is available here: https://www.genuitec.com/forums/topic/using-tomcat-5-with-jboss-3-2-x-closed/

    #207098 Reply

    Thanks Scott, There are 2 issues here.
    1. I cannot go back to JDK 1.4.1 becasue some of my api s (from other teams) have specifically 1.4.2_03 requirement.
    2. The management is not “happy” to go to JBoss3.2.4 as it is still in RC. I have no problem in going to 3.2.4. I have miserably “failed” in convincing the management.
    Thanks once again. Still trying to get a break through.
    Thank you once again.
    S

    #207100 Reply

    Scott,
    Do you feel upgrading my Eclipse to 3.x will be of any help. Since this is a upgrade on IDE, I can convince my top management easily.

    #207103 Reply

    Scott Anderson
    Participant

    No, I certainly would not upgrade to the 3.0 milestone builds for production work. It still has a long way to go to become stable.

    The management is not “happy” to go to JBoss3.2.4 as it is still in RC.

    Interesting, but they’ll happily let you customize 3.2.3 with a Tomcat 5 integration? Rather peculiar. 🙂

    Have you inadvertantly turned off JSP debug compilation in Tomcat 5’s web.xml’s entry for org.apache.jasper.servlet.JspServlet?

    #207105 Reply

    Scott,
    Here is the snippet

    <servlet>
    <servlet-name>jsp</servlet-name>
    <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
    <init-param>
    <param-name>logVerbosityLevel</param-name>
    <param-value>DEBUG</param-value>
    </init-param>
    <load-on-startup>3</load-on-startup>
    </servlet>

    </servlet>

    #207107 Reply

    Scott,
    Since becasue I have tiles defined in my index.jsp, is there any chance the debugger will get hung?

    #207108 Reply

    Scott Anderson
    Participant

    Since becasue I have tiles defined in my index.jsp, is there any chance the debugger will get hung?

    That shouldn’t be the case. What I’d suggest you do to test that is create a new web project with one JSP (the default created by the wizard is fine) and deploy it. Activate your JSP page with a browser and make sure it comes up. Then, set a breakpoint and refresh your browser. Did the breakpoint get hit?

Viewing 13 posts - 1 through 13 (of 13 total)
Reply To: JSP debugging with JBOSS3.2.3 with embedded Tomcat5.0

You must be logged in to post in the forum log in