after a BSOD in Windows 7 something gets corrupted and NetBeans cannot start a local WebLogic 10 server it didn't have any problems with before.
there is also a peculiar message appearing in NetBeans notification, with message and stacktrace almost identical to those reported in a filed NetBeans bug report:
java.lang.IllegalArgumentException: hostname can't be null
at java.net.InetSocketAddress.<init>(InetSocketAddress.java:139)
at org.netbeans.modules.weblogic.common.api.WebLogicRuntime.ping(WebLogicRuntime.java:623)
at org.netbeans.modules.weblogic.common.api.WebLogicRuntime.ping(WebLogicRuntime.java:612)
at org.netbeans.modules.weblogic.common.api.WebLogicRuntime.isRunning(WebLogicRuntime.java:500)
at org.netbeans.modules.j2ee.weblogic9.optional.WLStartServer.isRunning(WLStartServer.java:124)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance$3.run(ServerInstance.java:902)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
I tried multiple restarts since then, multiple netbeans restarts, tried even both NetBeans 8.1 and 9 - when starting WebLogic, NetBeans just is stuck with "Starting ..." message and never stops. You actually have to forcefully close NetBeans to stop this.
at some point i tried to start weblogic outside NetBeans, and saw that it was failing to start, with a message approximately like this from this Oracle forum thread:
<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141268]Parsing Failure in config.xml on line 1, column 1: Content is not allowed in prolog.>
Well, indeed there is a directory inside WebLogic domain I was trying to start called "config", with a file "config.xml" there (and a config.loc - deleting it didn't make any difference) - so I tried to look into config.xml and WOW it was totally corrupted. So that was the reason nothing started. I tried to just delete this file (config.xml) (in the above Oracle forum thread they also suggest to delete the domain - but this was not an option for me as it wasn't an integrated server) - after trying to start the server manually again, WebLogic starter script politely asked me if I want it to create a new default config.xml, since the old one was not found - answering yes worked and I am back in business (i hope :P)
of course, i lost some (EDIT: not all) of the custom settings i did in WebLogic configuration since installing it - I lost the custm data sources, but users and user groups were retained. if only i had backed up this config.xml :( anyway.
(EDIT: probably backing up config.xml wouldn't make sense - anyway - i think it keeps the reference to data source for all the deployed applications - so - you don't have to recreate a data source - you just have to redeploy your application(s))
Related
I am trying to install tomcat 9 using apdoptopenjdk jdk-11.0.6.10-hotspot on windows server 2008 R2. The tomcat starts properly from the command prompt when I ran startup.bat.
I have mentioned correct JVM path in the tomcat configutation dialog box and the mode is also set to JVM. Have cross checked this configuration multiple times and found no issue with it.
But it won't start when I ran from services.msc as a service.
The issue I get when ran as a service is 1067 terminated unexpectedly. And when I check the system logs in event viewer it shows below error.
Please help me as I am trying this since last two weeks.
I think this is a tomcat bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63767
I'm following up something similar, but your issue appears to have been fixed in 9.0.27
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.
I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log
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.
I am using eclipse 3.5 with google app engine + spring framework to develop application. My problem is when I change the code and build the project, the new code doesn't come in to effect. I even deleted the old file but at runtime, the old version gets display in the browser. Why?
Your description is not explicit, so following are my assumptions:
You are changing jsp/js or view related files
You have Google app engine plugin for eclipse to deploy the code
Following might be one of the reasons:
Your view files are cached in the browser, so try deleting the browser cache
Google app engine might have cached your files, so try deleting the temp folder
Eclipse IDE wouldn't have deployed your changed code, so check the timestamp, if it still shows the old timestamp, then find out how to configure eclipse to detect your changes.
I found 3 workarounds for similar issue (changes to a servlet (.java file) were not taking effect).
Before editing the .java file, stop the application. It seems that if you edit it while running, the issue occurs, even if you edit it, stop then re-start.
Delete items in Temp folder e.g, (C:\Users\username\AppData\Local\Temp), then stop and re-start the app.
I think the culprit folder in the Temp folder is this:Jetty_127_0_0_1_8888_war__.g0qk00
Right click in in the console area and select 'Remove All Terminated'. Sometimes that reveals there are other instances running, which need to be stopped by clicking the terminate button.
I got the similar issue and the problem was due to not stopping the running server.
What i was doing was running the server, editing the java file, saving and again running the server. This created two instances of the server running and when checking into the browsers the old code was executed from the first instances.
So, the solution is terminate and relaunch the server, and your new changes will be in effect.