[jboss-jira] [JBoss JIRA] Updated: (JBRULES-2515) Drools Eclipse debugger fails to start in version 5.0 but works in 5.1

Thu May 20 09:28:07 EDT 2010

     [ https://jira.jboss.org/browse/JBRULES-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Marks updated JBRULES-2515:
---------------------------------

    Affects Version/s:     (was: 5.1.0.M1)


> Drools Eclipse debugger fails to start in version 5.0 but works in 5.1
> ----------------------------------------------------------------------
>
>                 Key: JBRULES-2515
>                 URL: https://jira.jboss.org/browse/JBRULES-2515
>             Project: Drools
>          Issue Type: Bug
>          Components: drools-eclipse, drools-eclipse (expert)
>    Affects Versions: 5.0.1.FINAL
>         Environment: Ubuntu 10.04, AMD64, Eclipse 3.5 (Linux 64), java version "1.6.0_20"
>            Reporter: Peter Marks
>            Assignee: Mark Proctor
>            Priority: Minor
>             Fix For: 5.1.0.M1
>
>
> In version 5.0, setting a breakpoint in either the java code or in the RHS of a rule fails because the debugger is unable to start. The error is:
> FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
> ERROR: transport error 202: connect failed: Connection refused ["transport.c",L41]
> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
> JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
> A breakpoint set in a Java program worked OK.
> I loaded the 5.1.0.M1 drools-eclipse plugin. Debugging a Drools appllication works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira