Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » BIRT » How do debug AssertionError cannot be cast to Exception?(How can I debug AssertionError cannot be cast to Exception comming when loading a report?)
How do debug AssertionError cannot be cast to Exception? [message #541802] Tue, 22 June 2010 14:56 Go to next message
Jonathan is currently offline JonathanFriend
Messages: 4
Registered: July 2009
Junior Member
Birt loads up find but when we try to load a report we get the following error. How can we go about figuring out what we made wrong? Googling for something like this is sadly not so easy and my attempts has not come up with anything.

org.apache.axis.AxisFault: ; nested exception is:
java.lang.ClassCastException: java.lang.AssertionError cannot be cast to java.lang.Exception
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) ~[axis.jar:na]
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:333) ~[axis.jar:na]
at org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32) ~[axis.jar:na]
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) ~[axis.jar:na]
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) ~[axis.jar:na]
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454) ~[axis.jar:na]
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 ) ~[axis.jar:na]
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699) ~[axis.jar:na]
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer vlet.doPost(BirtSoapMessageDispatcherServlet.java:265) [viewservlets.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) [javax.servlet_2.5.0.v200806031605.jar:na]
at org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327) [axis.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [javax.servlet_2.5.0.v200806031605.jar:na]
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer vlet.service(BirtSoapMessageDispatcherServlet.java:122) [viewservlets.jar:na]
at org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:180) [org.eclipse.equinox.http.registry_1.0.200.v20090520-1800.ja r:na]
at org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90) [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111) [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59) [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [javax.servlet_2.5.0.v200806031605.jar:na]
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:318) [org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800.jar:na]
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:502) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:380) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl er.java:181) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl er.java:765) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp er.java:152) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.Server.handle(Server.java:324) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio n.java:535) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http Connection.java:880) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn dPoint.java:409) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr eadPool.java:520) [org.mortbay.jetty.util_6.1.15.v200905182336.jar:na]
Caused by: java.lang.ClassCastException: java.lang.AssertionError cannot be cast to java.lang.Exception
at org.eclipse.birt.report.soapengine.processor.AbstractBaseCom ponentProcessor.process(AbstractBaseComponentProcessor.java: 116) ~[viewservlets.jar:na]
at org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingI mpl.getUpdatedObjects(BirtSoapBindingImpl.java:66) ~[viewservlets.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_20]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) ~[na:1.6.0_20]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) ~[na:1.6.0_20]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_20]
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:397) ~[axis.jar:na]
at org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186) ~[axis.jar:na]
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323) ~[axis.jar:na]
... 30 common frames omitted

Re: How do debug AssertionError cannot be cast to Exception? [message #541806 is a reply to message #541802] Tue, 22 June 2010 15:11 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

Does this happen with all reports? How are you running them?

Jason

On 6/22/2010 10:56 AM, Jonathan wrote:
> Birt loads up find but when we try to load a report we get the following
> error. How can we go about figuring out what we made wrong? Googling for
> something like this is sadly not so easy and my attempts has not come up
> with anything.
>
> org.apache.axis.AxisFault: ; nested exception is:
> java.lang.ClassCastException: java.lang.AssertionError cannot be cast to
> java.lang.Exception
> at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) ~[axis.jar:na]
> at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi
> der.java:333) ~[axis.jar:na]
> at org.apache.axis.strategies.InvocationStrategy.visit(Invocati
> onStrategy.java:32) ~[axis.jar:na]
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> ~[axis.jar:na]
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) ~[axis.jar:na]
> at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService
> .java:454) ~[axis.jar:na]
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
> ~[axis.jar:na]
> at org.apache.axis.transport.http.AxisServlet.doPost(AxisServle
> t.java:699) ~[axis.jar:na]
> at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer
> vlet.doPost(BirtSoapMessageDispatcherServlet.java:265)
> [viewservlets.jar:na]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> [javax.servlet_2.5.0.v200806031605.jar:na]
> at org.apache.axis.transport.http.AxisServletBase.service(AxisS
> ervletBase.java:327) [axis.jar:na]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> [javax.servlet_2.5.0.v200806031605.jar:na]
> at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer
> vlet.service(BirtSoapMessageDispatcherServlet.java:122)
> [viewservlets.jar:na]
> at org.eclipse.equinox.http.registry.internal.ServletManager$Se
> rvletWrapper.service(ServletManager.java:180)
> [org.eclipse.equinox.http.registry_1.0.200.v20090520-1800.ja r:na]
> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
> n.handleRequest(ServletRegistration.java:90)
> [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
> ssAlias(ProxyServlet.java:111)
> [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
> ce(ProxyServlet.java:59)
> [org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar :na]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> [javax.servlet_2.5.0.v200806031605.jar:na]
> at org.eclipse.equinox.http.jetty.internal.HttpServerManager$In
> ternalHttpServiceServlet.service(HttpServerManager.java:318)
> [org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800.jar:na]
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder
> .java:502) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl
> er.java:380) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandl
> er.java:181) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandl
> er.java:765) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapp
> er.java:152) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.Server.handle(Server.java:324)
> [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnectio
> n.java:535) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.HttpConnection$RequestHandler.content(Http
> Connection.java:880) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748)
> [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 219)
> [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 404)
> [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEn
> dPoint.java:409) [org.mortbay.jetty.server_6.1.15.v200905151201.jar:na]
> at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThr
> eadPool.java:520) [org.mortbay.jetty.util_6.1.15.v200905182336.jar:na]
> Caused by: java.lang.ClassCastException: java.lang.AssertionError cannot
> be cast to java.lang.Exception
> at org.eclipse.birt.report.soapengine.processor.AbstractBaseCom
> ponentProcessor.process(AbstractBaseComponentProcessor.java: 116)
> ~[viewservlets.jar:na]
> at org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingI
> mpl.getUpdatedObjects(BirtSoapBindingImpl.java:66) ~[viewservlets.jar:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.6.0_20]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:39) ~[na:1.6.0_20]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:25) ~[na:1.6.0_20]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_20]
> at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP
> rovider.java:397) ~[axis.jar:na]
> at org.apache.axis.providers.java.RPCProvider.processMessage(RP
> CProvider.java:186) ~[axis.jar:na]
> at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi
> der.java:323) ~[axis.jar:na]
> .. 30 common frames omitted
>
>
Re: How do debug AssertionError cannot be cast to Exception? [message #545400 is a reply to message #541806] Wed, 07 July 2010 16:05 Go to previous messageGo to next message
Jonathan is currently offline JonathanFriend
Messages: 4
Registered: July 2009
Junior Member
Yes our project (Bioclipse) have at least two features with plugins that use Birt for generating reports and we get the same error message in both cases. As for the question of how they are run I guess the best I can do is point at this code which is one example of how one report is run:

< http://github.com/jonalv/bioclipse.brunn/blob/master/plugins /net.bioclipse.brunn.ui/src/net/bioclipse/brunn/ui/editors/m asterPlateEditor/MasterPlateReport.java#L224-234>

Sadly I did not write this code. It used to work earlier when we had Birt installed locally in Eclipse, now we have them in a separate target.platform and somewhere in this move this problem turned up. It's very difficult to know how to debug something like this though...

Do you have any suggestions?
Re: How do debug AssertionError cannot be cast to Exception? [message #545404 is a reply to message #545400] Wed, 07 July 2010 16:20 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

Do you get the error on all reports? Have you tried using the sample db
as a test?

Jason

On 7/7/2010 12:05 PM, Jonathan wrote:
> Yes our project (Bioclipse) have at least two features with plugins that
> use Birt for generating reports and we get the same error message in
> both cases. As for the question of how they are run I guess the best I
> can do is point at this code which is one example of how one report is run:
>
> < http://github.com/jonalv/bioclipse.brunn/blob/master/plugins /net.bioclipse.brunn.ui/src/net/bioclipse/brunn/ui/editors/m asterPlateEditor/MasterPlateReport.java#L224-234>
>
>
> Sadly I did not write this code. It used to work earlier when we had
> Birt installed locally in Eclipse, now we have them in a separate
> target.platform and somewhere in this move this problem turned up. It's
> very difficult to know how to debug something like this though...
>
> Do you have any suggestions?
Re: How do debug AssertionError cannot be cast to Exception? [message #559197 is a reply to message #545404] Wed, 15 September 2010 22:30 Go to previous messageGo to next message
Don Bergstrom is currently offline Don BergstromFriend
Messages: 24
Registered: July 2009
Junior Member
Jason,

I have just completed building the birt_web application from the 2.5.2 release source using the following directions. ( http://wiki.eclipse.org/BIRT/FAQ/Birt_Project#Q:_How_do_I_ex port_the_2.5_BIRT_web_viewer.3F)

When trying to run the included sample reports, test.rptdesign and test1.rptdesign, I too get the java.lang.ClassCastException: java.lang.AssertionError cannot be cast to java.lang.Exception error.

What is missing?
Re: How do debug AssertionError cannot be cast to Exception? [message #559453 is a reply to message #559197] Thu, 16 September 2010 16:57 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

Don,

Can you post the complete stacktrace?

Jason

On 9/15/2010 6:30 PM, Don Bergstrom wrote:
> Jason,
>
> I have just completed building the birt_web application from the 2.5.2
> release source using the following directions.
> ( http://wiki.eclipse.org/BIRT/FAQ/Birt_Project#Q:_How_do_I_ex port_the_2.5_BIRT_web_viewer.3F)
>
> When trying to run the included sample reports, test.rptdesign and
> test1.rptdesign, I too get the java.lang.ClassCastException:
> java.lang.AssertionError cannot be cast to java.lang.Exception error.
>
> What is missing?
Re: How do debug AssertionError cannot be cast to Exception? [message #559498 is a reply to message #559197] Thu, 16 September 2010 20:44 Go to previous messageGo to next message
Don Bergstrom is currently offline Don BergstromFriend
Messages: 24
Registered: July 2009
Junior Member
The error does not produce a stacktrace, or at least the one that is produced for my is is blank.

It appears that the 2.5.2 version of the web viewer does not run when the -enableassertations flag is set. Setting the -disableassertations flag seems to ensure that the reports run with out the class cast exception for the assertation error.

This is also reproducable using the WebViewerExample app in the birt-runtime-2-5-2.zip file.

[Updated on: Thu, 16 September 2010 20:50]

Report message to a moderator

Re: How do debug AssertionError cannot be cast to Exception? [message #559680 is a reply to message #559498] Fri, 17 September 2010 14:52 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

Can you log a bug for this?

Jason

On 9/16/2010 4:44 PM, Don Bergstrom wrote:
> It appears that the 2.5.2 version of the web viewer does not run when
> the -enableassertations flag is set. Setting the -disableassertations
> flag ensures that the reports run with out the class cast exception for
> the assertation error.
Re: How do debug AssertionError cannot be cast to Exception? [message #559975 is a reply to message #559680] Mon, 20 September 2010 15:13 Go to previous message
Don Bergstrom is currently offline Don BergstromFriend
Messages: 24
Registered: July 2009
Junior Member
Bug has been logged for this issue.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=325769
Previous Topic:Pagebreak if not enough space left
Next Topic:SQL error #1: Incorrect syntax near ','.
Goto Forum:
  


Current Time: Thu Mar 28 13:59:06 GMT 2024

Powered by FUDForum. Page generated in 0.02986 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top