It is a project deployed in resin.the OS is Red Hat Enterprise Linux Server release 6.5 (Santiago)
it uses spring 2.5.6 and struts2 , .. for some reason ,we need to deploy it in jdk8 ,it is too complex to upgrade the spring version ,so we change one class in spring to make it support jdk8 ,It seems work well ,but after about half an hour , the cpu load rises to 10 ,sometimes higher than that . we have tried our best but havn't fount the reason . Is there goods suggestions to analyze the reason,or anyone meeting the similar problem ?
Related
I am planning to migrate a webapp from java 8/tomee 7.0.4 to java 11/tomee 7.1.0, but still unsuccessful. So I write a barebone webapp with only one facelet page and one managed bean. This works on java 10/tomee 7.1.0 but not java 11. The errors are:
java.lang.IllegalStateException: Cannot get Unsafe.defineClass
....
java.lang.NoSuchMethodException: sun.misc.Unsafe.defineClass(java.lang.String, [B, int, int, java.lang.ClassLoader, java.security.ProtectionDomain)
After some Googling, from http://tomee-openejb.979440.n4.nabble.com/Some-jars-in-TomEE-8-SNAPSHOT-are-not-Java-11-compatible-td4685162.html it seems that the problem originates from jaxb-impl. So I tried adding to pom.xml according to https://winterbe.com/posts/2018/08/29/migrate-maven-projects-to-java-11-jigsaw/ which failed. I restored pom.xml and modified according to Java 11 package javax.xml.bind does not exist which also failed.
This is for tomee server which is less popular. But tomee 7.1.0 is based on tomcat 8.5 which should be much more popular. I think the problem will still be the same.
Advice is appreciated and I think many people should have the same problem.
Try upgrading your tomcat/tomee to the latest version, or downgrading your Java version as incompatible versions tend to fire these NoSuchMethod/NoSuchFile exceptions.
Could be that one technology is reliant on a certain other technology, and is aware of a certain API version, but you are trying to use a higher API version, which could be entirely different.
Another possibility is that tomee is not yet ready to work with java 11 at all (but this seems rather unlikely).
I am working on building a workflow application and I'm planning to use JBPM as my BPM framework. Can anyone suggest me which is the stable version to use in producation environment?
You can try with enterprise release of jBPM which is Red Hat JBoss BPMS. Red Hat will provide hot-fix patches to known issues. Also rollup patches are provided on certain interval, which includes fix for multiple issues. Along with all this you will get 24x7 support for issue.
Just let you know, I have been using jbpm 6.5 with docker in production for 2 months. All work smoothly
My current application is running with JBPM 4 on JBoss 4.0.3 application server. We are planning to upgrade Jboss AS to 7.2 in the near future and we want to know the compatibility of JBPM4 with Jboss 7.2. We are unable to find useful documentation on compatibility between JBPM 4 and Jboss AS 7.2. Please help.
I wud suggest to migrate jBPM 4 also to latest version (6.X) as i have also worked on 4.x and moved back our application to 3.2.X becuase there was no product support aprat from community(https://developer.jboss.org/thread/150947).
Regarding the documentation and compatibility i think it shud work but again you need to test at your end only.
Post results here so it will be helpfull for other also.
We are planning to upgrade our Tomcat from 4.1.31.
Our's is an Axis 1.4 application where we have our web services.
Request you to suggest the latest stable version of Tomcat 5 or Tomcat 6 suitable for our application. And the things to consider while upgrading.
Will the existing 1.4 Java code base works smoothly on Tomcat 5 or 6?
And going further we may write the code in JDK 1.5 as well. So, having Java 1.4 code and Java 1.5 code together, will create any problems?
Kindly suggest.
Please share your upgradation experiences.
Thank You :)
Tomcat 6.0.26 is the latest stable release.
It requires JRE 5.0 or later, so if you are truly stuck on 1.4, you'll need to download the latest 5.5 release, which requires a compatability package to run on 1.4.
My advice: bite the bullet and make the necessary changes for your application to function on 1.6. It is only going to get more and more painful to upgrade (and to continue to code in 1.4) as time goes on.
Go to Java (1.)6; it really makes doing web services like yours easier and it's really widely available now.
If you are going to upgrade I would recommend first doing some tests with java 6 + the existing codebases. If that seems to work, go to Tomcat 6.
Perhaps also upgrade some Axis libraries while you're at it, or leave it as is if it still works.
In my experience you can get to trouble by migrating to Java 5 (and thus 6), especially with XML. My memory has something like a class name clash between Java 5 and an old version of Xerces, but I could be mistaken.
I've got a really nasty problem...
I wrote a Red5 app and so on and it is running perfectly on my local computer.
Now the problem occurs =>
How can I make this program work on a remote server?
Local : Mac OS X 10.5 - Red5 0.63
Server: CentOS 5 - Red5 0.90
Maybe it's because of the version difference. But I can't test Red5 0.90 locally because it won't start up and I can't install the 0.63 version on the server because of missing dependencies (and broken links to them...)
Two thoughts:
Without error messages, code, a description of your application, etc. we can't really help.
Red5 has been in very active development over the years, and each tiny version change is significant. I would suggest figuring out how to get Red5 0.9 running on your local machine would be your first priority.
I solved it...
The XML files have totally changed in the last versions :D and I got a little bug in my program :P
The primary change was in the web.xml, comparing your applications web.xml to one of the 0.9 demos will show you the differences.