• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Unable to print stack trace on own log file

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
In my application using JBoss 4.2.1-GA, I have used JSF+trinidad tag library for view and JPA+EJB 3.0 for the business logic. On persisting an entity into the DB using entity manager I got an exception - java.sql.BatchUpdateException. The stack trace is available in <JBOSS_HOME>/server/default/log/server.log.
I want to set up my own log file in<JBOSS_HOME>/bin. For this I set an error.jsp file with isError attribute true in the page.

This provided me with the implicit exception object. But when I used it to log the stack trace, it provided me with only the stack trace of the FacesException.The rest of the exceptions were not logged into my file.

How can I provide all the exception stack traces that were available in jboss server's log file to my own log file??

Thanks,
Dushyant
[ November 27, 2008: Message edited by: Dushyant Agarwal ]
 
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are you saying that when error.jsp display the stack trace that it is not showing the full trace? It is possible that the code providing the stack trace for error.jsp is catching the exception at a different location, hence the differences between it and what is in server.log.

If this does not help, please post the full stack trace as shown in server.log, and the stack trace that you are seeing and also state where that stack trace is appearing (in the browser or in a log file within the bin directory, or ???).
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic