Problems debugging Struts-app inside Intellij
I manage to get it up running with the classes are deployed inside a jar, - but when compiling the action-classes to .class files in the WEB-INF/classes I get this error message when starting the application inside Intellij. I get this error message even it the classes exists in the jar in the WEB-INF/lib. Any clues? Geir A. DEBUG 19:24:07,824 [main] no.aftenposten.common.www.config.WebConfiguration - load: loading: C:\JavaAften\src\webidam\web\webapps\webidam\WEB-INF\conf\webidam.proper ties INFO 19:24:07,854 [main] org.apache.struts.util.PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true ERROR 19:24:08,326 [main] org.apache.commons.digester.Digester - Begin event threw exception java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: no/aftenposten/adk/idam/czar/struts/Dummyform (wrong name: no/aftenposten/adk/idam/czar/struts/DummyForm) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
RE: Problems debugging Struts-app inside Intellij
You should rename the file no/aftenposten/adk/idam/czar/struts/Dummyform.java to DummyForm.java, may be. -Message d'origine- De: Arnesen, Geir [mailto:[EMAIL PROTECTED]] Date: mercredi 5 février 2003 19:34 À: [EMAIL PROTECTED] Objet: Problems debugging Struts-app inside Intellij I manage to get it up running with the classes are deployed inside a jar, - but when compiling the action-classes to .class files in the WEB-INF/classes I get this error message when starting the application inside Intellij. I get this error message even it the classes exists in the jar in the WEB-INF/lib. Any clues? Geir A. DEBUG 19:24:07,824 [main] no.aftenposten.common.www.config.WebConfiguration - load: loading: C:\JavaAften\src\webidam\web\webapps\webidam\WEB-INF\conf\webi dam.proper ties INFO 19:24:07,854 [main] org.apache.struts.util.PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true ERROR 19:24:08,326 [main] org.apache.commons.digester.Digester - Begin event threw exception java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: no/aftenposten/adk/idam/czar/struts/Dummyform (wrong name: no/aftenposten/adk/idam/czar/struts/DummyForm) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader. java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems debugging Struts-app inside Intellij
-Original Message- From: Arnesen, Geir [mailto:[EMAIL PROTECTED]] I manage to get it up running with the classes are deployed inside a jar, - but when compiling the action-classes to .class files in the WEB-INF/classes I get this error message when starting the application inside Intellij. I get this error message even it the classes exists in the jar in the WEB-INF/lib. Any clues? Yeah. Without knowing anything about IntelliJ, it seems pretty likely that you have a case matching problem. You have a class named Dummyform or DummyForm, and you're referring to it in the wrong case from somewhere. Check all your references and make sure that the case matches. DEBUG 19:24:07,824 [main] no.aftenposten.common.www.config.WebConfiguration - load: loading: C:\JavaAften\src\webidam\web\webapps\webidam\WEB-INF\conf\webidam.proper ties INFO 19:24:07,854 [main] org.apache.struts.util.PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true ERROR 19:24:08,326 [main] org.apache.commons.digester.Digester - Begin event threw exception java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: no/aftenposten/adk/idam/czar/struts/Dummyform (wrong name: no/aftenposten/adk/idam/czar/struts/DummyForm) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SV: Problems debugging Struts-app inside Intellij
Thanks a lot, - you got it I struggled a lot with this stupid mistyping... Worked now perfect while debugging.. Geir -Opprinnelig melding- Fra: ROSSEL Olivier [mailto:[EMAIL PROTECTED]] Sendt: 5. februar 2003 19:36 Til: 'Struts Users Mailing List' Emne: RE: Problems debugging Struts-app inside Intellij You should rename the file no/aftenposten/adk/idam/czar/struts/Dummyform.java to DummyForm.java, may be. -Message d'origine- De: Arnesen, Geir [mailto:[EMAIL PROTECTED]] Date: mercredi 5 février 2003 19:34 À: [EMAIL PROTECTED] Objet: Problems debugging Struts-app inside Intellij I manage to get it up running with the classes are deployed inside a jar, - but when compiling the action-classes to .class files in the WEB-INF/classes I get this error message when starting the application inside Intellij. I get this error message even it the classes exists in the jar in the WEB-INF/lib. Any clues? Geir A. DEBUG 19:24:07,824 [main] no.aftenposten.common.www.config.WebConfiguration - load: loading: C:\JavaAften\src\webidam\web\webapps\webidam\WEB-INF\conf\webi dam.proper ties INFO 19:24:07,854 [main] org.apache.struts.util.PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true ERROR 19:24:08,326 [main] org.apache.commons.digester.Digester - Begin event threw exception java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: no/aftenposten/adk/idam/czar/struts/Dummyform (wrong name: no/aftenposten/adk/idam/czar/struts/DummyForm) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader. java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: please, help! debugging Struts with VisualAge for Java and Tomcat
I am using VAJ4. It has Websphere Test Environment. I use that and then am able to debug the webapp. I don't know if VAJ has a tomcat plugin, but that's probably what the article Adrian sent you is all about. If you want the full installation instructions for websphere test environment and getting struts running in VAJ, gimme a shout I'll send it to you. cheers Darryl -Original Message- From: Adrian Brown [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 27, 2002 3:20 AM To: Struts Users Mailing List Subject: Re: please, help! debugging Struts with VisualAge for Java and Tomcat Hi Patria, I found this article by Sheldon Wosnick to be of great assistance. http://www7.software.ibm.com/vad.nsf/data/document2389?OpenDocument Let me know if you need any other help. Adrian --- Patria Lukman [EMAIL PROTECTED] wrote: Hello everyone I really don't want to bother you people, since this question might be addressed to VisualAge users... But I figure out that in this list there might be some people using it as a development tool. I have VAJ 3.5 Professional edition and Tomcat 4.0.b integrated with it... How can debug a Struts application using VAJ debugging facilities? I have followed the articles found in the Net but without much avail... Thank you very much for your time. P __ Post your ad for free now! http://personals.yahoo.ca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] http://digital.yahoo.com.au - Yahoo! Digital How To - Get the best out of your PC! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
please, help! debugging Struts with VisualAge for Java and Tomcat
Hello everyone I really don't want to bother you people, since this question might be addressed to VisualAge users... But I figure out that in this list there might be some people using it as a development tool. I have VAJ 3.5 Professional edition and Tomcat 4.0.b integrated with it... How can debug a Struts application using VAJ debugging facilities? I have followed the articles found in the Net but without much avail... Thank you very much for your time. P __ Post your ad for free now! http://personals.yahoo.ca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: please, help! debugging Struts with VisualAge for Java and Tomcat
Hi Patria, I found this article by Sheldon Wosnick to be of great assistance. http://www7.software.ibm.com/vad.nsf/data/document2389?OpenDocument Let me know if you need any other help. Adrian --- Patria Lukman [EMAIL PROTECTED] wrote: Hello everyone I really don't want to bother you people, since this question might be addressed to VisualAge users... But I figure out that in this list there might be some people using it as a development tool. I have VAJ 3.5 Professional edition and Tomcat 4.0.b integrated with it... How can debug a Struts application using VAJ debugging facilities? I have followed the articles found in the Net but without much avail... Thank you very much for your time. P __ Post your ad for free now! http://personals.yahoo.ca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] http://digital.yahoo.com.au - Yahoo! Digital How To - Get the best out of your PC! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Where can I find info Debugging Struts?
How do get Struts to write out more verbose debugging information? Where can I find better documentation struts-config.xml ? Struts does not seem to finding my Action? I have copied the struts.jar into the /WEB-INF/lib and find that I getting a class not found exception for Root cause: java.lang.NoClassDefFoundError: org/apache/struts/action/ActionForm at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at org.apache.tomcat.loader.AdaptiveClassLoader.loadClass(AdaptiveClassLoader.java:446) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:120) at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:563) at moar._0002fmoar_0002freconcil_0002dleft_0002dsource_0002ejspreconcil_0002dleft_0002dsource_jsp_10._jspService(_0002fmoar_0002freconcil_0002dleft_0002dsource_0002ejspreconcil_0002dleft_0002dsource_jsp_10.java:186) -- Peter Pilgrim | |++44 (0)207-545-9923 \ \ ___ / / ... . - ( * ) --- -- _Cafe_Savannah,_San Antonio,Ibiza__ -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: Where can I find info Debugging Struts? {SOLVED REALLY]
15 minute detention after class. I must remember to: NOT TO EDIT THE TOMCAT LAUNCH SCRIPT ANYMORE AND REMEMBER TO BLANK OUT THE CLASSPATH IF I DO! NOT TO EDIT THE TOMCAT LAUNCH SCRIPT ANYMORE AND REMEMBER TO BLANK OUT THE CLASSPATH IF I DO! NOT TO EDIT THE TOMCAT LAUNCH SCRIPT ANYMORE AND REMEMBER TO BLANK OUT THE CLASSPATH IF I DO! (x 100 ) Sorry Sir. I solved the problem really Sir -- Peter Pilgrim | |++44 (0)207-545-9923 \ \ ___ / / ... . - ( * ) --- -- _Cafe_Savannah,_San Antonio,Ibiza__ Message History From: Peter Pilgrim/DMGIT/DMG UK/DeuBa@DMG UK on 30/08/2001 12:36 --CUT-- How do get Struts to write out more verbose debugging information? Where can I find better documentation struts-config.xml ? Struts does not seem to finding my Action? I have copied the struts.jar into the /WEB-INF/lib and find that I getting a class not found exception for Root cause: java.lang.NoClassDefFoundError: org/apache/struts/action/ActionForm at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:486) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at org.apache.tomcat.loader.AdaptiveClassLoader.loadClass(AdaptiveClassLoader.java:446) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:120) at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:563) at moar._0002fmoar_0002freconcil_0002dleft_0002dsource_0002ejspreconcil_0002dleft_0002dsource_jsp_10._jspService(_0002fmoar_0002freconcil_0002dleft_0002dsource_0002ejspreconcil_0002dleft_0002dsource_jsp_10.java:186) --CUT-- -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Debugging struts?
Hi. I'm thinking of trying to debug my struts stuff in Netbeans. Does anyone use this successfully, and do you know if it works with Tomcat 3.3 m2? Thanks, Dave
Re: Debugging struts exceptions
On Tue, 10 Apr 2001, Will Spies/Towers Perrin wrote: I actually found a good solution to this. Looking at the taglib code I found this code all over the place when they throw exceptions: pageContext.setAttribute(Action.EXCEPTION_KEY, e, PageContext.REQUEST_SCOPE); I've just added a note to the documentation about this. If you declare an error page, you can process the actual exception by retrieving the exception itself under request attribute "org.apache.struts.action.EXCEPTION". Craig McClanahan
RE: Debugging struts exceptions - get SP9 for WL5.1
It appears that SP9 for WebLogic5.1 (recently released) fixes this problem. The informative exception is now reported! -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Monday, April 09, 2001 10:33 PM To: [EMAIL PROTECTED] Subject: Re: Debugging struts exceptions On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote: I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) You might want to complain to WebLogic about this. The actual exception that is thrown *does* contain a more useful error message -- it's just that WebLogic is not telling you about it. Alternatively, you can declare an error page to handle runtime errors. The Struts tags that throw exceptions store a copy of the underlying exception as a request attribute under key "org.apache.struts.action.EXCEPTION", so you can display it yourself. Craig McClanahan
Re: Debugging struts exceptions
I actually found a good solution to this. Looking at the taglib code I found this code all over the place when they throw exceptions: pageContext.setAttribute(Action.EXCEPTION_KEY, e, PageContext.REQUEST_SCOPE); I don't know if this is documented somewhere. Probably it is and I just missed it. However, this allowed me to create an errorPage which displays *THIS* exception. So, now all my JSPs have an errorPage declared that that yanks this exception out of the request and displays it. Although sometimes this exception isnt' great it's far far better than the original one. Thanks, I forgot to post this. Will To: [EMAIL PROTECTED] "Craig R.cc: (bcc: Will Spies/Towers Perrin) McClanahan" Subject: Re: Debugging struts exceptions craigmcc@apa che.org 04/09/01 10:32 PM Please respond to struts-user On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote: I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) You might want to complain to WebLogic about this. The actual exception that is thrown *does* contain a more useful error message -- it's just that WebLogic is not telling you about it. Alternatively, you can declare an error page to handle runtime errors. The Struts tags that throw exceptions store a copy of the underlying exception as a request attribute under key "org.apache.struts.action.EXCEPTION", so you can display it yourself. Craig McClanahan
RE: Debugging struts exceptions
What exactly do you mean by "declare an error page"? Is this a JSP that is specified as a global forward in struts-config.xml or a servlet param in web.xml? thanks, Bob -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 10, 2001 7:33 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Debugging struts exceptions I actually found a good solution to this. Looking at the taglib code I found this code all over the place when they throw exceptions: pageContext.setAttribute(Action.EXCEPTION_KEY, e, PageContext.REQUEST_SCOPE); I don't know if this is documented somewhere. Probably it is and I just missed it. However, this allowed me to create an errorPage which displays *THIS* exception. So, now all my JSPs have an errorPage declared that that yanks this exception out of the request and displays it. Although sometimes this exception isnt' great it's far far better than the original one. Thanks, I forgot to post this. Will To: [EMAIL PROTECTED] "Craig R.cc: (bcc: Will Spies/Towers Perrin) McClanahan" Subject: Re: Debugging struts exceptions craigmcc@apa che.org 04/09/01 10:32 PM Please respond to struts-user On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote: I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) You might want to complain to WebLogic about this. The actual exception that is thrown *does* contain a more useful error message -- it's just that WebLogic is not telling you about it. Alternatively, you can declare an error page to handle runtime errors. The Struts tags that throw exceptions store a copy of the underlying exception as a request attribute under key "org.apache.struts.action.EXCEPTION", so you can display it yourself. Craig McClanahan
RE: Debugging struts exceptions
I mean in all your JSPs use the following tag in the beginning:
%@ page language="java" errorPage="error.jsp" %
Then, in error.jsp you can use the following code:
% Throwable strutsException = (Throwable) request.getAttribute
("org.apache.struts.action.EXCEPTION");%
% if ( strutsException != null ) {%
pStruts trace was: brpre
%=getStackTraceAsString(strutsException)%b
%} else {%
pNo Struts trace
%}%
%!
String getStackTraceAsString(Throwable e)
{
ByteArrayOutputStream ostr = new ByteArrayOutputStream();
e.printStackTrace(new PrintStream(ostr));
return(ostr.toString());
}
%
Note: this is just a snipet of the error.jsp but this should give you the
idea. You'll find more info on the errorPage directive in the JSP guides.
The only reason I used Throwable above rather than the struts exception
itself was because I already had this method and was using it for other
exceptions.
To:
[EMAIL PROTECTED]
[EMAIL PROTECTED]cc: (bcc: Will Spies/Towers
Perrin)
elheim.com Subject: RE: Debugging
struts exceptions
04/10/01 09:15 AM
Please respond to
struts-user
What exactly do you mean by "declare an error page"? Is this a JSP that is
specified as a global forward in struts-config.xml or a servlet param in
web.xml?
thanks,
Bob
-Original Message-
From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 7:33 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Debugging struts exceptions
I actually found a good solution to this. Looking at the taglib code I
found this code all over the place when they throw exceptions:
pageContext.setAttribute(Action.EXCEPTION_KEY, e,
PageContext.REQUEST_SCOPE);
I don't know if this is documented somewhere. Probably it is and I just
missed it. However, this allowed me to create an errorPage which displays
*THIS* exception. So, now all my JSPs have an errorPage declared that that
yanks this exception out of the request and displays it. Although sometimes
this exception isnt' great it's far far better than the original one.
Thanks, I forgot to post this.
Will
To:
[EMAIL PROTECTED]
"Craig R.cc: (bcc: Will Spies/Towers
Perrin)
McClanahan" Subject: Re: Debugging struts
exceptions
craigmcc@apa
che.org
04/09/01
10:32 PM
Please
respond to
struts-user
On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote:
I didn't get any response so I'm going to try again. Here is another
exception:
Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root
cause of ServletException
javax.servlet.ServletException: runtime failure in custom tag 'form'
at jsp_servlet._employee._jspService(_employee.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
You might want to complain to WebLogic about this.
The actual exception that is thrown *does* contain a more useful error
message -- it's just that WebLogic is not telling you about it.
Alternatively, you can declare an error page to handle runtime
errors. The Struts tags that throw exceptions store a copy of the
underlying exception as a request attribute under key
"org.apache.struts.action.EXCEPTION", so you can display it yourself.
Craig McClanahan
RE: Debugging struts exceptions
Got it! Thanks for the details...
-Original Message-
From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 10:17 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Debugging struts exceptions
I mean in all your JSPs use the following tag in the beginning:
%@ page language="java" errorPage="error.jsp" %
Then, in error.jsp you can use the following code:
% Throwable strutsException = (Throwable) request.getAttribute
("org.apache.struts.action.EXCEPTION");%
% if ( strutsException != null ) {%
pStruts trace was: brpre
%=getStackTraceAsString(strutsException)%b
%} else {%
pNo Struts trace
%}%
%!
String getStackTraceAsString(Throwable e)
{
ByteArrayOutputStream ostr = new ByteArrayOutputStream();
e.printStackTrace(new PrintStream(ostr));
return(ostr.toString());
}
%
Note: this is just a snipet of the error.jsp but this should give you the
idea. You'll find more info on the errorPage directive in the JSP guides.
The only reason I used Throwable above rather than the struts exception
itself was because I already had this method and was using it for other
exceptions.
To:
[EMAIL PROTECTED]
[EMAIL PROTECTED]cc: (bcc: Will
Spies/Towers Perrin)
elheim.com Subject: RE:
Debugging struts exceptions
04/10/01 09:15 AM
Please respond to
struts-user
What exactly do you mean by "declare an error page"? Is this a JSP that is
specified as a global forward in struts-config.xml or a servlet param in
web.xml?
thanks,
Bob
-Original Message-
From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 7:33 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Debugging struts exceptions
I actually found a good solution to this. Looking at the taglib code I
found this code all over the place when they throw exceptions:
pageContext.setAttribute(Action.EXCEPTION_KEY, e,
PageContext.REQUEST_SCOPE);
I don't know if this is documented somewhere. Probably it is and I just
missed it. However, this allowed me to create an errorPage which displays
*THIS* exception. So, now all my JSPs have an errorPage declared that that
yanks this exception out of the request and displays it. Although sometimes
this exception isnt' great it's far far better than the original one.
Thanks, I forgot to post this.
Will
To:
[EMAIL PROTECTED]
"Craig R.cc: (bcc: Will Spies/Towers
Perrin)
McClanahan" Subject: Re: Debugging struts
exceptions
craigmcc@apa
che.org
04/09/01
10:32 PM
Please
respond to
struts-user
On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote:
I didn't get any response so I'm going to try again. Here is another
exception:
Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root
cause of ServletException
javax.servlet.ServletException: runtime failure in custom tag 'form'
at jsp_servlet._employee._jspService(_employee.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
You might want to complain to WebLogic about this.
The actual exception that is thrown *does* contain a more useful error
message -- it's just that WebLogic is not telling you about it.
Alternatively, you can declare an error page to handle runtime
errors. The Struts tags that throw exceptions store a copy of the
underlying exception as a request attribute under key
"org.apache.struts.action.EXCEPTION", so you can display it yourself.
Craig McClanahan
Re: Debugging struts exceptions
On Wed, 4 Apr 2001, Will Spies/Towers Perrin wrote: I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) You might want to complain to WebLogic about this. The actual exception that is thrown *does* contain a more useful error message -- it's just that WebLogic is not telling you about it. Alternatively, you can declare an error page to handle runtime errors. The Struts tags that throw exceptions store a copy of the underlying exception as a request attribute under key "org.apache.struts.action.EXCEPTION", so you can display it yourself. Craig McClanahan
RE: Debugging struts exceptions
This is really not realistic. I did try adding an errorPage directive to my JSPs. This didn't help either. It didn't catch these. To: [EMAIL PROTECTED] "Ludwig, Pat" cc: (bcc: Will Spies/Towers Perrin) pludwig@silversSubject: RE: Debugging struts exceptions tream.com 04/04/01 04:11 PM Please respond to struts-user Will, forgive me if i am off-base here but i can sympathize with your situation. often times when exceptions happen it doesn't produce the necessary information for problem diagnosis. in your case, it may be that if there is a exception getting generated by a Struts tag, it is getting swallowed by Weblogic and getting re-thrown as a "runtime failure". while it's a little ugly, you might try modifying the generated jsp page class to instrument it and catch the real exception since all it can tell you now is that it is happening in the generated service method of the jsp. i don't disagree however with the sentiment that has been expressed that code should provide a logging mechanism rather than just throwing an exception to a higher level to deal with it. good luck. regards, Pat Ludwig Silverstream Software -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions Yes, I've seen that too. Some errors do have more information appearing in the log. Many are like the one below though with nothing. Sending the errors to the browser would of course be the best overall ( but beggers can't be choosy...I would take just getting more information in the log ). To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: (bcc: Will Spies/Towers Perrin) elheim.com Subject: RE: Debugging struts exceptions 04/04/01 03:38 PM Please respond to struts-user I noticed that some tags do have more specific error messages. For example, if you use the iterate tag and specifically an invalid rte for the collection property you get both a stack trace and a JSP error message in the browser. I think this is the type of error message that should be generated for any error that occurs in a tag.. The error should be sent to the browser as a JSP error as well, since page designers may not have access to the servlet log file- or at least it won't be as convenient. The error message should state the tag type, name, property, etc... that resulted in the error so you can jump right to the section of JSP that caused the error. -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:20 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions I think really if someone just put some extra logging in the tag libraries the way it's in the other struts code...for example: if (servlet.getDebug() = 1) servlet.log(...); this would be a huge help and not a whole lot of effort... Will To: [EMAIL PROTECTED] "Kurt Olsen" cc: (bcc: Will Spies/Towers Perrin) kolsen@get2h Subject: RE: Debugging struts exceptions awaii.com 04/04/01 03:06 PM Please respond t
Debugging struts exceptions
I didn't get any response so I'm going to try again. Here is another
exception:
Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root
cause of ServletException
javax.servlet.ServletException: runtime failure in custom tag 'form'
at jsp_servlet._employee._jspService(_employee.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:1697)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1540)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:507)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:481)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
I can't really say that this is very helpful in determing what the problem
is in my JSP code except that inside 'some' form there is 'some' problem. I
get past these but I could do it quicker if there was some sort of extra
logging. Is there extra logging that I can turn on for the tag libraries?
What's the recommend way to debug this ( let's say without a remote JSP
debugger though ) or does everyone just live with this?
This could be a newbie stupid question. If so I apologize in advance.
Thanks for any information!
Will
- Forwarded by Will Spies/Towers Perrin on 04/04/01 10:54 AM -
To: [EMAIL PROTECTED]
Will Spies cc:
Subject: Debugging struts exceptions -
correction
04/03/01
08:13 AM
Oops...I put the wrong tag in there:
html:form action="/logon" focus="badproperyname"
(see what I mean?)
- Forwarded by Will Spies/Towers Perrin on 04/03/01 08:12 AM -
To: [EMAIL PROTECTED]
Will Spies cc:
Subject: Debugging struts exceptions
04/03/01
08:12 AM
Seems certain exceptions don't come with very good explanations. For
example, I have a tag which had a bad property:
html:text property="badpropertyname" size="16" maxlength="16"/
If 'badpropertyname' does not exist the exception I see in the log file is:
javax.servlet.ServletException: runtime failure in custom tag 'form'
at jsp_servlet._logon._jspService(_logon.java, Compiled Code)
at
RE: Debugging struts exceptions
I noticed that some tags do have more specific error messages. For example, if you use the iterate tag and specifically an invalid rte for the collection property you get both a stack trace and a JSP error message in the browser. I think this is the type of error message that should be generated for any error that occurs in a tag.. The error should be sent to the browser as a JSP error as well, since page designers may not have access to the servlet log file- or at least it won't be as convenient. The error message should state the tag type, name, property, etc... that resulted in the error so you can jump right to the section of JSP that caused the error. -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:20 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions I think really if someone just put some extra logging in the tag libraries the way it's in the other struts code...for example: if (servlet.getDebug() = 1) servlet.log(...); this would be a huge help and not a whole lot of effort... Will To: [EMAIL PROTECTED] "Kurt Olsen" cc: (bcc: Will Spies/Towers Perrin) kolsen@get2hSubject: RE: Debugging struts exceptions awaii.com 04/04/01 03:06 PM Please respond to struts-user I'm just living with it but we hate it. Struts is working extremely well for us but I'd have to say that from the perspective of the page designers it makes struts look much more 'raw' than it is. As a developer I know what struts is doing for us (ie look at the alternatives) but some attention needs to be focused on these error messages. Anybody got the time? I don't! Sorry.. Kurt -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 4:58 AM To: [EMAIL PROTECTED] Subject: Debugging struts exceptions I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java :106) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java :124) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp l.java:154) at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.ja va:1697) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1540) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:865) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java :106) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp l.java:507) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp l.java:481) at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext Manager.java:252) at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364) at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code) I can't really say that this is very helpful in determing what the problem is in my JSP code except that inside 'some' form there is 'some' problem. I get past these but I could do it quicker if there was some sort of extra logging. Is there extra logging that I can turn on for the tag libraries? What's the recommend way to debug this ( let's say without a remote JSP debugger though ) or does everyone just live with this? This could be a newbie stupid question. If so I apologize in advance. Thanks for any information! Will - Forwarded by Will Spies/Towers Perrin on 04/04/01 10:54 AM - To: [EMAIL PROTECTED] Will Spies cc: Subject: Debugging struts exceptions - correction 04/03/01 08:13 AM Oops...I put the wrong tag in there: html:form action="/logon" focus="badproperyname" (see what I mean?) - Forwarded by Will Spies/Towe
RE: Debugging struts exceptions
I agree. I would take any message that is available as well... I just wanted to make sure we keep page designers in mind too since ideally they will be doing the JSP. I just noticed "improved error reporting" is on the to-do list for 1.1 Maybe you can volunteer :) -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions Yes, I've seen that too. Some errors do have more information appearing in the log. Many are like the one below though with nothing. Sending the errors to the browser would of course be the best overall ( but beggers can't be choosy...I would take just getting more information in the log ).
RE: Debugging struts exceptions
Will, forgive me if i am off-base here but i can sympathize with your situation. often times when exceptions happen it doesn't produce the necessary information for problem diagnosis. in your case, it may be that if there is a exception getting generated by a Struts tag, it is getting swallowed by Weblogic and getting re-thrown as a "runtime failure". while it's a little ugly, you might try modifying the generated jsp page class to instrument it and catch the real exception since all it can tell you now is that it is happening in the generated service method of the jsp. i don't disagree however with the sentiment that has been expressed that code should provide a logging mechanism rather than just throwing an exception to a higher level to deal with it. good luck. regards, Pat Ludwig Silverstream Software -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions Yes, I've seen that too. Some errors do have more information appearing in the log. Many are like the one below though with nothing. Sending the errors to the browser would of course be the best overall ( but beggers can't be choosy...I would take just getting more information in the log ). To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: (bcc: Will Spies/Towers Perrin) elheim.com Subject: RE: Debugging struts exceptions 04/04/01 03:38 PM Please respond to struts-user I noticed that some tags do have more specific error messages. For example, if you use the iterate tag and specifically an invalid rte for the collection property you get both a stack trace and a JSP error message in the browser. I think this is the type of error message that should be generated for any error that occurs in a tag.. The error should be sent to the browser as a JSP error as well, since page designers may not have access to the servlet log file- or at least it won't be as convenient. The error message should state the tag type, name, property, etc... that resulted in the error so you can jump right to the section of JSP that caused the error. -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:20 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions I think really if someone just put some extra logging in the tag libraries the way it's in the other struts code...for example: if (servlet.getDebug() = 1) servlet.log(...); this would be a huge help and not a whole lot of effort... Will To: [EMAIL PROTECTED] "Kurt Olsen" cc: (bcc: Will Spies/Towers Perrin) kolsen@get2h Subject: RE: Debugging struts exceptions awaii.com 04/04/01 03:06 PM Please respond to struts-user I'm just living with it but we hate it. Struts is working extremely well for us but I'd have to say that from the perspective of the page designers it makes struts look much more 'raw' than it is. As a developer I know what struts is doing for us (ie look at the alternatives) but some attention needs to be focused on these error messages. Anybody got the time? I don't! Sorry.. Kurt -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 4:58 AM To: [EMAIL PROTECTED] Subject: Debugging struts exceptions I didn't get any response so I'm going to try again. Here is another exception: Wed Apr 04 10:53:26 EDT 2001:E WebAppServletContext-tpsampleapp Root cause of ServletException javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._employee._jspService(_employee.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Servle tStubImpl.java :106) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Servle tStubImpl.java :124) at weblogic.servlet.internal.RequestDispatcherImpl.forward(Reques tDispatcherImp l.java:154) at org.apache.struts.action.ActionServlet.processActionForward(Ac tionServlet.ja va:1697) at org.apache.struts.action.ActionServlet.process(ActionServlet.j ava:1540) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http
RE: Debugging struts exceptions
You know what, if I could I would. Too much time too little to do...strike that...reverse it. To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: (bcc: Will Spies/Towers Perrin) elheim.comSubject: RE: Debugging struts exceptions 04/04/01 04:04 PM Please respond to struts-user I agree. I would take any message that is available as well... I just wanted to make sure we keep page designers in mind too since ideally they will be doing the JSP. I just noticed "improved error reporting" is on the to-do list for 1.1 Maybe you can volunteer :) -Original Message- From: Will Spies/Towers Perrin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 3:47 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Debugging struts exceptions Yes, I've seen that too. Some errors do have more information appearing in the log. Many are like the one below though with nothing. Sending the errors to the browser would of course be the best overall ( but beggers can't be choosy...I would take just getting more information in the log ).
Debugging struts exceptions - correction
Oops...I put the wrong tag in there:
html:form action="/logon" focus="badproperyname"
(see what I mean?)
- Forwarded by Will Spies/Towers Perrin on 04/03/01 08:12 AM -
To: [EMAIL PROTECTED]
Will Spies cc:
Subject: Debugging struts exceptions
04/03/01
08:12 AM
Seems certain exceptions don't come with very good explanations. For
example, I have a tag which had a bad property:
html:text property="badpropertyname" size="16" maxlength="16"/
If 'badpropertyname' does not exist the exception I see in the log file is:
javax.servlet.ServletException: runtime failure in custom tag 'form'
at jsp_servlet._logon._jspService(_logon.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:507)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:481)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
This doesn't always happen but it happens here and this is probably a
pretty common error. Any suggestions?
P.S. I use WLS 5.1 SP8
Debugging struts exceptions
Seems certain exceptions don't come with very good explanations. For example, I have a tag which had a bad property: html:text property="badpropertyname" size="16" maxlength="16"/ If 'badpropertyname' does not exist the exception I see in the log file is: javax.servlet.ServletException: runtime failure in custom tag 'form' at jsp_servlet._logon._jspService(_logon.java, Compiled Code) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:507) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:481) at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252) at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364) at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code) This doesn't always happen but it happens here and this is probably a pretty common error. Any suggestions? P.S. I use WLS 5.1 SP8
