I suspect this is some JBoss logging setting that suppressed the stack
trace. Don't know much about Log4J on JBoss, so unfortunately I can't
give any specific pointers.
Do you see other exceptions fully in the logs? Could you throw a fake
exception in the same approximate place in the code and see if it is
printed properly?
Andrus
On Jun 7, 2004, at 3:34 AM, Tore Halset wrote:
> On Jun 7, 2004, at 9:22, Tore Halset wrote:
>
>> Hello.
>>
>> We have a strange error here. It does only happen on one of our
>> servers. It seem to be related to memory, but the application runs ok
>> with less memory elsewere. The machine has been running ok for about
>> a year, but we have recently upgraded our application to use cayenne
>> (1.1M6).
>>
>> The application has a routine to build up a product catalogue of all
>> the availible products in the database. It fetches ca 50K rows from
>> the database using cayenne. We are testing with snapshot size from
>> 100K to 1M.
>>
>> After a realy huge cayenne query we get the following error in the
>> log. We are using log4j, but log.error("", e); does not output the
>> stacktrace. Anyone seen NPEs without stacktrace before?
>>
>> "
>> 2004-06-01 16:00:14,864 ERROR [org.jboss.web.localhost.Engine]
>> StandardWrapperValve[ServletRefreshCatalogue]: Servlet.service() for
>> servlet ServletRefreshCatalogue threw exception
>>
>> java.lang.NullPointerException
>> "
>
> Here is the line in the log created by log.error("", e);
> 2004-06-07 09:24:02,687 ERROR [myapp.catalogue.ServletRefreshCatalogue]
> java.lang.NullPointerException
>
> - Tore.
This archive was generated by hypermail 2.0.0 : Mon Jun 07 2004 - 09:45:28 EDT