[jbosstools-issues] [JBoss JIRA] (JBDS-2404) JBDS crashes at startup when a BPEL diagram was open upon previous shutdown

[Robert (Bob) Brodt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739076#comment-12739076 ] 

Robert (Bob) Brodt commented on JBDS-2404:
------------------------------------------

I'm having a difficult time reproducing this problem. I'm trying to avoid having to set up additional hardware to repro this so I've been using a VM image of ubuntu but apparently the ISO needed to create the VM is only available as a 32 bit image for intel processors (am I missing something maybe?!)

Maurice, can you provide some additional information? Specifically where did you install JBDS 5.0.0 GA from? Was this installed into an existing eclipse runtime or did you use the installer? Have you tried reproducing this on any other OS or processor architecture?

Thanks!
Bob
                
> JBDS crashes at startup when a BPEL diagram was open upon previous shutdown
> ---------------------------------------------------------------------------
>
>                 Key: JBDS-2404
>                 URL: https://issues.jboss.org/browse/JBDS-2404
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: SOA Tooling / Platform 
>    Affects Versions: 5.0.0.GA, 5.0.1.GA
>         Environment: Linux (Ubuntu 12.10, 64-bit), Oracle JVM (1.6.0_37 and 1.7.0_09, 64-bit)
>            Reporter: Maurice de Chateau
>            Assignee: Robert (Bob) Brodt
>             Fix For: 5.0.2.GA
>
>         Attachments: crash with BPEL diagram.log, crash with jdk 6.log, CreditReport.wsdl, CreditReportProcess.bpel
>
>
> In JBDS 5.0.x with ´SOA and Data Services Tooling´ installed, the IDE cannot be started up once it was previously closed with a BPEL diagram still opened.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira