This content has been marked as final. Show 5 replies
In your email, you have mentioned that "*I have debugged a single remote server before by modifying the startup Java option*"
Why dont you try the same across the cluster? you can perform the same startup options in cluster and check / debug the issue
you can set those debug parameter with in setDomainEnv.sh file under java option that will consider to entire Domian as well as cluster.
If you only like to do it towards cluster then you need to it separately.
Thank you both for your answers.
I have set the options in my startup command line for both nodes in the cluster, but was then confused about how to connect to the cluster as an entity. When I remote debug in JDeveloper it asks for a host:port, so am confused about what to enter there.
Kal, can you provide an example of configuration in the setDomainEnv.sh script and what details one would enter in JDeveloper?
setDomainEnv.sh or .cmd file will not available on Jdev you need to check Domain directory and under that you will find bin folder you will find that setDomainEnv.cmd in case of windows or .sh file in unix based OS.
edit it under java_option.
I understand where the setDomainEnv.sh script is, but I do not understand what I must enter in the JDev remote debugger dialogue. It prompts for hostname and port.