Re: [rules-users] Problems debugging on Eclipse 3.5

My answers below.. On Tue, Nov 24, 2009 at 3:18 PM, Kris Verlaenen < Kris.Verlaenen(a)cs.kuleuven.be&gt; wrote: > Do you only have this when you run this using "Debug as Drools JUnit > test" and not when you debug this as a normal JUnit test? Normal unit-tests run fine, I just can't put a breakpoint on my rules. > And if you > turn this into a normal class with a main method, do you still have this > when using "Debug as Drools application" and/or "Debug as Java > application". > I got that behaviour at work, but now I just tried at home and had the same problem. Here I'm on Ubuntu 9.10, jdk 6, Drools 5 and Eclipse 3.5 . > > And no firewall turned on that could cause this connection refused? > Not really. > > Kris > I actually installed Drools plugin via Eclipse's dropin folder. I'll remove it from there and try to install it via the regular update site to see what happens. Thanks, Kris. > Quoting Leonardo Gomes <leonardo.f.gomes(a)gmail.com&gt;: > > > Hi Guys, > > > > I'm having the following exception while trying to lauch "Debug as > > Drools > > JUnit Test": > > > > 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 > > > > > > I'm using: > > > > * Eclipse 3.5.0 > > * Drools Eclipse Plugin 5.0.1 > > * jdk1.5.0_18 > > > > > > Any ideas? > > > > Thank you, > > Leo. > > > > > > > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm >