| Dropping JDBC Classes [message #659821] |
Tue, 15 March 2011 13:53  |
Eclipse User |
|
|
|
Scenario:
Tomcat 5.5.31, BIRT 2.6.2, RHEL 5.5, Java 1.6.23
When the server is first started, ALL reports can be generated just fine. However, after "stress testing" the server (a program constantly runs reports for a hour or so), SOME reports start generating errors. Here is an excerpt of the stack trace, though I doubt its very relevant.
Axis Fault
(...etc.)
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.eclipse.birt.rep ort.service.api.ReportServiceException: Error happened while running the report.
at org.eclipse.birt.report.service.ReportEngineService.throwDum myException(ReportEngineService.java:1104)
(...etc.)
Caused by: java.lang.NoClassDefFoundError: com/ibm/as400/access/AS400EndJobDS
at com.ibm.as400.access.AS400ImplRemote.getConnection(AS400Impl Remote.java:1069)
at com.ibm.as400.access.AS400ImplRemote.connect(AS400ImplRemote .java:402)
at com.ibm.as400.access.AS400.connectService(AS400.java:1135)
Most of these reports take parameters for the database they are to connect to. One report will run for multiple databases, depending on those values we pass. Because of that, we don't use connection pooling (it connects to ~200 different databases, more than I want to maintain in a pool).
Now, once we start getting this error, the reports that are getting this simply won't run. We can run other reports that are similar, (ie, connect to the same type of DB) without error.
Once Tomcat is restarted, the problem goes away.
Any idea what would be causing BIRT to randomly "drop classes" so to speak?
|
|
|
| Re: Dropping JDBC Classes [message #660002 is a reply to message #659821] |
Wed, 16 March 2011 10:11  |
| Eclipse User |
|
|
|
Logan
I have never seen this happen. I assume the AS400 driver is only in the
drivers directory of the jdbc plugin within the webapp/tomcat libs?
Jason
On 3/15/2011 1:53 PM, Logan wrote:
> Scenario:
>
> Tomcat 5.5.31, BIRT 2.6.2, RHEL 5.5, Java 1.6.23
>
> When the server is first started, ALL reports can be generated just
> fine. However, after "stress testing" the server (a program constantly
> runs reports for a hour or so), SOME reports start generating errors.
> Here is an excerpt of the stack trace, though I doubt its very relevant.
> Axis Fault
> (...etc.)
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:org.eclipse.birt.rep ort.service.api.ReportServiceException:
> Error happened while running the report.
> at org.eclipse.birt.report.service.ReportEngineService.throwDum
> myException(ReportEngineService.java:1104)
> (...etc.)
>
> Caused by: java.lang.NoClassDefFoundError:
> com/ibm/as400/access/AS400EndJobDS
> at com.ibm.as400.access.AS400ImplRemote.getConnection(AS400Impl
> Remote.java:1069)
> at com.ibm.as400.access.AS400ImplRemote.connect(AS400ImplRemote .java:402)
> at com.ibm.as400.access.AS400.connectService(AS400.java:1135)
>
>
> Most of these reports take parameters for the database they are to
> connect to. One report will run for multiple databases, depending on
> those values we pass. Because of that, we don't use connection pooling
> (it connects to ~200 different databases, more than I want to maintain
> in a pool).
> Now, once we start getting this error, the reports that are getting this
> simply won't run. We can run other reports that are similar, (ie,
> connect to the same type of DB) without error.
> Once Tomcat is restarted, the problem goes away.
>
> Any idea what would be causing BIRT to randomly "drop classes" so to speak?
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04782 seconds
Home