Because of the --portbase=8000, the debug port winds up on port 8009 instead of the default 9009. The Eclipse Glassfish plugin doesn't seem to pickup on this and can't deal with it. If I create the domain without --portbase=8000, the debug port uses it's default 9009 and all is good. Note that this also fixed a problem related to the JMX port. In that case, I was getting exceptions at startup having to do with JMX and those have now cleared as well.

Hey John. I too am having SEVERE problems trying to get Indigo to start Glassfish. Numerous fresh installs of both Eclipse and the plugin haven't helped me. I'm getting a NPE when I try to start glassfish 3.1.

BTW, I doubt the Eclipse folks will be able to help. Last time I reported an issue, they referred me to the Glassfish guys because they wrote the plugin. Been down over a month now....Ready to throw in the towel and go back to NetBeans.

On 19-Sep-11 12:11, gbarnard wrote:
> Hey John. I too am having SEVERE problems trying to get Indigo to start
> Glassfish. Numerous fresh installs of both Eclipse and the plugin
> haven't helped me. I'm getting a NPE when I try to start glassfish 3.1.
> BTW, I doubt the Eclipse folks will be able to help. Last time I
> reported an issue, they referred me to the Glassfish guys because they
> wrote the plugin. Been down over a month now....Ready to throw in the
> towel and go back to NetBeans.

Or, file a bug and go back to Helios until the problem works itself out?

I dropped on this thread when failing to get debugging working between Glassfish 3.1.1 and Eclipse Indigo. The port number information set me looking for some domain config and I found the port numbering in my domain.xml file. Changing this config fixed it for me. So, changed: