SOLVED - See bottom of post
Firstly, I will state that I have read all the existing posts regarding this problem and none of the suggested solutions have worked.
After upgrading eclipse to Indigo SR2 and to java 7, I was not able to start Glassfish, either embedded or separate installation.
After a week of this and because my PC was getting sluggish, I decided a full rebuild of my PC was required, so I reset the PC back to factory settings and started again.
My spec now looks like this...
Windows XP SP3 - Firewall Disabled as 3rd Party solution installed
Java 7 - jdk1.7.0_03 + jre
Eclipse Indigo SR2
hosts file...
127.0.0.1 localhost
I installed the latest Glassfish Plugin from: http://download.java.net/glassfish/eclipse/indigo
However, just as before the rebuild, when I try and start the server, I get the CREDENTIAL_ERROR.
I'm now super frustrated as I would have expected this completely clean install to just work.
I disabled the firewall, but that made no difference.
I then tried to start the embedded server manually. e.g. asadmin start-domain, and it started fine. I can stop it from Eclipse, but as soon as I try and start it again I get the CREDENTIAL_ERROR. Grrrrhhh!!!
I also spotted this entry in the eclipse .log file...
!MESSAGE GlassFish: error reading one jmx portjava.lang.NumberFormatException: For input string: "${JMX_SYSTEM_CONNECTOR_PORT}"
...which may be relevant as the final line of a verbose manual startup of the server looks like this...
[#|2012-04-09T15:33:16.625+0100|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=41;_Thre
adName=Thread-23;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://HOME:8686/jndi/rmi://HOME
:8686/jmxrmi|#]
Many thanks
Chris
SOLVED
Darn it. Just after posting this, I stumbled upon this link...
http://java.net/jira/browse/GLASSFISHPLUGINS-72
...which suggested that the Anti-Virus (not the firewall) being the culprit and lo and behold, it was. I removed port 8080 from scanning and the server fired up without a problem.
Now I need to work out if I've opened up a security hole.
UPDATE
I decided to install a separate Glassfish instance and the problem started over again. In then end I discovered that I had to disable the NOD32 HTTP Scanner entirely to allow the server to start. Re-enabling it got the CREDENTIAL_ERROR again. There didn't seem to be any configuration setting that would get around this. I'll have to fire an email off to ESET to see what they suggest.
I'm working with about the same configuration. Only my eclipse is Version: Indigo Service Release 1, and I work in an environment where it isn't allowed to disable a firewall.
In my case it helped to switch to a previous version of Java (jdk6-u30), which wasn't what I intended. So I installed the newest version of the JDK at this moment: jdk1.7.0_04, and used this as the -vm value in de eclipse.ini.
This still left some complains about a Currentversion of 1.7 when 1.6 was expected by our version of Glassfish's asadmin. Which were worked around by changing the registry back to 1.6, instead of the 1.7 version added by the installation of the jdk1.7.0_04.
After these changes I could start and stop Glassfish from within eclipse without the CREDENTIAL_ERROR.
Related
I'm trying to install Netbeans 8.2 Java EE, but whenever I start the installer it quits after configuring it. I am trying to install it on Windows 10 64-bit.
This is not going to make sense at all, but do you happen to have the "God Mode" item on your desktop? Take it off the desktop (delete it, move it somewhere else, whatever). I have no idea why, but it worked for me: I found the solution in this bug report - https://netbeans.org/bugzilla/show_bug.cgi?id=269988
I do hope this helps you, too.
This is an Java issue, which was came up due to recent windows 10 update, that started treated differently for GodMode folder/shortcut.
This has been already fixed - https://bugs.openjdk.java.net/browse/JDK-8179014
You can verify the fix in early access build of JDK8 update 152, which is available here
We have verified the issue only with GodMode, do let us k now if there are any other scenarios that can cause such similar issues.
I'm adding this because: I had a different issue which I was unable to find addressed anywhere, this question appears near the top of a web search for "NetBeans 8.2 ee won't install on Windows 10", and someone else may have the problem I had.
My NetBeans install was almost immediately crashing with the following error:
An unexpected exception happened in thread main
Exception: javax.xml.parsers.FactoryConfigurationError: Provider for
class javax.xml.parsers.DocumentBuilderFactory cannot be created
In my Windows 10 System Properties -> Environment Variables -> System Variables, I had a previously created _JAVA_OPTIONS variable values using -Xbootclasspath/a to append some jar files to the end of the bootstrap class path. These files are used with some work I'm doing with the Oracle BI Publisher plug-in for Microsoft Word.
As soon as I renamed the _JAVA_OPTIONS variable to something else, my NetBeans installation started normally and completed with no issues.
After NetBeans installation, I reset the name of this variable back to _JAVA_OPTIONS, and discovered that the values I have for this System Variable cause NetBeans launch to crash. (Which does not completely make sense to me since I am only appending these files/classes to the class path, and not overwriting.)
Regardless, I'll have to go back to the drawing board for my work with the BI Publisher plug-in; but at least I can use NetBeans now!
Uninstall any Java installations along with NetBeans, and install Java with NetBeans (bundle) from the Oracle website.
I had the same issue, and then installed the bundle, works perfectly.
for the past several days I've been experiencing this error, while publishing to either JBoss EAP 6.3 or Wildfly 8.2 from Eclipse.
Error renaming D:\Servers\wildfly-8.2.0.Final\standalone\tmp\tmp9064011157118650757.jar
to D:\Servers\wildfly-8.2.0.Final\standalone\deployments\BusinessService.war\WEB-INF\lib\spring-web-4.2.3.RELEASE.jar.
This may be caused by incorrect file permissions, or your server's temporary deploy
directory may be on a different filesystem than the final destination. You may adjust
these settings in the server editor.
The problem occurs when I "Add and Remove..." projects from the server, then try to publish them, so the server can start.
I've experienced this issue on two different machines (home (Wildfly) and work (JBoss EAP)).
I'm using:
Windows 7 / 10
Eclipse Mars / Luna
JBoss Tools plugin 4.3 / 4.2
JDK 1.8.0.66 / 1.8.0.65
Maven
Building with maven from Eclipse and from the command line makes no difference. The server is configured to deploy projects as compressed archives. On both machines my user has administrator rights and has full rights on the server directory.
So far I've tried:
recreating the server multiple times with different configurations
using a newly created workspace
reinstalling JBoss Tools
reinstalling Eclipse
using different JDK versions
I'm really at a loss here and I don't know how to proceed in resolving this issue. Please help.
If you are using Windows, the path could get too long and can cause this error. A simple fix is to move WildFly closer to the root.
I had the same problem and solved it like this:
First of all, stop Server (Servers->WildFly(rigth click)->Stop), than clean. So you can run server again.
I had this problem several times in my new windows 10 machine that my employer gave me. Since I did not have admin rights it was a hectic process to troubleshoot this issue. Simple fix would be moving JBOSS_HOME closer to root. However, you need to do a proper restart of your eclipse. I rather recommend a complete restart of your computer because after all you are going to change JBOSS_HOME in windows environmental variables.
This is related to permissions issue on wildfly folder. Allow full control to the wildfly folder.
https://issues.jboss.org/browse/JBIDE-18697
I have moved the wildfly home to reduce the overall path length, and also removed any non-alphanumeric characters from the folder name (like "-" and "." ) . This worked for me, everything else (removing tmp, deployment, rebooting wildfly, rebooting eclipse, rebooting computer) failed.
I also suspect that the issue was stemming from running Wildfly from a ConEmu and/or git bash shell. Running from a plain CMD shell seems more robust.
I also got stuck with the same problem. I tried the below steps and it worked:
Clear the deployments and tmp folder in standalone folder in wildfly folder.
Delete the server and again add the server
Make a build of the project and start the server after successful build.
This is a terribly annoying error that either the Eclipse team or Redhat need to fix.
The solution is to close Eclipse, right click on the icon -> Run As Administrator. This solved it for me.
So I created a Websphere Application Server in Eclipse and pointed it at my WAS_HOME and the profile I created. Whenever I try to start the server, it starts fine and according to the log I see...
[2/22/12 14:16:25:037 EST] 00000000 WsServerImpl A WSVR0001I: Server server1 open for e-business
However, Eclipse says it is still waiting to start, typically it sticks at 23%. Eventually it times out saying it couldn't start, however, the instance is still up and running fine.
How do I get it to recognize the running instance?
Your workspace folder/name could be the issue.
or for me it was the WAS installation itself. When I moved it to C:\was8 everything started to work properly. The default puts it into c:\Program Files... and that was hanging at 23%
a. Please use websphere jre to replace sun hotspot vm to launch the eclipse, like below setting in the eclipse.ini
-vm
D:/IBM/WebSphere/AppServer/java/bin/javaw.exe
b. Please make sure there is not a specail character (like 23%) in the websphere path or eclipse workpsace.
Recently, I've got the same problem with Eclipse Luna and Websphere Developer Tools... The problem was the eclipse proxy configuration
Increase the initial and max heap sizes of the VM that is loading Eclipse.
First of all this question has been asked at least twice.
I tried several approaches with no effect.
Here's the problem:
When I try to download/update plugins like EclEmma, Eclipse starts to communicate with the repository and that takes about 5 minutes. After that I get an error:
"An error occured while collecting items to be installed
session context was:(...)
Unable to read repository at http: (...)
Read time out
(... for every *.jar)"
What I was trying to fix the problem was running eclipse as an admin (got vista x86 running) and changing the connection properties from native to direct and back. I also tried deleting saved repositories and adding again. No effect at all.
I have no proxy configured and don't need one.
This is getting kind of personal between me and my IDE :D
So I hope you guys can help me out.
Thanks Zoltán (köszi :D), but i found the error last night.
Resolution
After hours of debugging I figured out that AVG Anti-Virus Software blocks the request. After deactivating it for temporarily, Eclipse installed the new software.
In my case timeout was caused by definition of SOCKS proxy... we have proxy.company.com:80 and I incorrectly provided that proxy to all three (HTTP, HTTPS and SOCKS) connection schemas. Removal of proxy from SOCKS resolved the problem
Try to open the internal web browser of Eclipse (Window menu/Show view/Other...), and navigate to the 1) update site url, and 2) to any webpage.
If the latter one is not working, then Eclipse does not have connection to the internet, and you should try to open a new workspace, and try installing from there (possibly something wrong in the workspace settings).
If the second one works, but the first one does not, that suggests that the update site is not working. In this case report to the developers.
I also had this problem (my system: Win7, jdk7, Eclipse Indigo).
I installed jre6, changed my JAVA_HOME, ran eclipse with the following:
eclipse -debug -consolelog -vm 'c:\Program Files\Java\jre6\bin\java.exe'
Install the plugins/updates, then switch back to using jdk7.
Worked for me!
Temporarily disabling AVG firewall fixed the issue for me.
Eclipse then installed the Android plugin.
In my case, adding these lines to eclipse.ini solved the problem
-vmargs (this one was alreayd there)
-Djava.net.preferIPv4Stack=true
I have reinstalled java JDK 6.0.25,(after some problems installing java, finally succeeded). I have set paths (JAVA_HOME points to C:\Program Files\Java\jdk1.6.0_25 and in Path also added C:\Program Files\Java\jdk1.6.0_25\bin).
In eclipse I have pointed everything to this new JDK, also in servers. When I have installed Glassfish 3.1, after installation the domain wasn't created. So when I add this server in Eclipse, the domain wasn't found.
So I did extract an ZIP version of Glassfish and in Eclipse configure the server to this ZIPPED Glassfish. Also I have installed tomcat 7.0.14 again and add to eclipse but both did not work.
Main problem: When I start Tomcat or Glassfish in Eclipse they don't start. Tomcat is starting but after 45 seconds it says, that the time is run out. I have read the forums to increase starting time, I have putted it to 240 sec, but it does not work, because it pop out error in which sazs, that the port is already used by a different server.
By Glassfish, when I start it, its starting, but after few minutes gives me error: Failed to start. It looks like some ports or something is blocking this servers. I have turned off firewall also and antivirus but nothing.
I have looked all the forum about "not starting Glassfish or Tomcat" but didn't found the solution. I don't want to reinstall windows for this.
So if anyone know anything about this problem, please HELP.
Update:
I've tried to change the ports in domain.xml and checked with netstat -b (everything was established), but the server (Glassfish) didn't start. It shows an error "Server GlassFish Server Open Source Edition 3 (Java EE 6) at localhost failed to start.". I've also tried install "built in Eclipse" Glassfish from marketspace and from "Install new software" from eclipse, but it comes out with the same error. Currently, for needs I'm using XP Mode in Windows 7, there servers work, without any problems.
It seems your installation odyssey messed up your system.
But you should get it working without reinstalling Windows. Maybe the fragment of an old server installation blocks the ports Glassfish and Tomcat need for operation.
Try the following:
Check which ports your "new" servers try to access (should be something like 8080 and should be written in server logs during startup)
Use netstat -b (from cmd started with admin rights) to check which application blocks this / these ports (could be java.exe if there is an old installation still hanging)
Remove the old installation (uninstall or disable service)
Try again to start your new server(s).
Try tell to GF or TC to bind the default web listener other port than 8080, because this is a root of problem.
I doesn't know well TC, but in GF case, this is very easy. Simply edit $GLASSFISH_HOME/domains/domain1/config/domain.xml and find something similar:
<network-listener port="8080" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>
And replace 8080 with other port (but not same with TC). In your case I could choose 8888 which is easy to remember but you can pretty sure this is differs from TC's port.
Note: Edit this file before you start GF!