I am facing issue while installing any of the Jenkins plugins suggested.
Actually after downloading,Jenkins.war file(which is latest 2.141) when i tried to execute the jar with
java -jar jenkins.war so it gave me an error of Jenkins require java 8 but you are using 10. Also,it says that java class version 54.0 is running,but it requires java 52.0.
But I was able to resolve this issue by setting --enable-future-java flag.
java -jar jenkins.war --enable-future-java flag
Now,after writing this command,jenkins is up and running but i am unable to install the plugins.
Also,im cmd prompt after the Jenkins is upa d running.There is one error also.
PFB :-
Sep 17, 2018 4:38:49 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
[31mSep 17, 2018 4:39:02 PM hudson.model.UpdateSite updateData
SEVERE: ERROR: SHA-512 based signature in the update center doesn't match with the certificate in 'update site 'default''
[0mSep 17, 2018 4:39:02 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Download metadata. 15,407 ms
You need to add a flag which allows starting Jenkins with unsupported Java versions. You can do some google research on this.
If we change the Jenkins war file version from 2.141 to 2.814 then it is suitable with Java 10 and works fine for plugins installation of Jenkins
I'm setting up a new server for an application (node.js with Neo4j 1.8.3) that hasn't been used for a while. I installed Oracle JDK 7 (latest), which might explain this issue, as it's not recommended
for 1.8.3, will retest with JDK 6 tomorrow.
I installed Neo4J 1.8.3 on Thursday, on Ubuntu 14.04 running on Linode. Today I reviewed the log file (neo4j.0.0.log) and saw the following error:
Oct 02, 2014 5:02:48 PM java.util.prefs.FileSystemPreferences$1 run
WARNING: Couldn't create user preferences directory. User preferences are unusable.
After that there are numerous errors as follows:
WARNING: java.io.IOException: No such file or directory
Oct 02, 2014 12:00:46 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode
This discussion seems relevant,
java system preferences under different users in linux
But before trying this I wanted to ask here. Is this a known problem with a standard solution?
Neither of the example code snippets from the official Google Selenium Wiki (http://code.google.com/p/selenium/wiki/ChromeDriver) work for me. With either starting the Selenium server standalone or using the ChromeDriverService it hangs at line "new RemoteWebDriver(...)". Here's the output on my console:
/tmp/chromedriver: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory
Jun 29, 2011 8:46:58 AM org.openqa.selenium.net.UrlChecker waitUntilAvailable
INFO: Waiting for [Ljava.net.URL;#16df84b
Jun 29, 2011 8:46:58 AM org.openqa.selenium.net.UrlChecker$1 call
INFO: Polling http://localhost:21461/status
Jun 29, 2011 8:46:58 AM org.openqa.selenium.net.UrlChecker$1 call
INFO: Polling http://localhost:21461/healthz
Jun 29, 2011 8:46:59 AM org.openqa.selenium.net.UrlChecker$1 call
INFO: Polling http://localhost:21461/status
...
It is polling for healthz and status forever?
I believe this thread refers to the same problem as the one you're encountering:
http://code.google.com/p/chromium/issues/detail?id=13425
I had a similar problem. My Fedora had libbz2.so.1 in directory /lib64/ whilst Chrome was looking for it in /usr/lib64/
Solution was to create a symbolic link:
sudo ln -s /lib64/libbz2.so.1 /usr/lib64/libbz2.so.1.0
zilupe's answer lead me to the right answer for 32-bit CentOS:
sudo ln -s /lib/libbz2.so.1 /usr/lib/libbz2.so.1.0
Presumably his is right if you have 64-bit CentOS
suddenly for some reason tomcat server is not runnin/starting/stopping.
below is the result I get when i run the startup command,
C:\Program Files\jasperserver-3.5.0\apache-tomcat\bin>startup
Using CATALINA_BASE: C:\Program Files\jasperserver-3.5.0\apache-tomcat
Using CATALINA_HOME: C:\Program Files\jasperserver-3.5.0\apache-tomcat
Using CATALINA_TMPDIR: C:\Program Files\jasperserver-3.5.0\apache-tomcat\temp
Using JRE_HOME: C:\PROGRA~1\JASPER~1.0\java\jre
The tomcat window pops up for a split of a second and goes away.
(I have another java instance installed under c:\program files)
Help!!!
Update:
Logs from catalina file
Mar 22, 2011 3:41:50 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Mar 22, 2011 3:41:50 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1017 ms
Mar 22, 2011 3:41:51 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar 22, 2011 3:41:51 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.20
Mar 22, 2011 3:41:51 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 22, 2011 3:42:06 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Mar 22, 2011 3:42:06 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Mar 22, 2011 3:42:06 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/43 config=null
Mar 22, 2011 3:42:06 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Mar 22, 2011 3:42:06 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 15374 ms
Use catalina.bat run instead of startup.bat. Then the window won't go away and you can see what's going on
In my case that was a problem with final slash in %CATALINA_HOME% path: final slash should not be there!
C:\tomcat\8.0.30 - correct
C:\tomcat\8.0.30\ - wrong
See http://blackandwhitecomputer.blogspot.de/2015/09/tomcat-debug-cannot-startup.html
Honestly, I had not expected modern applications may be depended on final slash in environment variable path!
I ran into a similar problem. I open cmd prompt and cd to tomcat\bin\startup.bat. The issue was my JRE_HOME not defined in the environment variables. I added and it worked.
I had the same problem and I solved it this way:
First, following #ykaganovich suggestions, I tried to start the server using the catalina.bat start command; it did not solve the problem, but at least it showed a log that specified the error, which was really helpful.
In my case, the log said that the problem was because of the java versión. I had the JAVA_HOME variable pointing to the JDK7, but my tomcat version needed it to point to the JDK8.
I changed the JAVA_HOME variable to point to JDK8 (instead of JDK7) and then , when I executed the catalina.bat start command again, it worked perfectly and the server started. I hope my suggestion could be helpful to someone.
Hmm it's very strange problem because in the log you have that server started, so try this:
restart computer :) - the best solution for strange situations
change tomcat port
close every unnecessary applications: skype, ip phones etc (I've encountered similar problem someday and application ip phone "softly" blocked this port ("softly" - in tomcat log everything was OK but in reality webapp doesn't work)
Add tomcat in your eclipse and start it from there. Configure tomcat as 'Use Tomcat installation'. It will work
Had same problem with apache Tomcat 9 version.
Solution very simple.
Apache Tomcat 9 is supported by Java 8 and later versions.
So, i had JRE_HOME with JRE7 path, I binded it to new JRE8 and everything works fine.
Different versions of Apache Tomcat are available for different versions of the Servlet and JSP specifications. The mapping between the specifications and the respective Apache Tomcat versions is:
Hope this will work for you guys, cheers!
If Tomcat was earlier working fine and Tomcat not starting happens unexpectedly, it's because some other process has started using the port you were using Tomcat on. In my case, I had shutdown Tomcat and was trying to run my servlet directly from Eclipse. So Eclipse took control of the port. After I closed Eclipse and tried restarting Tomcat (with startup.bat), everything worked fine.
ykaganovich's answer helped me track down my issue.
Non of the solutions above worked for me.
I found my way out by removing my current tomcat and replace it with a new one and setting up again my workspace.
I hope this may help someone
Open up the Tomcat users file (tomcat-users.xml)and check that you've closed all your speech marks. That is what fixed it for me.
Now double-check the role names:
<tomcat-users>
<role rolename="admin" />
<role rolename="manager" />
<user username="admin" password="secret" roles="admin,manager" />
</tomcat-users>
Finally, execute startup.bat file from bin
Try to open Tomcat7w.exe or follow the below steps.
(I have installed Tomcat under folder C:\Program Files\Apache Software Foundation\Tomcat 7.0)
open command prompt as Administrator
run --> "C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7w.exe" //MS//
now you can see icon in the system tray
double click on icon and start/stop
I just got prompted for a Java update on my iMac machine. After the java update, my App Engine based Web Application (in Eclipse) won't start anymore.
The following was in the console (as usual) when I tried to debug it as Web Application:
<terminated exit value:139> myapp [Web Application] /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java (Mar 13,2011 7:20:27 pm)
2011-03-13 19:20:28.193 java[1772:903] [Java CocoaComponent compatibility mode]: Enabled
2011-03-13 19:20:28.194 java[1772:903] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Mar 14, 2011 2:20:29 AM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Mar 14, 2011 2:20:29 AM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Users/tom/Workspace/myapp/war/WEB-INF/appengine-web.xml
Mar 14, 2011 2:20:29 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Users/tom/Workspace/myapp/war/WEB-INF/web.xml
Mar 13, 2011 7:20:30 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8081/
And then the app just stops. The termination value seem to be 139. Why does this happen and how can I fix it?
Deleting the Java cache folder (~/Library/Caches/Java) (as posted in tom's link to the groups discussion) - although temporarily successful - did't solve the problem.
After re-installing the previous Java version, the eclipse GAE environment worked without any problems.