MalformedByteSequenceException with Grails jasper plugin 1.1.6

comments (4)

1. J. M. RajalaMay 20, 2011 at 6:53 pm

   Hi,

   I stumbled upon this same problem while trying to make the Grails Jasper plugin work with reports containing subreports, which needed to be pre-compiled to .jasper. Like Sachin I found out that if the main report is not pre-compiled with them but on the fly, then the plugin works. The reason for the “MalformedByteSequenceException” seems to be a bug in JasperService.groovy (in generatePrinter() method): it decides on whether compilation is needed by looking at the report file name extension. If no extension has been defined in the name parameter you have supplied, it is resolved in JasperReportDef. As long as you have a jrxml version only, the if/else condition in the Service class works since it default to a jrxml having been loaded and needing compilation, but in case of implicit .jasper extension the name is not appended with that (in the logic inside JasperReportDef) and JasperService tries to compile the .jasper file again, which throws the exception.
   So until this is fixed in the plugin, you should be able to get this working by explicitly defining the main report name parameter with .jasper extension, if that reports has been pre-compiled.

   Regards,
   JM

   Reply ↓
2. NitinApril 14, 2011 at 5:28 pm

   I want view jasper report by using below code but it giving me Exceptions.
   Please help me

   private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
   try {
   String reportName = “C:\\New Folder\\report4.jasper”;
   java.io.InputStream is = this.getClass().getClassLoader().getResourceAsStream(reportName);
   Class.forName(“com.mysql.jdbc.Driver”);
   Connection conn = DriverManager.getConnection(“jdbc:mysql://localhost:3306/college”, “root”, “”);
   JasperPrint jasperPrint = JasperFillManager.fillReport(is, new HashMap(), conn);
   JasperViewer jv = new JasperViewer(jasperPrint);
   jv.setVisible(true);
   } catch (ClassNotFoundException ex) {
   System.out.println(ex);

   } catch (JRException ex) {
   System.out.println(“1..”+ex);

   } catch (SQLException ex) {
   System.out.println(“2…”+ex);

   }
   }

   Exception in thread “AWT-EventQueue-0” java.lang.NullPointerException
   at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2264)
   at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2277)
   at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2748)
   at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
   at java.io.ObjectInputStream.(ObjectInputStream.java:280)
   at net.sf.jasperreports.engine.util.JRLoader.loadObject(JRLoader.java:191)
   at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:361)
   at javaapplication15.NewJFrame.jButton1ActionPerformed(NewJFrame.java:80)
   at javaapplication15.NewJFrame.access$000(NewJFrame.java:27)
   at javaapplication15.NewJFrame$1.actionPerformed(NewJFrame.java:50)
   at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6038)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
   at java.awt.Component.processEvent(Component.java:5803)
   at java.awt.Container.processEvent(Container.java:2058)
   at java.awt.Component.dispatchEventImpl(Component.java:4410)
   at java.awt.Container.dispatchEventImpl(Container.java:2116)
   at java.awt.Component.dispatchEvent(Component.java:4240)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
   at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
   at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
   at java.awt.Container.dispatchEventImpl(Container.java:2102)
   at java.awt.Window.dispatchEventImpl(Window.java:2429)
   at java.awt.Component.dispatchEvent(Component.java:4240)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

   Reply ↓
3. Bala Thiruppanambakka,December 29, 2010 at 9:52 pm

   Hi Sachin

   I have a fix for this described in my blog

   regards
   Bala

   Reply ↓
4. Sebastian HohnsDecember 14, 2010 at 1:57 pm

   Hi Sachin

   just found your message here (a few days late, please use the grails mailing list if you require a faster response ;)). As the author of the grails jasper plugin i can tell you that you are not the only one with this problem. This is a common problem with iReport (you will find various reports all over the net) and has nothing to do with the grails plugin.
   In most cases it helps if you install a iReport plugin “XML and Schema” see:

   this should give you a stacktrace you can work with.
   This is a odd bug, i even know cases where it’s enough to simply compile the report on another system (for example i was able to reproduce this bug on a XP install, but exactly the same report worked fine if i compiled it on Linux).

   Greetings

   Reply ↓