We have recently installed Orbeon Forms stable 3.8.0 CE's orbeon.war and that works out of box.
Because some features do not work in the stable version we installed the CE nightly build orbeon-CE.war, but this one does not work out of the box.
Form builder has some exceptions. Not only the builder fails but the examples too, so Form runner too.
Java exception
java.lang.NullPointerException
class: java.util.zip.Deflater
method: ensureOpen
line: 421
We are using Linux Debian Lenny 2.6.26-smp, Tomcat 5.5.
Probably we are running into some undocumented requirement for this nightly build...?
Problem identified and workaround:
We use IBM java 1.5 and this is what we found.
Orbeon stable works OK with IBM java 1.5, Orbeon nightly does not work with IBM java 1.5, see previously mentioned zip error.
We then installed SUN java 1.5 and Orbeon nightly works OK with SUN java 1.5., but first there was a problem:
*Exception in thread "exist_QuartzScheduler_QuartzSchedulerThread" java.lang.OutOfMemoryError: PermGen space*
And we googled up this thread:
http://orbeon-forms-ops-users.24843.n4.nabble.com/Data-lost-on-quot-Save-Document-quot-td40450.html
The permgen space is a separate VM
setting. It can be increased with a
VM option, e.g.:
-XX:MaxPermSize=128m
Which solved the problem.
This is not a known issue, and this is something I am unable to reproduce here. Maybe the download you got was corrupted. Try to unzip the war file by hand (e.g. with unzip), and if this gives you an error, re-download a new war. If this doesn't solve your problem, could you update your question with more information, in particular the full stack trace for that NPE?
Related
I am trying to upgrade Jenkins from version 2.176.1 to 2.375.2. I tried two methods and both of them failed.
Method-1: Download the jenkins.war and copy it into /usr/lib/jenkins/ directory by replacing the original one. After copying, when I restart Jenkins, it simply fails to restart.
Method-2: Upgrade Jenkins' RPM using yum update jenkins. This command runs successfully and process exists without any error. But, again when I restart Jenkins, it fails to start.
CentOS version: CentOS-7
First of all - I can only support opinion of Dmitriy Tarasevich about reading upgrade guides. You can find theme here: https://www.jenkins.io/doc/upgrade-guide/
Then - stick to the version upgrade process that you've used previously (or for the first time with installation). If you did install it via .*war, don¨t worry and use your Method-1. On the other hand, if you used yum, stick to that method-2.
Then - such a "big" upgrade at once from 2.176.1 to 2.375.1 is, I'd say, the reason it's failing for you as the version in between contain several major/breaking changes (our team has faced the same problem (we "just" wanted to bump the versions too much after a long time of no upgrading and we've faced several problems we weren't able to solve together). So it was necessary to split it into several independent upgrades which appeared to be doable and we managed to get to LTS 2.375).
To summarize recommended steps - I'd you need to:
1/ Split your upgrade into several steps and upgrade LTS more gradually: try to upgrade to first to some not-current LTS version. I believe something less than or precisely 2.303.3 could work and see if you can start it.
then actually run Jenkins and check administration page,
upgrade your plugins (if you want). FYI: this is recommended officially in Jenkins docs after every Jenkins core upgrade.
check Jenkins administration page and apply necessary changes / manage necessary decision that might appear there (if applicable).
2/ Try to upgrade to a higher LTS version (repeat step 1 with its sub-steps)
To be a very specific and give some examples (although I don't remember everything by hearth):
you skipped a gradually upgrade to version 2.319 LTS that brings a major change of working with master node --> built-in node that needs to be applied (confirmed) from within the administration section of Jenkins (see docs: https://www.jenkins.io/doc/book/managing/built-in-node-migration/ )
version 2.332.1 LTS brings an important change. I would say that you've hit exactly this issue (covered here): https://community.jenkins.io/t/jenkins-cant-find-java-after-update-running-on-centos-7/3615 - exact steps and more resources are within that thread and also here: https://www.jenkins.io/doc/upgrade-guide/2.332/#upgrading-to-jenkins-lts-2-332-1
from version 2.361 LTS Jenkins requires Java 11 or higher (see docs https://www.jenkins.io/doc/upgrade-guide/2.361/ ). So - you will need to ensure that you have a proper Java installed (you already might have it though). Including your agents!. Otherwise you would start your Jenkins but it would not connect any agent (usually undesired state).
Please, try to make some gradual progress and let us know where you managed to get
I've recently been trying to set up a Jenkins server that uses the Jenkins MKS plugin for version control. I had a Windows Jenkins server that was running this same configuration just fine, and now that we're moving it to a linux server (Red Hat Enterprise Linux Client release 5.1 Tikanga), it doesn't seem to be able to download the files. The folder structure is built perfectly fine, which tells me connecting to the server isn't the problem, but the files aren't populated in the folders.
Jenkins System Log:
Sep 02, 2016 11:15:46 AM WARNING org.apache.commons.httpclient.HttpMethodBase readResponseBody
Unsupported transfer encoding:
Sep 02, 2016 11:15:46 AM INFO org.apache.commons.httpclient.HttpMethodBase readResponseBody Response
content is not chunk-encoded
Sep 02, 2016 11:15:46 AM INFO hudson.model.Run execute
Test #67 main build action completed: FAILURE
Any suggestions on what I can do to check if my data/files are chunk encoded, or why this would be unique to a linux server? I realize we’re 3+ years behind on our configuration, but IT here has tight restrictions on what software can be installed and updated. Any troubleshotting suggestions or help is much appreciated!
Config Details:
Jenkins Version 1.596.3
MKS Plugin Version 1.16 MKS Server: MKS Integrity Client 2009, Build
4.10.0.9665, SP 007-01
Jenkins Slave info: Red Hat Enterprise Linux Client release 5.1
(Tikanga)
Java version 1.7.0 Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server_VM (build 21.0-b17, mixed mode)
Similar issues / Research:
This issue report perfectly describes my problem, but the comment section suggests that the Java 7u40 update causes the issue, whereas I'm on an earlier version of Java.
https://issues.jenkins-ci.org/browse/JENKINS-21638
This issue describes the log error I'm seeing, but comment section suggests it was solved by Jenkins version 1.577. We're using a newer version of Jenkins. https://issues.jenkins-ci.org/browse/JENKINS-16985
You're using Integrity 10.9: As per the Version 2.0 (Jan 27, 2016) entry on the Plug-in's page:
IMPORTANT – PTC Integrity Plugin 2.0 is not backward compatible.
Please create new Jobs.
Productized version of PTC Integrity Plugin
compatible with PTC Integrity 10.9. Versions older than Integrity
10.9 are no longer supported.
I think what Cletus is trying to explain in that post is that both the version of Java used to build the plug-in and the version of Java running Integrity should be the same, and in the case linked for JENKINS-21638, changes in the 'File' object after Java 7u40 are preventing the plug-in from fetching files from the server.
If you were on a version of Java earlier than 7u40 (e.g. 7u25) it should work. Integrity 2009 SP6 (and hence the mksapi.jar file) were compiled with Java 6, so it's likely you're running into a similar issue there. Having said that, I'm working on an educated guess here, so you'd actually need to test that to see if it works.
We have Jenkins installed and running on a WebSphere Application Server. We recently upgraded the server to version 8.5.5 and switched the profile to use JDK version 1.7. Doing this Jenkins Crashes the WebSphere Application Server and we cannot tell why. Any hints or suggestions on things to look at? Switching the server back to JDK 1.6 seems to work just fine, can Jenkins not run on JDK 1.7 or is it something else?
I'll assume that by crash the websphere application server you mean either a fatal error at startup or a java process crash. Those can have many causes.
Just to give some ideas, it may be related to the fact that you had somewhat customized your JDK install and forgot to re-apply those customization to your new JDK. Or that switching SDK requires you to switch command line options, or that you indeed hit an incompatible class in the stack, or that your process crash because of bad luck, etc.
So please find more information in the logs, either the corresponding stack traces in your WAS server logs or the javacores crash files.
Please also report your jenkins version.
As for JDK 7 compatibility, latest jenkins itself should be compatible, yet some plugins are not
You may also want to read this: https://stackoverflow.com/questions/17411717/jenkins-on-websphere-reports-java-lang-noclassdeffounderror-jenkins-model-jenki. Maybe you have the same issue.
If you indeed find out an incompatibility, please report an issue in jenkins issue tracker and consider updating the Jenkins Websphere wiki.
I searched for an answer to this, but was unable to find anyone else having the same problem.
This is the first time I've tried to use Neo4j.
I'm running on Windows Server 2008 R2 Standard.
I downloaded and unzipped Neo4j Community 1.8.2 for Windows.
In a command window, I switched to the bin folder and ran Neo4j.bat.
I received the following message in the command window: Unable to locate jvm. Could not find HKLM\SOFTWARE\JavaSoft\Java Runtime Environment/CurrentVersion entry in windows registry.
I verified that I have the latest JVM.
I verified that the above registry key is not present in the location shown, but I did find it at HKLM\Wow6432Node\JavaSoft\Java Runtime Environment/CurrentVersion.
How should I proceed?
Thanks for any direction!
I Fixed this problem by making a new environment variable JAVA_HOME and pointing it to my Java installation folder
C:\Program Files (x86)\Java\jre7\bin
try to set up the java PATH variable to the correct path. tutorial here:
http://java.com/en/download/help/path.xml
than, newest java are i think by 2 version newer than the original java for neo4j 1.8.2. a remind myself some problems with such versioning few months ago - i solved it by running neo4j in the newest versions of 1.9.0x
I installed JRE version 6 on my machine and this cleared the problem. (I previously had version 7 on the machine.)
Set the JAVA_HOME path in your environment variables.
i am using virtual dedicated server and the configuration is windows server 2008 R2 standered edition. I recently upgraded it to PHP version 5.3.10(thread Safe version). I Installed PHP ImageMagick version /ImageMagick-6.6.3-0-Q16-windows-dll.exe by following the steps given at http://gary-greendale.blogspot.in/2011/01/install-php-imagemagick-and-imagick-for.html
I got my php ImageMAgick working finally(after nth attempts) using command prompt. but now i am tryin to use php_imagick.dll to load iMagick Library with PHP.
After thousands of efforts and lots of dll files replaced (tried many versions)
http://valokuva.org/builds/
http:+//valokuva.org/builds/ext/vc9/nts/imagick/2011-04-25_1849/
http:+//valokuva.org/builds/ext/vc9/ts/imagick/2011-04-25_1849/
and many other thread and non thread safe versions. Please suggest me the correct version of the php_imagick.dll so that i can get it running on my server.
I am sure the issue is related to php_imagick.dll's version.
Its kinda urgent now help please
The problem is that those versions at valokuva.org are VC9 and versions of ImageMagick after 6.6.2-10 are VC10. Basically, you're going to need to downgrade to an earlier version of ImageMagick if you want to run it with those IMagick binaries.
I know this because I just dealt with it today and found the solution on an Apache forum. Once I downgraded to 6.6.2-10, it started working.
Here's a link to the forum post...