Naming Error shutting down JBoss server in JBoss Eclipse

[gzoller]

Hello,

I'm running JBoss Eclipse (latest beta) on Windows. On this platform I needed to change the JNDI port from 1099 to something else (1999) because something else had already claimed 1099. This works fine and I can launch and use the server from Eclipse.

My problem comes when I go to shut it down from the Eclipse "Server" tab. It's looking for naming at 1099, not my changed value of 1999. I thought I changed everything necessary in my JBoss config files, but I've apparently missed something either in the JBoss installed directory or in my Eclipse directory.

Any ideas where I should start looking?
Some people on the MyEclipse forum had a similar problem but I couldn't find the config file they were referring to.

Thanks,
Greg

[rob.stryker]

Greg:

I read a bug about something similar on bugs.eclipse.org. It seems the user there was using the webtools "generic server" adapter for JBoss, which is not what we use here. We use a custom server adapter.

I suspect strongly you're using the same thing.

The only thing I can think of to help you is that there is probably, somewhere in your plugins folder, a jboss-related xml file which the generic server uses to configure ports and such.

The folder should be something like: eclipse\plugins\org.eclipse.jst.server.generic.jboss_1.5.1.v200609140551\servers\jboss.serverdef

But, we suggest you use JBoss IDE instead ;)

If I'm wrong and you're not using the generic jboss server, feel free to respond. (You can tell by watching which category you create your server in. JBoss vs JBoss Inc. JBoss Inc. is the one we create / support. JBoss is provided by webtools.)

Take luck.

[gzoller]

Thanks for the response.

Actually I think this might have been an install error on my part. I moved my JBoss AS install aside and used the Windows installer to install a fresh copy. I got past that error and then got a problem with Authentication failing. Same thing happened from the command line. Searching this forum I found a fix where I can comment out some lines of XML in the jmx-invoker-service.xml file.

Now it's all good.

:-)