We are migrating from WebSphere 8.0 to WildFly 10.0.0. after compiling the project in eclipse and removing all the reference of IBM WebSphere jars, on deploying the application, I am getting an error that NoClassDefFoundError: com/ibm/wsspi/uow/UOWException
I have tried to search this exception class in my project, i did not find any.
Can you please help me in fixing this error.
Along with the migration , we are also upgrading Java version to 8 and Spring version to 4.3.0
While working on this, I figured that we were referring to WebSphereUowTransactionManager which is specific for WebSphere in the Springs Transaction Manager. We have to replace it with JtaTransactionManager for removing the exception.
Related
I have created custom connector project using below command, "mvn org.mule.extensions:mule-extensions-archetype-maven-plugin:generate" in Mule 4. But when i open this project in anypoint studio 7.1.2 it gives below error ('The import org.mule.runtime cannot be resolved') in all of defaultly created java.class files. I have updated the pom file dependencies also, but still issue persists.
Help me to resolve this error, thanks in advance
Thanks,
Videesh.
Studio 7 (including the at this time last release 7.2.2) doesn't support Mule SDK projects. You can use any other IDE that supports generic Maven projects.
I get the below error while deploying my Spring Batch application (war) from IntelliJ IDEA 14.1 (Ultimate edition) into Tomcat server 6.0.26.
However, if I take the same war file and deploy it manually in Tomcat webapps, then I don't see any error. Has anyone faced this issue?
java.lang.IllegalStateException:
org.springframework.batch.core.configuration.DuplicateJobException: A
job configuration with this name [deferJob] was already registered
I finally found the issue. For some reason, IntelliJ IDEA was picking up duplicate spring batch xml files from /src/test/resources. I have raised this issue with IntelliJ support team.
While deploying simple hello world application on Mule, i am getting following error. Any way to resolve the same?
Reading plugins from: D:/MULE/MuleStudio/plugins/org.mule.tooling.server.3.5.0_3.5.0.201405141856/mule/plugins
Exception in thread "main" java.lang.NullPointerException
Version: Mule Studio 3.5,
Java: JDK 1.6
Flow include a HTTP adapter|Request-Response and logger only.
I am able to resolve this issue.
Actually, I was creating project with Mule Cloud Runtime; but I need to create it with Mule Server 3.4.1 EE. After creating project correctly, i am able to deploy it successfully.
JPA 2.0 "seems" to be finally working in my application deployed on Weblogic 10.3.5 (after tweaks described below).
However, I still get the following message on the WL console terminal:
This version of OpenJPA cannot read a persistence.xml document with a version different from "1.0". Found: version "2.0" in
This is appearing more than once in the logs and I am looking at some way to get rid of it. Read somewhere that this happens with WL 11g release but is there a way to hide/do away or fix it?
Environment:
Weblogic 10.3.5
Toplink configured as default persistence provider in console
WL classpath modified to have jpa2 specific jars in WL in front of the path (as described in Toplink with Weblogic 10.3)
Removed Toplink jars from application.
We've used the Oracle patch to configure JPA2 on WLS 10.3.5
http://docs.oracle.com/cd/E24329_01/web.1211/e24972/using_toplink.htm#CIHIBGBG
Looks as if Kodo is using openJPA. You might consider configuring Toplink in your console.
Update to Worklight version 6.0. Even load sample apps from new version 6.0 web site and get this exception like this:
An internal error occurred during: "Upgrade Worklight Projects".
loader constraint violation: when resolving method
"org.apache.commons.io.FileUtils.iterateFiles(Ljava/io/File;Lorg/apache/commons/io/filefilter/IOFileFilter;Lorg/apache/commons/io/filefilter/IOFileFilter;)Ljava/util/Iterator;"
the class loader (instance of
org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the
current class, com/worklight/builder/skins/impl/SkinBuilderImpl, and
the class loader (instance of
org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved
class, org/apache/commons/io/FileUtils, have different Class objects
for the type org/apache/commons/io/filefilter/IOFileFilter used in the
signature
None of the apps could be built and deployed in new 6.0 (Tried With JDK 1.6/1.7, Eclipse 4.2.2).
Please try to find if you have apache commons IO installed in your Eclipse plugin directory.
That's the source of the conflict.
If you can, please try to:
1. stop the Eclipse
2. move the apache commons IO out of the plugin dir
3. start Eclipse, then close it.
4. move the commons IO back into the plugin dir.
5. Start Eclipse.
Does the problem occur?
Have to use Eclipse is 4.2.2 Java Platform Enterprise Edition version but not Classic