You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/09/20 13:47:00 UTC

[jira] [Resolved] (MEECROWAVE-142) error while starting jpda debug in a bundle

     [ https://issues.apache.org/jira/browse/MEECROWAVE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved MEECROWAVE-142.
--------------------------------------
    Resolution: Fixed

> error while starting jpda debug in a bundle
> -------------------------------------------
>
>                 Key: MEECROWAVE-142
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-142
>             Project: Meecrowave
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Major
>             Fix For: 1.2.4
>
>
> On some servers and JVMs I got a weird Exception:
> {nocode}
> 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 [debugInit.c:750]
> {nocode}
> It turned out that some JVMs seems to be sensible about the order of the jpda parameters.
> All started to run perfectly fine if I changed the position of 'server=y' and the address parameter. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)