geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jinmei Liao <jil...@pivotal.io>
Subject Re: Enabling debugging from gfsh launched components
Date Wed, 31 May 2017 15:42:09 GMT
I believe this is due to bug I introduced when working on gfsh parser when
dealing with --J option that has comma in the values. Will get a fix in
soon.

On Wed, May 31, 2017 at 7:41 AM, Jens Deppe <jdeppe@pivotal.io> wrote:

> Hi,
>
> In the past, when launching a server or locator with gfsh, I could specify
> debugging options like this:
>
> gfsh start locator --name=locator1 \
>   --J=\"-agentlib:jdwp=transport=dt_socket,server=y,
> suspend=n,address=5005\"
>
>
> I had to specially quote the agentlib options otherwise the commas would
> mess up the command parsing. Unfortunately, since various option parsing
> refactorings have happened, I cannot get this to work now. I just get this
> error:
>
> The Locator process terminated unexpectedly with exit status 1. Please
> refer to the log file in /Users/jdeppe/git/gemfire-develop/open/locator1
> for full details.
>
> ERROR: JDWP Non-server transport dt_socket must have a connection address
> specified through the 'address=' option
> ERROR: JDWP invalid option: -agentlib:jdwp=transport=dt_socket
>
>
> Is there some new incantation in order to be able to do this?
>
> Thanks
> --Jens
>



-- 
Cheers

Jinmei

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message