Glassfish 3.1 CREDENTIAL_ERROR in Eclipse

Question

I can\'t start Glassfish 3.1 on Eclipse Indigo with \"Oracle Glassfish Server Tools\" plugin on Windows 7. After installing the plugin, I\'ve chosen \"New\" -> \"Server\" in

Answer 1

On Mac OS 10.6 I had many of the same problems described above:

1. First I had the CREDENTIAL_ERROR.

2. I tried creating a new server, as suggested in answer 2. However, I accidentally added the wrong password (it should be left blank), and started getting "wrong user name or password" messages. I was not able to change the password.

3. I then started getting the CREDENTIAL_ERROR again.

4. The solution was suggested by answer 3, that there is another process running. I decided to try completely deleting all of the servers on my Eclipse setup, and then adding a new server, as described in answer 2.

That worked beautifully, and I was immediately up and running (remembering to leave the password blank this time through)

Answer 2

I got the "The Eclipse plugin cannot communicate with the GlassFish server, status is :CREDENTIAL_ERROR" error too.

For me it was a Firewall problem. -- For some reason the Firewall (configured by the IT) blocks eclipse to communicate with Glassfish on port 4848, by default used as "Admin Server Port".

But port 8080 is not blocked.

My workaround was to switch the ports in the domain.xml

<network-listeners>
  <network-listener port="4848" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>
  <network-listener port="8181" protocol="http-listener-2" transport="tcp" name="http-listener-2" thread-pool="http-thread-pool"></network-listener>
  <network-listener port="8080" protocol="admin-listener" transport="tcp" name="admin-listener" thread-pool="admin-thread-pool"></network-listener>
</network-listeners>

Now I can start the server from eclipse. And access the normal pages in the browser (because 4848 is not blocked for the browser).

Answer 3

The reason your port swapping probably worked, is because when 8080 was the http listener it was likely that your anti-virus was scanning the port for http traffic, which causes the Credential Error. I removed the 8080 entry from my AV settings under web scanning and the server started up fine. Only took my a week and a half and a PC Rebuild before I found that one!!!!!

Regards Chris

Update: It turns out that I had to disable the HTTP Scanner entirely to stop this issue. As soon as it was re-enabled the CREDENTIAL_ERROR returned. I've tried adding all sorts of exceptions to the AV settings, but none worked.