In my web application I am using apache logging log4j. When I was working jboss as 7.0, logging was working well.
But when i switched to Jboss 7.1 logging is not working. Can somebody let me know what has been changed?
By default in 7.1 logging dependencies are added to each deployment. This works for most people, but if you're using your own log4j configuration this will not work for you in 7.1.1 and lower. You need to exclude the servers log4j dependency.
Note: In 7.2.x this will just work and you can remove the jboss-deployment-structure.xml and the dependency.
Related
For the newest version of PDI 9.3, it still uses jetty 9.4.18. There are several security issue of jetty and no workaround for some of them, such as CVE-2022-2047, CVE-2022-2048. And if replaces jetty*.jar to newer version such as 9.4.48, PDI will work not properly.
So how to resolve the security issue of jetty in PDI(kettle)?
Thank you.
what would be the compatible weblogic versions for the log-2.17.1. any Reference link is useful.
part of my research nowhere i found related solutions in the official sites
It would be more the java version that weblogic runs on. If it supports java 8 then you would be able to use log4j 2.17.1. I think weblogic 12.1.3 onwards supports java 8.
Recently we upgraded to elastic 5.0. The java client in Elastic 5.0 has a hard dependency on log4j 2.6. Storm server (version 1.0.2) on the other hand uses an older version log4J and both are hard wired dependency. The following is the error we get when trying to deploy to the server and i can see that 'PreBuiltTransportClient' is not able to instantiate.
java.lang.NoSuchMethodError: org.apache.logging.log4j.Logger.info(Ljava/lang/String;Ljava/lang/Object;)V
I have raised the issue with Elastic and they have acknowledged the issue and mentioned that they are working on a true client that has lesser dependencies.
Any workarounds or suggestions to get around this for the timebeing?
I found a solution for this and it is working now. Here is what i did,
Storm loads the log4j files using a python script from a specified folder under /lib. The latest version of storm uses log4j 2.1
I copied the log4j 2.6.2 files in to that folder.
Now when I deployed my toplogy, storm started using the log4j2.6.2 in the CLASSPATH.
Elastic client got what it needed and it started working.
Until the light weight Elastic Client is released we will continue to use this workaround.
Can someone please help me out with the Oracle ADF faces application which I'm trying to deploy on Websphere 7.0? Do I need to apply any fixpacks on WAS? I'm trying to migrate this project from Websphere 6.1 to Websphere 7.0.
In Websphere 6.1, after removing jsf implementation jar files and providing them as part of WEB-INF\lib and changing the classloader to PARENT_LAST, the application was working fine.
For websphere 7.0, I can't seem to get the application working. It always picks up the Sun's JSF implementation. I've also tried the shared library concept but to no success.
Regards,
Zahir
The Oracle documentation lists a certification for WAS 7.0.0.13 ND. So you need FixPack 13 or later.
As the WebSphere Application Server 7 is a full blown JEE5 server it requires/has JSF 1.2 support. You can switch between the built in Sun and MyFaces implementation if required.
You should probably make sure that the ADF version you are using is certified for WAS 7. The ADF release notes tell that ADF supports JSF 2.0. The WAS 7 only comes with JSF 1.2. Exchanging the JSF version with placing the JSF 2 libs into WEB-INF/lib works well for our projects in conjunction with the 'PARENT_LAST' classloading policy. Make sure that you set the policy either for the whole application or for both the application and the web module.
ADF Faces is a Java based framework and it will run on WebSphere but, you have to add the required libraries first. The easiest way to prepare WebSphere to run ADF Faces application is through JDeveloper. Alternatively, you can google Oracle JRF (Java Runtime Framework) and install that on your WebSphere, before running the ADF Faces application.
I have a (old) web app that is using Jrun and IIS. I would like to replace JRun with something free and OS. Can you recommend something that I can just install and copy the app jar files over and be up and running?
If you don't need a full J2EE (damn, that must be old software), Connecting IIS with Tomcat using isapi_redirect describes how to front Apache Tomcat with IIS (covers version 7).
If you are running EJBs, I would consider using the (appropriate) version of JBoss and follow the same procedure as above to front JBoss with IIS.
I use Jetty. Very easy to use. Not sure if you have EJBs - the version of Jetty I use is just Servlets and JSP.
I've also used Tomcat and JBoss. They work too.
WebsphereCE from IBM is also open source. It is a scaled down version of the paid version. Some people reported success using it with IIS but you might want to use either Tomcat or Jetty if all you have are servlets and JSPs.