Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot find java port #156

Open
mitchdraft opened this issue Apr 3, 2019 · 1 comment
Open

cannot find java port #156

mitchdraft opened this issue Apr 3, 2019 · 1 comment

Comments

@mitchdraft
Copy link
Contributor

@mitchdraft mitchdraft commented Apr 3, 2019

From Slack conversation on April 3, 2019

Configured my GKE cluster (using config map) with -agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=n

My JAVA_OPTS is

JAVA_OPTS: -javaagent:/usr/local/aspectjweaver-1.8.11.jar -Dcom.sun.management.jmxremote
    -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.port=9000
    -Dcom.sun.management.jmxremote.rmi.port=9000 -Dcom.sun.management.jmxremote.authenticate=false
    -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=127.0.0.1
    -Djava.net.useSystemProxies=true -Xmx3g -agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=n

Now, when I run the squashctl-windows.exe against my cluster, trying to debug a java service I keep getting -

Can't find port in java command line arguments for PID: 197711

and

{"level":"fatal","ts":1554296914.100451,"caller":"plank/main.go:27","msg":"debug failed!","error":"Can't find port in java command line arguments for PID: 197711","stacktrace":"main.main\n\t/workspace/gopath/src/github.com/solo-io/squash/cmd/plank/main.go:27\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}
@rverma-jm
Copy link

@rverma-jm rverma-jm commented Dec 27, 2019

even plank doesn't honor JAVA_TOOL_OPTIONS, which is a recommended way of passing java_opts. Jib uses same.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants