Thanks Brandon, but unfortunately that didn't work - I still don't see any
stack trace on the server (I've attached my log4j.xml also). I uncommented
the TRACE entries, set the threshold level to "All", but still no stack
trace.
Here is the code which I'm using to programmatically create a
RuntimeException (inside a SLSB):
Object o = null;
System.out.println("1111");
o.hashCode();
System.out.println("2222");
On the client I get the NPE as expected:
java.rmi.ServerException: RemoteException occurred in server thread; nested
exception is:
java.rmi.ServerException: null
Embedded Exception
null
javax.ejb.EJBException: null
Embedded Exception
null
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC
all.java:245)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProx
y.java:128)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:108)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73
)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInter
ceptor.java:111)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy1.doTest(Unknown Source)
at
com.softface.framework.services.test.FrameworkTestMain.main(FrameworkTestMai
n.java:17)
java.lang.NullPointerException
<<no stack trace available>>
But on the JBoss console (and in the logs), all I see is:
569 TRACE [LogInterceptor] Start method=doTest
589 TRACE [TxInterceptorCMT] Current transaction in MI is null
619 TRACE [TxInterceptorCMT] TX_REQUIRED for doTest
639 TRACE [TxInterceptorCMT] Thread came in with tx null
659 TRACE [TxInterceptorCMT] Starting new tx TransactionImpl:XidImpl
[FormatId=257, GlobalId=pc-paul//3, BranchQual=]
679 TRACE [StatelessSessionInstancePool] Get instance
org.jboss.ejb.plugins.StatelessSessionInstancePool@75ade6#true#class
com.softface.framework.services.test.FrameworkTe
739 INFO [STDOUT] testing.....
759 INFO [STDOUT] 1111
799 TRACE [TxInterceptorCMT] TxInterceptorCMT: In finally
820 TRACE [LogInterceptor] End method=doTest
ie the exception is somehow being gobbled up. Is anyone using JBoss 3.0.0
and seeing RuntimeExceptions ? If so, could you please post your log4j.xml ?
Thanks in advance,
-Paul
> -----Original Message-----
> From: Brandon Knitter [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 07, 2002 11:41 AM
> To: [EMAIL PROTECTED]; Paul Kavanagh
> Subject: Re: [JBoss-user] JBoss 3.0.0 hiding RuntimeExceptions ???
>
>
> Near the bottom of the log4j.xml file there are two "TRACE" entries, I
> uncommented those and restarted jboss and have better errors now.
>
> Hope that's what you were looking for.
>
> --
> -bk
>
>
> Quoting Paul Kavanagh <[EMAIL PROTECTED]>:
>
> > Hi guys,
> >
> > hoping someone can shed some light on this.
> >
> > I'm using JBoss 3.0.0 (using default settings for everything)
> on Win2K, but
> > when I run my test applciation (Java client connecting to a
> simple session
> > bean) on it, JBoss is not showing us any RuntimeExceptions
> which are being
> > thrown (neither on the console nor in the server.log). The client is
> > getting
> > a java.rmi.ServerException, but there's no stack trace or any
> info on the
> > server. I'm using the default log4j.xml. Any ideas ?
> >
> > Thanks in advance,
> > -Paul
> >
> >
> > _______________________________________________________________
> >
> > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> >
> >
>
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<!-- ===================================================================== -->
<!-- -->
<!-- Log4j Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: log4j.xml,v 1.5.2.2 2002/05/23 05:55:43 starksm Exp $ -->
<!--
| For more configuration infromation and examples see the Jakarta Log4j
| owebsite: http://jakarta.apache.org/log4j
-->
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"; debug="false">
<!-- ================================= -->
<!-- Preserve messages in a local file -->
<!-- ================================= -->
<!-- A time/date based rolling appender -->
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
<param name="File" value="${jboss.server.home.dir}/log/server.log"/>
<param name="Append" value="false"/>
<!-- Rollover at midnight each day -->
<param name="DatePattern" value="'.'yyyy-MM-dd"/>
<!-- Rollover at the top of each hour
<param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
-->
<layout class="org.apache.log4j.PatternLayout">
<!-- The default pattern: Date Priority [Category] Message\n -->
<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
<!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
<param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
-->
</layout>
</appender>
<!-- A size based file rolling appender
<appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
<param name="File" value="${jboss.server.home.dir}/log/server.log"/>
<param name="Append" value="false"/>
<param name="MaxFileSize" value="500KB"/>
<param name="MaxBackupIndex" value="1"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
</layout>
</appender>
-->
<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="ALL"/>
<param name="Target" value="System.out"/>
<layout class="org.apache.log4j.PatternLayout">
<!-- The default pattern: Date Priority [Category] Message\n -->
<param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
</layout>
</appender>
<!-- ====================== -->
<!-- More Appender examples -->
<!-- ====================== -->
<!-- Buffer events and log them asynchronously
<appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
<appender-ref ref="FILE"/>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="SMTP"/>
</appender>
-->
<!-- EMail events to an administrator
<appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
<param name="Threshold" value="ERROR"/>
<param name="To" value="[EMAIL PROTECTED]"/>
<param name="From" value="[EMAIL PROTECTED]"/>
<param name="Subject" value="JBoss Sever Errors"/>
<param name="SMTPHost" value="localhost"/>
<param name="BufferSize" value="10"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
</layout>
</appender>
-->
<!-- Syslog events
<appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
<param name="Facility" value="LOCAL7"/>
<param name="FacilityPrinting" value="true"/>
<param name="SyslogHost" value="localhost"/>
</appender>
-->
<!-- Log events to JMS (requires a topic to be created)
<appender name="JMS" class="org.apache.log4j.net.JMSAppender">
<param name="Threshold" value="ERROR"/>
<param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
<param name="TopicBindingName" value="topic/MyErrorsTopic"/>
</appender>
-->
<!-- ================ -->
<!-- Limit categories -->
<!-- ================ -->
<!-- Limit JBoss categories to INFO
<category name="org.jboss">
<priority value="INFO"/>
</category>
-->
<!-- Increase the priority threshold for the DefaultDS category
<category name="DefaultDS">
<priority value="FATAL"/>
</category>
-->
<!-- Decrease the priority threshold for the org.jboss.varia category
<category name="org.jboss.varia">
<priority value="DEBUG"/>
</category>
-->
<!--
| An example of enabling the custom TRACE level priority that is used
| by the JBoss internals to diagnose low level details. This example
| turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
| subpackages. This will produce A LOT of logging output.
If you use replace the log4j 1.2 jar with a 1.1.3 jar you will need to
change this from XLevel to XPriority.
-->
<category name="org.jboss.system">
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>
<category name="org.jboss.ejb.plugins">
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>
<!-- ======================= -->
<!-- Setup the Root category -->
<!-- ======================= -->
<root>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
</root>
</log4j:configuration>
