Jump to content

  • JSS 6.2.1v201602090842 Not starting a second time on Mac

    mvcoile

    By mvcoile

     Share
    Assigned User Massimo Rabbi
    CategoryBug report
    PriorityImmediate
    ReproducibilityAlways
    ResolutionUnable to Reproduce
    SeverityBlock
    StatusClosed
    Versionv6.2.2

    Hi,

     

    When I open JSS 6.2.1v201602090842 a second time on Mac, it just hangs.

     

    Screenshots:

    1st try: http://cl.ly/f7Mf

    2n try: http://cl.ly/f7Po

     

    Log:

    !SESSION 2016-02-11 13:40:43.870 -----------------------------------------------

    eclipse.buildId=unknown

    java.version=1.8.0_65

    java.vendor=Oracle Corporation

    BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US

    Framework arguments: -keyring /Users/maarten/.eclipse_keyring -showlocation

    Command-line arguments: -os macosx -ws cocoa -arch x86_64 -data @noDefault -keyring /Users/maarten/.eclipse_keyring -showlocation

     

    !ENTRY org.eclipse.core.resources 2 10035 2016-02-11 13:40:46.431

    !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

     

    !ENTRY com.jaspersoft.studio 1 0 2016-02-11 13:40:47.941

    !MESSAGE Starting JaspersoftStudio bundle - Version: 6.2.1.beta-v201602090842

     

    !ENTRY org.eclipse.core.net 1 0 2016-02-11 13:40:51.487

    !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

     

    !ENTRY com.jaspersoft.studio.book 4 0 2016-02-11 13:40:55.345

    !MESSAGE An error occurred

    !STACK 0

    org.xml.sax.SAXParseException; lineNumber: 753; columnNumber: 2; The content of elements must consist of well-formed character data or markup.

    at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)

    at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)

    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)

    at com.jaspersoft.studio.utils.XMLUtils.parseNoValidation(XMLUtils.java:31)

    at com.jaspersoft.studio.book.BookUtils.validateBook(BookUtils.java:122)

    at com.jaspersoft.studio.book.BookUtils.isValidJRBook(BookUtils.java:97)

    at com.jaspersoft.studio.book.BookUtils.checkFileResourceForDefaultEditor(BookUtils.java:79)

    at com.jaspersoft.studio.book.BookUtils.checkContainerMembersForDefaultEditor(BookUtils.java:61)

    at com.jaspersoft.studio.book.BookUtils.checkContainerMembersForDefaultEditor(BookUtils.java:64)

    at com.jaspersoft.studio.book.BookUtils.checkContainerMembersForDefaultEditor(BookUtils.java:64)

    at com.jaspersoft.studio.book.BookUtils.scanWSForBookReports(BookUtils.java:47)

    at com.jaspersoft.studio.book.JRBookActivator$1.run(JRBookActivator.java:67)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

     

     Share
    Go to bugs

    User Feedback

    Recommended Comments

    mvcoile

    Changed Status from Feedback Requested to Acknowledged

    Hi,I have never used JasperReports Book before in my live, especially not in the editor.Kind regards,Maarten @ Yesplan
    Link to comment
    Share on other sites
    Massimo Rabbi

    Changed Status from Acknowledged to Feedback Requested

    Unfortunately we are not able to reproduce anymore the issues.We removed the JasperReports extensions pre-loading from startup because it appeared to be one of the main causes of the hangs.Can you please attach the thread dumps for JSS process? Simply go into a console and give the following command: jstack -l Attach the output here. Even better if you can attach a zipped copy of the workspace that is causing the block.Thanks in advance.Best regards,Massimo.
    Link to comment
    Share on other sites
    mvcoile

    Changed Status from Feedback Requested to Acknowledged

    Logs: http://cl.ly/f9zRMy workspace is rediculously large, about 200-300 mb. I do believe it's related to a specific report that is working just fine in an older version. Closing the "bad" report allows me to start the JSS 6.2.1 again. The "bad" report opens just fine once JSS 6.2.1 has loaded.
    Link to comment
    Share on other sites
    Massimo Rabbi

    Changed Status from Acknowledged to Feedback Requested

    Changed Assigned User from - to @mrabbi

    Can you please attach a sample or two of "bad reports"? It would help trying to replicate the issue on our test workspaces.Regards,Massimo.
    Link to comment
    Share on other sites
    Massimo Rabbi

    Changed Status from Acknowledged to Feedback Requested

    Hi Maarten,I don't see any reports inside the workspace you attached. Problems during packaging?Its big size as far as I can see is caused by the downloaded JR compiler version 6.0.2 located inside .metadata/.plugins/com.jaspersoft.studio/jrcompilers.Regards,Massimo.
    Link to comment
    Share on other sites
    mvcoile

    Changed Status from Feedback Requested to Acknowledged

    Massimo,No, I have my reports in an external directory that i link in (they are in a git repository).That is strange. I don't have a downloaded JR compiler version installed since 6.2.0. Kind regards,Maarten @ Yesplan
    Link to comment
    Share on other sites
    mvcoile

    @mrabbi: It might be because I changed the appearance away from the default. I restored that to default and the problem is gone.

     

    Kind regards,

    Maarten @ Yesplan

    Link to comment
    Share on other sites
    mvcoile

    Hi Massimo,

     

    Yes I am referring to the Eclipse Theme: http://cl.ly/gOCJ

     

    But I don't think it really is that simple. Though, using the Restore Defaults button in JSS 6.2.0 fixes the blocked startup of JSS 6.2.2.

    So whenever JSS 6.2.2 does not want to start I open 6.2.0and change a setting, hit apply, choose Restore Defaults, hit Apply and close 6.2.0. Then JSS 6.2.2 will start properly again for a while.

     

    Kind regards,

    Maarten @ Yesplan

    Link to comment
    Share on other sites
    Massimo Rabbi

    Changed Resolution from Open to Unable to Reproduce

    Changed Status from Acknowledged to Closed

    Hi Maarten,I tried to replicate but I was not able too even playing with the theme configuration.I will close for now.Regards,Massimo.
    Link to comment
    Share on other sites

×
×
  • Create New...

© 2023 Cloud Software Group,
Inc. All rights reserved

Products

Explore