Skip to main content

Problem with Eclipse Plugin for Glassfish 3.1.2

5 replies [Last post]
Joined: 2012-03-09


my freshly installed Eclipse Indigo SR2 with a new workspace and the recent released GlassFish Server Tools produces an issue: Every time I start my Eclipse there will be add a new Glassfish Server Runtime Environment enty in my Server Tab.
First start: Internal GlassFish 3.1.2
Next Start: Internal Glassfish 3.1.2 and Internal Glassfish 3.1.2 (2)
and so on...

What's the problem?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2012-05-10

Do you know how to add mysql-connector-java-5.1.18-bin to this internal glassfish 3.1.2.

If I have stand-alone instalation of glassfish 3.1.2 I just put this jar in glassfish\modules directory and it work.

But with this internal I can't find where to put this jar.

Regards, Tomaz

Joined: 2012-05-10

I figure it out it should be put in directory


Regards; Tomaz

Joined: 2006-03-08


is there any way to prevent the GF plugin from installing any internal servers? I don't need and use that at all. I need to keep several instances anyway and setting them up manually is easy.


Joined: 2012-01-04

It was caused by bug in runtime plugin. Now it is fixed and you can download new runtime plugin at update site (or juno, depends on what you are using). You have stil to unistall old buggy runtime - see the guide here

Note: I don't recommend to install plugins from Eclipse marketplace, there are only old versions there. It may worked for this case because eclipse leaves uninstalled plugins inside plugins directory..

Joined: 2012-03-17

The same thing happened to me when I installed the tool by adding

as an update site and used "install new software". The following worked for me: uninstall everything installed from that update site

and install Glassfish Java EE Application Server Plugin from Eclipse Marketplace. This keeps the previously installed 3.1.2 as

the installed runtime (though it could be that 3.1.2 also ships with this one, I'm not sure) and eliminates the problem you described.