I have created a Jboss Fuse catridge on openshift. Now, when I go adding apache-cxf feature to container, I receive below error:
Provision Exception:
io.fabric8.agent.utils.MultiException: Error while downloading artifacts
java.util.zip.ZipException: zip file is empty
I have done lot of research online around this, but couldn't find a resolution. Duplicate of another similar issue: Can't download CXF artifacts on JBossFuse running on OpenShift
Related
I am trying to get singe sign-on to work with WildFly-prevew 26.0.1. I found a tutorial WildFly Elytron - Add Kerberos Authentication To Existing Web Application by Darran Lofthouse.
After it did not work I searched for further resources and found How to Set Up SSO for JBoss EAP with Kerberos. There is a JBoss Negotiation Toolkit mentioned. It is said that yout should use the same version of the toolkit as the JBoss Negotiation included in JBoss EAP (EAP_HOME/modules/system/layers/base/org/jboss/security/negotiation/main/module.xml).
Sadly I did not find the folder EAP_HOME/modules/system/layers/base/org/jboss/security/negotiation in the Wildfly 26.0.1-preview. At first I thought that it may be an JBoss EAP feature not included in WildFly. But actually the folder is included in WildFly 24.0.1. Starting with version 25.0.0, the folder is missing. And starting with version 26.0.0.Beta, the whole EAP_HOME/modules/system/layers/base/org/jboss/security folder is missing.
So my question is weather this is a bug or a feature (maybe it migrated to another module). And if it is a bug, may it be a reason my single sign-on is not working?
In a WildFly 25 release post (https://www.wildfly.org/news/2021/10/05/WildFly25-Final-Released/) it is said that
We deprecated the use of legacy security long ago and in the WildFly 25 release we have removed support for it.
Most probably that is the reason these packages are missing.
Application is a EAR file
Shared Library where the third party jar are bundled and deployed to managed server as shared library.
weblogic-application.xml file where library ref to shared library is made and present in EAR file(META-INF folder).
Shared libraries are deployed to managed server as target and is successful.
while deploying the EAR file, the selection of EAR from console deployment results in ClassNotFoundException of the class present in shared library even though the reference is made in weblogic-application.xml.
Note that if the Library deployment is targeted to Admin Server and Managed Server the deployment of EAR file is successful without any exception.
Single Admin Server deployment is working fine without any issues for the same setup.
Deployment is expecting the JAR is classpath of admin server while deploying to managed server. is this an intended behavior ?
Is there any setup configuration we are missing here ? Correct me if there is any steps gone wrong.
Update : we did the same deployment with ant script using wldeploy and no errors are encountered and application is deployed successfully.
This was a known issue in a previous version of weblogic. Maybe it is still not fixed.
CR282367
While using the WebLogic Administration Console with applications or EJBs deployed on a Managed Server that depend on a deployed library, you may encounter a java.lang.NoClassDefFoundError
Workaround:
The WebLogic Server Administration Console needs access to any shared library deployments so that Java data types and annotations can be processed. Therefore, all shared library deployments should always be targeted to the Administration Server in addition to any Managed Servers or clusters.
https://docs.oracle.com/cd/E11035_01/wls100/issues/known_resolved.html
I'm upgrading a web-app that is hosted on 32-bit Weblogic 9.2 into 64-bit Weblogic 10.3.6. For this purpose, I have installed 64-bit Weblogic 10.3.6 on my Windows 7 PC and use OEPE 11.1.1.8 that I separately installed to test local builds and deploys.
Using Eclipse (ver. Indigo), when I publish the app into the local instance of 10.3.6 as a virtual-application, the app works as expected. However, when I change the mode to "exploded archive" I start getting all sorts of errors which, from what I've read so far, are due to Weblogic Classloading.
Example errors:
java.lang.AbstractMethodError:
weblogic.deployment.PersistenceUnitInfoImpl.getSharedCacheMode()Ljavax/persistence/SharedCacheMode
I fixed this by adding
<package-name>javax.*</package-name>
<package-name>javax.*</package-name>
<package-name>javax.*</package-name>
to the weblogic-application.xml file after which I've started seeing the following error which I haven't been able to fix:
java.lang.IllegalArgumentException: interface
javax.persistence.EntityManagerFactory is not visible from class
loader
I've done the following so far:
In Eclipse, searched (using find-type) for the jar(s) that included this class and found a total of 3. Two - "javax.persistence_1.0.0.0_1-0-2.jar" and "javax.persistence_1.1.0.0_2-0.jar" - were under the Weblogic server installation ("%BEA_HOME%\modules") folder and 1 from the application lib path ("WEB-INF\lib\hibernate-jpa-2.0-api-1.0.0.Final.jar").
Given that the javax.* class filter is already in place (above), what else could I do to fix this issue?
If Weblogic doesn't like what I'm doing, why is it allowing the application to work when deployed as a virtual application?
I want to deploy JBoss FUSE as war or in any other way on application server (Tomcat for example). In documentation for the old version (3.5) of FUSE there was described a simple way for doing that by running special maven project from examples folder.
But for later releases I just can't find any information about possibility of doing that. I thought that deploying ESB as a service on application server is standard way of working with it, but I only found tutorials for installing FUSE as standalone instance or system service.
I would like to know how can I deploy it or why I can't do this if thats the case.
This is no longer supported. JBoss Fuse 6.x is a standalone application that has its own container (based on Apache Karaf).
The current 6.x release requires running on top of Apache Karaf.
Though we have plans to make Fuse (that would be Fuse Fabric) container agnostic so you in the
future would be able to run Fuse on JBoss AS, Tomcat, Karaf, Standalone, in the cloud, etc. Though we focus on JBoss AS, Tomcat, and Karaf as the main containers at first we aim to support.
I am using the cargo-maven2-plugin:1.2.0 to do redeployments of my GWT 2.4.0 based web application to Apache Tomcat 7.0.25 1.6.0_30-b12 Sun Microsystems Inc. Windows Server 2008 R2 6.1 amd64).
The initial deployment works fine. I immediately try to undeploy the application using the tomcat manager when I receive the following error message:
org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Unable to delete [C:\apache-tomcat7\webapps\mywebapp]. The continued presence of this file may cause problems.
From tomcat the war file and most of the unzipped web application files have been successfully removed. But it fails to delete two libraries from mywebapp\WEB-INF\lib:
gwt-user-2.4.0
servlet-api-2.3
When I now wait half a minute and trigger the undeploy again, it works.
Did anybody experience the same or a similar behavior?
I already tried to debug using PSI Probe for Tomcat but that didn't really give me any insights. What could I try next?
Both files shouldn't be deployed in the first palce. First gwt-user-2.4.0 is the complete gwt jar file. For deployment only the server specific version needs to be deployed: gwt-servlet-2.4.0.jar. The servlet-api-2.3 is already available in the tomcat lib directory. So you should set both files to provided and if you not yet have the gwt-servlet jar file, add that file to you dependencies.