Is Glassfish 4.1 supported in AIX 6.1.0.0? - java

I'm using GlassFish 3.1.2.2 on a AIX machine and it is working fine. The company's security policy requires me to upgrade it to the latest version, but everytime I try to deploy my application (the same that is working fine in version 3.1.2.2) I get the error Type javax.rcm.ResourceAttributes not present and a nasty stack trace afterwards.
I read the server's specification and it is not clear if it will run on AIX or not. Previous releases had a separate distribution specific for AIX, but that is not the case now.
Does anyone know if it just not compatible or if it is some sort of bug in the JDK implementation?
Kind regards,
Carlos Ferreira

GlassFish 4.x and higher is not "supported" on anything. The reason is that Oracle have withdrawn commercial support, so GlassFish is only available as an open source edition.
If you do need commercial support, the Payara project exists to provide commercial support and custom builds of GlassFish.
Coincidentally, there is a recently opened issue on their Github relating to known issues with GlassFish on the IBM JDK, so it is probably worth commenting on that issue (or creating a new one) with your errors and stack traces.

Payara Blue is the version of Payara that should run on IBM AIX on the IBM JDK. Get Payara Blue from the Payara WebSite Payara is derived from GlassFish 4.x Open Source Edition.

Related

Applet based application stopped working after upgrading to Java

We recently upgraded the JDK on our Java application server from JRockit to Java 7. While most of the applications worked as expected, users for one of the applications reported issues. We ended up upgrading the JDK on the client nodes to get it to work. While it works for most users, some users are still complaining about intermittent pop up complaining about security warnings.
Obviously applets are quite old and should the application should be replaced. But I am not part of the software team and looking for any suggestions to deal with this issue.

What is wrong with my attempt to create a Glassfish server available at Eclipse?

I am trying to integrate Glassfish server support to an already existing eclipse java (maven) project. IMore precisely, I am looking into JMS and queues. I have completed a tutorial wih NetBeans, due to lack of success in Eclipse, but as my skills and familiarity with Eclipse are a lot better, I would really like to make it work there too.
I've tried a lot of different, but similar tutorials, and here is what happens in all of them:
1. Download Glassfish Tools for eclipse. As far as I can tell, this is done:
2. Create new server, if not existing. No servers available. No Glassfish option available.
3. Try Downloading additional server adapters. Still no glassfish options...
None of the tutorials available seems to deal with this scenario. And they are all dependent on completing these steps. I am in the dark here. Any idea of what my problem might be? I am behind company firewall. There might be proxy-settings involved in this issue, but I have not been able to find the right concepts to explore if that is the case.
If it still doesn't work for you (2014.10.07) use the following link to install GlassFish 7.2 (with Eclipse's Install New Software mechanism):
http://download.oracle.com/otn_software/oepe/12.1.3.1/luna/repository
The one from the marketplace is 7.3, and it is broken for now.
Courtesy of Jan Kowalski
A new version of GlassFish Tools (7.3.0.201409251743) was released recently, which seems to be broken. There is this bug report, and I myself experienced buggy behavior after upgrading my installed version, too, like not being able to start the server anymore.
This is very annoying because apparently one can't revert to the previous version anymore either:
No repository found containing: org.eclipse.update.feature,oracle.eclipse.tools.glassfish,7.2.1.201407111426
Got the same problem at first when using the GlassFish Tools or the OEPE downloads (both deliver the same version) via Eclipse Marketplace. The installation runs smoothly, but no GlassFish option when adding a new server.
I'm running Kepler SR2 and Java 6 update 45.
Then, when browsing the Oracle site for OEPE, I found that the latest few versions are for Java 7/8. Via the archive page for OEPE http://www.oracle.com/technetwork/developer-tools/eclipse/downloads/oepe-archive-1716547.html
I downloaded version 12.1.2.3 which is the last one for Kepler and Java 6.
With this version, the GlassFish option in the New Server dialog finally turned up.
Took me a few hours to find out. It's a bit disappointing that there were no error messages in neither the Eclipse UI nor in de Eclipse log.
(No comments on me using an old JDK please :-) I'll upgrade in the near future.

JRE 8 compatibility with weblogic 10.3.6 (11g

Could you please help in finding out if JRE 8 would be compatible with weblogic 10.3?
We have a swing based application deployed on weblogic 10.3 server. We want to upgrade our JRE so wanted to check if JRE 8 would be able to run apps deployed on weblogic 10.3
Java 8 is supported on WebLogic Server 12.1.3. It is not supported on 10.3.6, 12.1.1, or 12.1.2.
See https://blogs.oracle.com/WebLogicServer/entry/weblogic_server_12_1_3
Java 8 is not yet supported in Weblogic server (till Weblogic 12.1.2).
It would be supported in future release.
https://community.oracle.com/thread/3539686
Bit old topic, but just came across this issue myself and have a bit more to add to it. As with the existing answers, it can't be used to install directly- the oracle installer will complain.
However, it is possible to install using an earlier JDK (6 or 7 are supported in 10.3.6), and then swap to JDK8 under the covers. I expect you could also use a custom install to bypass the installer entirely.
This obviously isn't supported - but it does run. If you try to use certain JDK8 features though, they tend not to work (such as newer jdbc drivers - 4.2 simply won't run), so there isn't much benefit to this in normal use cases.
As per the latest update Weblogic 12C is compatible with JDK 8.
https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/notes/whatsnew.html#GUID-960100E8-DFC1-49E5-8CED-1EC1D883A42F

How risky if I develop on Weblogic 10.x and deploy to Weblogic9.2.x?

Recently I took over a relative old project, which is running on weblogic 9.2. I need work on some change requests. I don't know much about weblogic product.
The old DEV-Env is windows based, however I dont have a windows machine. I tried to download Weblogic9.2 for linux (32bits), however I cannot find the link on Oracle website, after quite a lot google, still no working link found.
So the options for me:
find out a working link, download weblogic9.2 and work with it
download and use the 10.x version from oracle
setup a windows box (we have the installer of weblogic9.2 for win)
the 3 is the last thing I want to do. If someone knows where can I get the 9.2 version, it would be great. If there is no weblogic9.2 available, can I work on weblogic10.x and release to 9.2 in production? how risky is it?
Developing in WLS 10.x and deploying in 9.2 may cause some trouble.
There are quite a no of features which have been upgraded in 10.x, such as Java 5 to 6, J2EE 1.4 to 5, Servlet 2.4 to 2.5, JSP 2.0 to 2.1, EJB 2.1 to 3.0.
While most of the features here do have backward compatibility, you have to be extra careful when you develop.
I would suggest to develop based on the lowest common denominator features only, and build on the same server you are deploying it to. (i.e. 10.x has a diff build, and 9.2.x has different one.)
EDIT: There seems to be a authentic binary available on PeopleSoft's FTP site.
It's definitely a risk. Different versions of Weblogic use different jars, so what works on 10.x may not work on 9.x. It's a good practice to have your QA and PROD environments as similar as possible including node setup and startup variables.
If your current PROD deployed code works on 10.x then I would upgrade your PROD environment to 10.x and continue your development on 10.x. If not then do what you can to have 9.x on your DEV environment as well.

Patching a single class in Glassfish

We're experiencing a bug in Glassfish 3.1.2.2 (specifically, in the WSEndpointImpl class in Metro module) which is fixed but due in Glassfish 4.0 or some next release in the 3.1 branch hopefully. As this fix is critical for our application, we would like to patch this class alone and install it somehow to Glassfish, before waiting for the next release. Is this possible? What do you recommend?
Glassfish supports swapping in other versions of certain modules via the Endorsed Standards Override Mechanism and according to the Oracle documentation JAX-WS is among the replaceable components.
You just have to copy the updated version into the /lib/endorsed directory of your domain, but I'm pretty sure you can also put your file in the /lib/endorsed directory of the Glassfish server itself.
See a practical example in this blog entry

Categories