Thank you for your suggestion Maximiliano, debugging really works in Eclipse version 3.4 for me. So the problem is probably in compatibility with 3.5 (but maybe just on few specific configurations).

Bye

On Wed, Aug 19, 2009 at 3:28 PM, Maximiliano Batelli <maxibatelli@gmail.com> wrote:
Hello
I have the same problem when debuging rules using eclipse 3.5, drools 5.0 and jdk 1.6.
I downgraded to eclipse 3.4 and worked for me.
Is there a solution to let me debug using eclipse 3.5?

Thanks
Max




Hi,

I`m experiencing the same problems as Vishal. I am using Eclipse 3.5
and newest Drools. I am only able to debug project as Java
application, but when I want to debug it as Drools application all I
get is this problem. I also tried disabling firewall and changing its
settings but as it seems it does not help.
So if anyone has figured out a solution to this problem, I would
really appreciate an answer.

Thanks,
Jakob

probably related to your personal firewall:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6303969
http://www.techienuggets.com/Comments?tx=3786

I don't think this is a Drools specific issue.

Mark


Vishal Anand wrote:
>
**>* Hi,*
>
**>* *
>
**>* I am using Drools 5.0 and have create a simple application using *
>* drools flow, it runs perfectly but when trying to debug it as n drools *
>* application I get the following error:*
>
**>* *
>
**>* FATAL ERROR in native method: JDWP No transports initialized, *
>* jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)*
>
**>* ERROR: transport error 202: connect failed: Connection refused*
>
**>* ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510)*
>
**>* JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports *
>* initialized [../../../src/share/back/debugInit.c:690]*
>
**>* *
>
**>* *
>
**>* While stack trace shows the following:*
>
**>* *
>
**>* *
>
**>* java.lang.IncompatibleClassChangeError: Expected static method *
>*org.drools.eclipse.launching.DroolsVMDebugger.renderCommandLine([Ljava/lang/String;)Ljava/lang/String;
*
>
**>* at org.drools.eclipse.launching.DroolsVMDebugger.run(Unknown Source)*
>
**>* at *
>*org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:101)
*
>
**>* at *
>*org.drools.eclipse.launching.DroolsLaunchConfigurationDelegate.launch(Unknown
*
>* Source)*
>
**>* at *
>*org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
*
>
**>* at *
>*org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
*
>
**>* at *
>*org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
*
>
**>* at *
>*org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
*
>
**>* at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)*
>
**>* *
>
**>* *
>
**>* I am using eclipse 3.4*
>
**>* *
>
**>* What could be the issue ?*
>
**>* *
>
**>* Thanks*
>
**>* Vishal*

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org