I have a Web application using Apache CXF version 3.2.1 which deploys and works successfully on Weblogic version 12.2.1.3.0.
Because of security vulnerabilities I need to bump the version of CXF library from 3.2.1 to latest (3.2.13 in that moment).
I got the following error when trying to deploy the application with version above 3.2.1(3.2.2, 3.2.3, 3.2.11, 3.2.13 etc..)
<Apr 7, 2020 6:19:54,850 PM EEST> <Error> <HTTP> <BEA-101216> <Servlet: "JAX-RS/Jersey#1" failed to preload on startup in Web application: "webservices.war".
A MultiException has 3 exceptions. They are:
1. java.lang.InstantiationException
2. java.lang.IllegalStateException: Unable to perform operation: create on org.apache.cxf.jaxrs.provider.AbstractResponseViewProvider
3. java.lang.IllegalStateException: Unable to perform operation: create on org.glassfish.jersey.message.internal.MessageBodyFactory
I tried the following approaches:
Adding a shared library as described here:
https://docs.oracle.com/middleware/1213/wls/RESTF/use-jersey20-ri.htm#RESTF296
Modifying the schema location
https://www.oracle.com/webfolder/technetwork/weblogic/weblogic-web-app/index.html
Setting prefer-web-inf-classes to true so all
libraries are taken from the deployed application(not from the
server)
Adding local copy of Jax-RS in my lib folder and trying to use it with prefer-application-packages
Do you have any idea what could cause the problem?
What might be the difference between Apache CXF 3.2.1 and 3.2.2 ?
Why is a minor version change breaking an application?
Related
I am using Alfresco Community v6.0.7.
When I try to query the default path by searching just PATH:"/" in the Node Browser of Alfresco Share, I get No results and 07100085 is displayed at the Name column in the grid below.
Can anyone tell me what could be causing this issue and where do we declare the app:company_home property?
Issue solved. I tried running Solr search services using following command
./solr/bin/solr start -a "-Dcreate.alfresco.defaults=alfresco,archive"
It did not give any error on the console, but when I checked Solr logs it was throwing error.
ERROR (main) [ ] o.a.s.c.SolrCore null:java.lang.UnsupportedClassVersionError: org/alfresco/error/AlfrescoRuntimeException has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
This was because I was running JDK on the machine whereas Alfresco Search Services 1.4 requires JDK 11. After upgrading to JDK 11 both core and archive got created and I was able to run queries again in the Node Browser.
I am configuring IntelliJ to run my Jboss 7.1 remotely, which is on a linux Ubuntu 18.4 in my machine(I'm using WSL).
When I try to deploy my .ear file and set staging option to native IntelliJ throws me this error:
Error: Native deployment method is supported since version 7.1 Jboss
How can I solve this?
You just have remove the JBossServer and put it on again, that will work it out
Initially i was using Tomee 7.0.68 version to deploy and run the web application.
But I now onwards I need to use Apache-tomee-plume-1.7.6 for the same. But after deploy what I found is that, There is No log or work or extracted war files generated once I run the server.
My question is, Is there any difference between apache-tomee-plume-1.7.6 and Tomee 7 to deploy and run/debug the appication?
How can I use Apache-tomee-plume-1.7.6 server?
Thanks.
TomEE 7.x.x is compatible with Java EE7.
TomEE 1.7.x is Java EE6 certified version.
Current TomEE 8.x branch is a work in progress for JavaEE8 compatibility.
As of today, TomEE 8.0.0-M3 is available containing also MicroProfile compatibility.
https://tomee.apache.org/download-ng.html
When I am starting the JBoss server with kie workench 6.4 war file, I am getting the following error
Caused by: org.eclipse.jgit.dircache.InvalidPathException: Invalid path: social-files/<system>
Ok, since your system is Windows and you are using Wildfly this might be caused by a CDI bug that the combination introduces. I recommend you either change the operating system or try another container for the war.
I have recently upgraded our unboundid ldap jar version from 1.1.3 to 3.1.1. After the upgrade when I am deploying the app in weblogic, I am getting a ClassNotFoundException in the log. So far I have faced no issues in terms of functionality, but I am concerned is there any connection leakage is happeining underneath or not.
Caused by: java.lang.ClassNotFoundException: com.unboundid.ldap.sdk.DisconnectType
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
... 1 more
App package : WAR
Server : Weblogic 10.3.6
I experienced a similar issue, using unboundid ldap 2.2.0 and Tomcat 7, with reference to ProtocolMessages instead of DisconnectType:
java.lang.NoClassDefFoundError: com/unboundid/ldap/protocol/ProtocolMessages
The class was definitely present in the jar files. In my case, this error was a smokescreen. On initialization, the application experienced an error and failed to load; however, some ldap connection threads had already connected and did not get shut down properly. The orphaned threads continued to throw NoClassDefFoundError until I restarted the application server.