Jump to content
Changes to the Jaspersoft community edition download ×

2005 IR Help

Recommended Posts

By: BOURGOUIN - bourgoui

JVM crash

2003-05-16 00:33

hello,

 

I'm using JasperReports 4.5 with windows 2000 SP2 and a jdk4.1 and I'm faced with jvm crash. The message of the crash is the following:

 

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D3CE26A

Function=JVM_FindSignal+0x17C1C

Library=X:j2sdk1.4.1_01jrebinclientjvm.dll

 

 

****************

 

Current Java thread:

Another exception has been detected while we were handling last error.

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

Dumping information about last error:

ERROR REPORT FILE = (N/A)

PC = 0x6D3CE26A

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

SIGNAL = -1073741819

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

FUNCTION NAME = JVM_FindSignal

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

OFFSET = 0x17C1C

LIBRARY NAME = X:j2sdk1.4.1_01jrebinclientjvm.dll

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

Please check ERROR REPORT FILE for further information, if there is any.

Good bye.

at dori.jasper.engine.fill.JRCalculator.evaluate(JRCalculator.java:678)

Java Result: 1

 

This problem happens randomly. I've tried others jdk version (1.4.1_01 and 1.4.1_02) but the problem still persist. Is it a bug of JasperReports. If anybody can help me, I will appreciate.

 

thanks,

Jeremy

 

 

 

 

By: schroffd - schroffd

RE: JVM crash

2003-05-16 00:40

I've posted a similar question to the support mailing list, but without any response.

 

https://sourceforge.net/tracker/index.php?func=detail&aid=702128&group_id=36382&atid=416704

 

Does anyone has an idea?

 

 

 

 

By: Albert L. - looks

RE: JVM crash

2003-05-17 00:28

I've encountered this problem before, but only when I use jdk 1.4.2 beta.

 

As soon as I remove 1.4.2 beta and reinstall 1.4.1_02, there is no such error.

 

To be sure, have tested it time - remove/install between 1.4.2 beta and 1.4.1_02 stable - this problem always occur on 1.4.2 beta jvm.

 

I'm using JasperReports 0.4.6.

 

 

 

 

By: Albert L. - looks

RE: JVM crash

2003-05-17 00:31

To be sure, have tested it a few times - remove/install between 1.4.2 beta and 1.4.1_02 stable - this problem always occur on 1.4.2 beta jvm.

 

 

 

 

By: BOURGOUIN - bourgoui

RE: JVM crash

2003-05-19 00:14

I 've never installed jdk 1.4.2 beta on my computer, and the problem happens randomly with the jdk 1.4.1_02. If anyone has another suggestion, it would help.

 

thanks,

Jeremy

 

 

 

 

By: Chris Green - c_g12

RE: JVM crash

2003-05-28 11:16

Yep I got this too, using jdk 1.4.1_02

 

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D3DE3FE

Function=JVM_FindSignal+0x17BD4

Library=jvm.dll

 

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 dori.jasper.engine.fill.JRCalculator.evaluate(JRCalculator.java:678)

 

 

****************

Another exception has been detected while we were handling last error.

Dumping information about last error:

ERROR REPORT FILE = (N/A)

PC = 0x6D3DE3FE

SIGNAL = -1073741819

FUNCTION NAME = JVM_FindSignal

OFFSET = 0x17BD4

LIBRARY NAME = jvm.dll

Please check ERROR REPORT FILE for further information, if there is any.

Good bye.

 

 

 

 

By: Dan Dubinsky - dandubinsky

RE: JVM crash

2003-07-03 11:22

I got the same error using JDK 1.4.0 and JDK 1.4.1_02. For me, the problem appears when I call:

 

JasperPrint pr = JasperFillManager.fillReport(JasperReport,Map,DataSource);

 

three or four time with the same report object, but a different Datasource. Anybody have any idea what to do? This puppy is a real show stopper.

 

 

 

 

By: Albert L. - looks

RE: JVM crash

2003-07-03 13:11

Hi,

 

I've managed to solve my JVM crash issue. However, it may not apply to all related JVM crashes, as mine specifically crashed 1.4.2 (both beta and the official release) but not 1.4.1 (all sub version 02,03 is ok too).

 

In summary, my JVM crashed was due to my code calling System.gc() too often (after printing each report, trying to free resources asap).

 

For my case, when the JVM crashed, it does not show a Library reference on the crash message. But it does show some common messages, such as :

 

..

Good bye.

at dori.jasper.engine.fill.JRCalculator.evaluate(JRCalculator.java:678)

 

As soon as I remove the code calling System.gc(), the 1.4.2 JVM performs solidly - without a single JVM crash. But it does show at least one 'out of memory' instance during my stress test, which probably won't happen in real use (I hope).

 

If your code calls System.gc() at all, try removing it and see if it helps.

 

Anyway, 1.4.2 handles gc internally better than 1.4.1, so I don't really need to call it manually, but still funny, calling gc can crash the JVM.

 

Albert

 

 

 

 

By: Dan Dubinsky - dandubinsky

RE: JVM crash

2003-07-09 08:52

I think I may have found the solution to the problem.

 

In the methods dori.jasper.engine.fill.JRCalculator:

 

evaluate(JRExpression expression) and

evaluateEstimated(JRExpression expression)

evaluateOld(JRExpression expression)

 

The code looked like this (with slight variations for each method)

 

try {

value = this.evaluate(expression.getId());

}

catch (NullPointerException e){}

catch (Exception e) {

throw new JRException("Error evaluating expression value : " + expression.getName(), e);

}

 

I changed it to

 

try {

if (expression != null)

value = this.evaluate(expression.getId());

}

catch (Exception e) {

throw new JRException("Error evaluating expression value : " + expression.getName(), e);

}

 

and it stopped blowing up. I think it might be that too many exceptions being thrown (expression appears to be null quite a lot of times in each fill) and too many stack traces are causing the VM to wig out.

 

Is it possible to get this fix into the next release of Jasper Reports?

 

 

 

 

By: Teodor Danciu - teodord

RE: JVM crash

2004-04-30 03:18

 

Hi,

 

Try to launch your JVM using the -server command line

switch instead of the default which is -client.

 

Thank you,

Teodor

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...