Hi,Don't you have another Karaf instance runing?Pax-exam will try to find a
newer free portregards,FrancoisEnvoyé depuis mon smartphone Samsung Galaxy.
-------- Message d'origine --------De : Paul Fraser <[email protected]> Date :
01/06/2019 16:04 (GMT+04:00) À : [email protected] Objet : Re: Debugging
Itests On 1/06/2019 7:10 pm, Jean-Baptiste Onofré wrote:> Actually, if you run
in debug mode directly in intellij, it works,> nothing special is required.Does
this mean it is not necessary to uncomment
"KarafDistributionOption.debugConfiguration("5005", true)"?> Are you running
your itests in IntelliJ ?Yes. Trying to..It seems that somewhere the port for
the connection to the java vm is not being set to 5005 but a random high
value.Should the port for the vm be set to 5005 by Karaf when debugging?Paul>>
Regards> JB>> On 01/06/2019 08:09, Paul Fraser wrote:>> On 1/06/2019 4:03 pm,
Jean-Baptiste Onofré wrote:>>> Hi Paul,>>>>>> What Pax Exam version are you
using ?>> pax exam 4.13.1 and Karaf 4.2.5>>>> Paul>>>>> Regards>>> JB>>>>>> On
01/06/2019 08:01, Paul Fraser wrote:>>>> Hi,>>>>>>>> The example itests code
has line>>>> "KarafDistributionOption.debugConfiguration("8889", true)
commented out.>>>>>>>> Presumably, the idea is to uncomment and debug of the
itest becomes>>>> possible. (for intellij set port to 5005 and remote debug
config set in>>>> intellij)>>>>>>>> When I try to debug the target connects
->>>>>>>> "Connected to the target VM, address: '127.0.0.1:52458',
transport:>>>> 'socket' " and then>>>>>>>> "Listening for transport dt_socket
at address:5005">>>>>>>> If I run debugging outside an itest with "bin\karaf
debug" , it works.>>>>>>>> What am I missing in the debug itests case?>>>>>>>>
Paul Fraser>>>>>>>>
