aspose file tools*
The moose likes Tomcat and the fly likes problem [Ljava.lang.StackTraceElement;@26355060 when run tomcat 6 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "problem [Ljava.lang.StackTraceElement;@26355060 when run tomcat 6" Watch "problem [Ljava.lang.StackTraceElement;@26355060 when run tomcat 6" New topic
Author

problem [Ljava.lang.StackTraceElement;@26355060 when run tomcat 6

Angus Comber
Ranch Hand

Joined: Jul 16, 2011
Posts: 90
I am running some servlet code in tomcat 6 via Eclipse.

In the log I see:

...
INFO: Server startup in 198 ms
problem [Ljava.lang.StackTraceElement;@26355060
Oct 13, 2012 6:54:47 PM org.apache.catalina.core.ApplicationContext log
...

Does @26355060 mean anything? Can I use that?

I can access the application via a jsp page and everything seems to work fine. But I am puzzled by the "problem [Ljava.lang.StackTraceElement;@26355060" error and wondering what to do about it???

I am running a 64 bit operating system and 64 bit Java but tomcat-6 is 32 bit. Would that cause this problem?

I ma looking at the Java api Class StackTraceElement docs but that doesn't seem to help.

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15665
    
  15

"[Ljava.lang.StackTraceElement;@26355060 " is the signature and identify of an object. The object is an array of java.lang.StackTraceElement's and its internal JVM object ID is 26355060 (which is mostly useless for you other than to distinguish it for any other possible arrays of StackTraceElements you might encounter).

This looks like an app did a System.out.println in the attempt to display a stack trace for an exception instead of using the exception's own printStackTrace method. Unfortunately, since the app did a brute-force print instead of using a logger, it's going the be a "treasure hunt" to find which app it was and where in the app it was done.


Customer surveys are for companies who didn't pay proper attention to begin with.
Angus Comber
Ranch Hand

Joined: Jul 16, 2011
Posts: 90
Tim Holloway wrote:"[Ljava.lang.StackTraceElement;@26355060 " is the signature and identify of an object. The object is an array of java.lang.StackTraceElement's and its internal JVM object ID is 26355060 (which is mostly useless for you other than to distinguish it for any other possible arrays of StackTraceElements you might encounter).

This looks like an app did a System.out.println in the attempt to display a stack trace for an exception instead of using the exception's own printStackTrace method. Unfortunately, since the app did a brute-force print instead of using a logger, it's going the be a "treasure hunt" to find which app it was and where in the app it was done.


Ah I wonder what idiot would have done that ;)

Thanks Tim, I will have a look at the code - looks quite likely the culprit.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: problem [Ljava.lang.StackTraceElement;@26355060 when run tomcat 6
 
Similar Threads
Using Tomcat 6 with IIS7 in Win 2008 64 bit OS
Installing Tomcat 6 (64 bit) on Windows Server 2008 R2.
start/stop Tomcat 7 windows service on 64-bit results in error
Can't load IA 32-bit .dll on a AMD 64-bit platform
Integrating Tomcat 6 with IIS7 in Windows 2008 64 bit OS