Hello,
I'm a newbie using jasper reports server, and I'm trying to deploy a home server to practise and learn the technology. I'm using jasperserver 5.5.0 over a mysql database. It's working acceptably except for some problems when I'm trying to schedule jobs.
First of all, when I try to put the job, I get this error from server ( HTTP 500 Internal Server Error - "java.io.EOFException: No content to map to Object due to end of input"), although job is correctly scheduled and throws itself in time without problem. The stacktrace in log is as following
<span style="font-size:11px;">at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2766) at org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:2682) at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1308) at org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:419)</span>
In addition, when I return to see the list of scheduled jobs for current report, I get another Internal Server Error which is caused for
<span style="font-size:11px;">java.lang.NoClassDefFoundError: com/sun/xml/bind/DatatypeConverterImpl$CalendarFormatter at com.sun.xml.bind.DatatypeConverterImpl._printDateTime(DatatypeConverterImpl.java:360) at com.sun.xml.bind.DatatypeConverterImpl.printDateTime(DatatypeConverterImpl.java:356) at javax.xml.bind.DatatypeConverter.printDateTime(DatatypeConverter.java:598)</span>
every time there is still an scheduled job. Even more, when I load a list of scheduled jobs, it doesn't mind if there is any of them, I get an HTTP 404 when trying to view the /options page from the report,being referrer page the following jasperserver/scheduler/main.html</span>.</p>
<p>I hope anyone could help me solving this problem because I can't manage my scheduled jobs nowadays.</p>
<p>Thank you all in advance.</p>
3 Answers:
First of all, thank you Hozawa for your suggestion, trying to update I realized it wasn't any bug, because the problem persisted, so I investigate a bit more and realized the problem should be Java version and a conflict in ClassLoaders. Finally, removing jaxb-api and jaxb-impl libraries from war and deploying it again over tomcat I was able to schedule jobs without problem.
I write this to help anyone could solve the same problem working with tomcat 7, JRE 1.7.0_52 (at least that's my version) and mysql database over Linux. Hope it can help.
Recently a pro customer encountered this problem. It was resolved by deleting their tomcat work dir for jasperserver-pro webapp (aka $CATALINA_HOME/work/Catalina/localhost/jasperserver-pro"). The theory is that upon upgrade the work directory was not properly cleared by deployment scripts, so the work dir retained some old JSPs (they were using version 5.5 just prior) and these older classes were compiled with different versions of classes than 6.x would afford.
