Jump to content
Changes to the Jaspersoft community edition download ×

Threading error - Product release showstopper


2004 IR Help

Recommended Posts

By: Earl Jenkins - earlsjenkins

Threading error - Product release showstopper

2005-07-25 08:53

I'm getting signal 11 error (segment violation) from a couple of threads in JasperReports during the fill operations. I'm using v0.6.5, in a J2EE app running on WebSphere. Here's the log messages:

 

Unexpected Signal : 11 occurred at PC=0xFED3D150

Function=[unknown. Nearest: JVM_FillInStackTrace+0x48ED0]

Library=/opt/WebSphere/AppServer/java/jre/lib/sparc/client/libjvm.so

?

Current Java thread:

??????? at java.lang.Throwable.fillInStackTrace(Native Method)

??????? at java.lang.Throwable.<init>(Throwable.java:180)

??????? at java.lang.Exception.<init>(Exception.java:29)

??????? at java.lang.RuntimeException.<init>(RuntimeException.java:32)

??????? at java.lang.NullPointerException.<init>(NullPointerException.java:36)

??????? at net.sf.jasperreports.engine.fill.JRCalculator.evaluate(JRCalculator.java:426)

?

Unexpected Signal : 11 occurred at PC=0xFED3D150

Function=[unknown. Nearest: JVM_FillInStackTrace+0x48ED0]

Library=/opt/WebSphere/AppServer/java/jre/lib/sparc/client/libjvm.so

?

Current Java thread:

??????? at java.lang.Throwable.fillInStackTrace(Native Method)

??????? at java.lang.Throwable.<init>(Throwable.java:180)

??????? at java.lang.Exception.<init>(Exception.java:29)

??????? at java.lang.RuntimeException.<init>(RuntimeException.java:32)

??????? at java.lang.NullPointerException.<init>(NullPointerException.java:36)

??????? at net.sf.jasperreports.engine.fill.JRCalculator.evaluateEstimated(JRCalculator.java:403)

 

 

Being a thread-related error, reproduction is inconsistent, but defintely repeated. The worst part is, it's crashing the whole server.

 

Has anyone ever seen this before? I found a single reference to a similar problem on Sun's Java forum, nothign else, with no followups. Please help! We're supposed to go live ASAP, and this is the only big thing holding us up -- and it's a doozy! The problem only appeared when we started large-scale testing in the production environment.

 

Thanks in advance,

 

Earl

Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...