GlassFish 5.0 - Not a valid GlassFish Server installation

Question

I downloaded the GlassFish 5.0 from here because I was experiencing an issue with the JDBC connection pools in GlassFish 4.1.1 (and 4.0).

After unzipping the folder I tried to add the server to NetBeans and I received this error:

Not a valid GlassFish Server installation.

The found one potential answer here, but it didn't seem to help.

I am able to add other versions of GF into fine. Also, GF 5.0 runs, and it has fixed the previous issue I described in 4.1.1 which is nice.

One thing I noticed was that when I changed the name of the console-core file here:

glassfish4/glassfish/lib/install/applications/__admingui/WEB-INF/lib/console-core-5.0-SNAPSHOT.jar

to

console-core-4.1.1.jar

NetBeans actually recognizes the GF installation! I tried to go through the entire GF installation and replace references to console-core-5.0-SNAPSHOT.jar to console-core-4.4.1.jar, but after clicking "next" in the Add server dialog, it doesn't advance. I may have missed something, but it's still a major hack.

Answer 1

I know its a late answer But it may help other new to this issue.

Rename the console-core jar file to have version name limited to 2 figure i.e. if jar name is console-core-4.1.1 or console-core-4.1.2 or something like it then change it to as console-core-4.1 which is in the directory in my case

E:\Programs\Java + Databases\java_ee_sdk-7u3\glassfish4\glassfish\lib\install\applications\__admingui\WEB-INF\lib

In my case in the above directory jar file name was console-core-4.1.1 And I changed it to console-core-4.1. Now Everything is working fine. Its working with Netbeans and in browser too with url

http://localhost:4848

Answer 2

I had the same issue when I downloaded netbeans 8.02 and tried to add glassfish 5 server. After investigating for hours I found the solution. I had actually downloaded the Java EE bundle of netbeans 8.02 for installation. I uninstalled my netbeans and reinstalled using the Java ALL bundle installation file. Then the error went away.

Thanks, Mitesh