Do we need any application level changes for move from AWS Java 8 platform to Corretto 8 in Elasticbeanstalk ? Since, they both are OpenJDK application specific changes should not be there correct ?
Correct, Corretto 8 is a drop in replacement for OpenJDK 8. If you run into issues please submit a GitHub issue: https://github.com/corretto/corretto-8/issues and someone from my team will help.
Related
we are planning to migrate our Tomcat from 8.5 to 10/11 version.
at the moment we are using Java 8, we are planning to use Java 17 .
I wanted to know if any one has previously migrated and what were the concerns regarding that.
I am aware that javax needs to be changed to jakarta series.
in our 8.5 tomcat we are using following maven dependencies
spring - 4.3.25.RELEASE
jackson
googleapi
graph
aws amazon jdk
javax servlet
mysql connector 5.1.44
log4j
slf4j
jsoup
unirest
httpcomponents
should we also need to update these dependencies to latest version? to be compatible with latest Tomcat 10
any other issues I need to be aware of ? I will post more on the same thread as I face issues while miggrating, appreciate the feedback and support from you guys. Thanks
Solution/ best way to migrating and also any tools that does it automatically? issues faced be individuals and how they resolved while migrating.
1) We are migrating from Jboss 5 to EAP 7.
2) The same code deploys under jboss 5 but throws below error when deploying under EAP7
Can someone help with how we accomplish
jboss-service.xml equivalent in EAP?
Thanks for your help.
There were many changes in between JBoss 5 and the latest EAP. You'll have to take a look at jboss-service.xml to see what it's trying to accomplish (this is generally just MBean configuration), there will be a new way to do this.
There are lots changes between EAP 5 and EAP 7. JBoss-service .xml is no longer valid. You will have to configure using standalone or domain.xml.
If you need messaging or clustering support then you will have to choose Ha or full or Full-ha profile.
This is a weird problem.
We are using spring boot web application with integrated tomcat.
On my local mac, the app startup quickly.. several seconds.
On google machine with Centos 7, it starts very slowly.. about 2 minutes.
Application is written in JAVA 8
Can anyone help?
This is a community wiki answer, provided by #AndyWilkinson
Are you using Tomcat? It could be a lack of entropy causing it to
block. See Spring Boot Actuator application won't start on Ubuntu VPS for more details.
and #leozin:
Try installing haveged: sudo apt-get install haveged -y
I agree that haveged improves the startup time.
In my case (also Centos 7 but docker containerized), I had to add some -XX:MaxMetaspaceSize and the startup times went down in about 2 minutes.
I have developed Restful Web service using Java EE 7, Netbeans 7.3.1 and MySQL database on GlassFish 4.0 webserver.
Now I am looking to host/deploy it on online server. I have searched for hosting provider for Java EE 7 with MySQL database on GlassFish 4.0 but could not able to find any. The one which I find here is openshift which support Java EE 6 only at the moment.
What are my options? Is there any Hosting provider available to meet above requirements?
I am not sure, if i can use Google app engine or Amazon to host my above web services?
OpenShift are good but expensive because they provide many services which you don't necessarily need (if you do - it's worth it!). You can use Rackspace - they support Java 7. Further, I know you can use Amazon too - but I haven't done it myself - do some Googling to find out how.
Cloudbees.com support java ee7. 5 free apps. Also they have an option to deploy on glass fish 4 through their click start option
I'd like to take advantage of some JDK7 features. What issues might I run into given that I use Apache Tomcat 7.0.x (latest) and Spring 3.1 (latest)?
There were a few compilation gotchas where JDK 6 could infer the generic type properly where JDK 7 could not. This was apparently a bug in JDK 6 as referenced here.
If you are using container-specific resources (e.g., data sources, etc.) be sure to verify these are still operating properly (though this will be immediately obvious on Spring startup if any of these are wired in).
If you are using Spring Security, and you upgrade, you do not need to make any changes per se to get get things running. However, you should take advantage of their less verbose configuration options (especially for REST URL's) that are available in Spring Security 3.1.
Other than that, our upgrade was seamless.
With the last Ubuntu update (11.10) I switched to JDK 7 (OpenJDK 1.7.0_147). I'm using Spring 3.0, Tomcat 6, and JRE 6 on the server (we have both VM and "physical" server installations). The code, compiled with JDK 7 runs on this configuration without any problems. I'm sure, switching to Spring 3.1 won't cause any changes. Not so sure about Tomcat 7, but hopefully this information will be useful to you.
You might run into a problem if you're using Java 7 features in a JSP. Tomcat by default user Java 1.6 for JSP compilation. See http://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html#Production%20Configuration
To solve the problem you'll want to override the compilerSourceVM and compilerSourceVM init parameters in your application's web.xml file. More on that here: https://stackoverflow.com/a/20194823/1029261