I have downloaded jboss-eap-7.0.0.Beta.zip and extracted it and I am able to execute the server in both the standalone and domain modes. However, when I try to deploy the Fuse jar fuse-eap-installer-6.2.1.redhat-084.jar on it, I am getting following error.
The error shown on console while executing the jar is:
java -jar ../fuse-eap-installer-6.2.1.redhat-084.jar
Skip already existing patch file: fuse-patch-distro-wildfly-1.6.2.zip
Skip already existing patch file: fuse-eap-distro-6.2.1.redhat-084.zip
Run command: java -Djboss.home=. -Dlogging.configuration=file:bin/fusepatch-logging.properties -jar jboss-modules.jar -mp modules org.wildfly.extras.patch --add file:fusepatch/repository/fuse-patch-distro-wildfly-1.6.2.zip
Repository already contains fuse-patch-distro-wildfly-1.6.2
Run command: java -Djboss.home=. -Dlogging.configuration=file:bin/fusepatch-logging.properties -jar jboss-modules.jar -mp modules org.wildfly.extras.patch --add file:fusepatch/repository/fuse-eap-distro-6.2.1.redhat-084.zip
Repository already contains fuse-eap-distro-6.2.1.redhat-084
Run command: java -Djboss.home=. -Dlogging.configuration=file:bin/fusepatch-logging.properties -jar jboss-modules.jar -mp modules org.wildfly.extras.patch --update fuse-patch-distro-wildfly
Patch fuse-patch-distro-wildfly-1.6.2 has already been applied
Run command: java -Djboss.home=. -Dlogging.configuration=file:bin/fusepatch-logging.properties -jar jboss-modules.jar -mp modules org.wildfly.extras.patch --update fuse-eap-distro
Patch fuse-eap-distro-6.2.1.redhat-084 has already been applied
Run command: java -Djboss.home=. -jar jboss-modules.jar -mp modules org.wildfly.extras.config --configs camel,switchyard --enable
Processing config for: camel
Writing 'layers=fuse' to: ./modules/layers.conf
Enable camel configuration in: ./standalone/configuration/standalone.xml
Error: Did not find the <extensions> element
Error: Command did not terminate normally
The EAP server log shows the following exception:
12:09:19,798 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.module.service."deployment.switchyard-bpel-console.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.switchyard-bpel-console.war".main: WFLYSRV0179: Failed to load module: deployment.switchyard-bpel-console.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.modules.ModuleNotFoundException: org.switchyard.component.bpel:main
at org.jboss.modules.Module.addPaths(Module.java:1042)
at org.jboss.modules.Module.link(Module.java:1398)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1426)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
... 5 more
Please let me know if there are any suggestions on getting this work.
Meanwhile, I checked that the standalone directory for camel configuration, but I don't find any. Please advise.
According official documentation you can't use JBoss Fuse 6.2.1 with JBoss EAP 7. If you want to use JBoss Fuse 6.2.1 you have to install it on top of JBoss EAP 6.4.x.
Please refer this post for answer for this question, I was able to fix this issue by installing Jboss fuse 6.2.1 over Jboss EAP 6.4 as Jboss recommendation.
How to do BPEL,BPM deployment in JBoss AS7/EAP
Related
My webapp running on JBoss EAP 7.4 is having problems locating certain classes. When I run, I see the following in the log:
2022-08-02 14:30:52,387 WARN [org.jboss.modules.define] (default
task-2) Failed to define class
org.apache.phoenix.schema.MetaDataSplitPolicy in Module
"deployment.dbp.rest-1.1.0-SNAPSHOT.war" from Service Module Loader:
java.lang.NoClassDefFoundError: Failed to link
org/apache/phoenix/schema/MetaDataSplitPolicy (Module
"deployment.dbp.rest-1.1.0-SNAPSHOT.war" from Service Module Loader):
Failed to link
org/apache/phoenix/schema/SplitOnLeadingVarCharColumnsPolicy (Module
"deployment.dbp.rest-1.1.0-SNAPSHOT.war" from Service Module Loader):
org/apache/phoenix/compat/hbase/CompatSteppingSplitPolicy
MetaDataSplitPolicy and SplitOnLeadingVarCharColumnsPolicy are present in our war file, but CompatSteppingSplitPolicy is not. The /usr/lib/phoenix/phoenix-hbase-compat-2.4.1-5.1.2.jar file contains CompatSteppingSplitPolicy. Adding external modules directories in JBoss EAP 6/7 tells how the classpath be extended to deployed content reference directories and files external to the installation. I modified my .bashrc accordingly, and the log file now includes:
module.path = /opt/jboss-eap-7.4/modules:/usr/lib/phoenix/phoenix-hbase-compat-2.4.1-5.1.2.jar:/usr/lib/phoenix/*
Unfortunately, I still get the same error. What can I do to fix it?
why not adding the jar in your war ? otherwise you need to add a dependency on that module in your war
I am trying to start up JBoss with parameters in Windows but getting some errors. If I remove parameters than JBoss startup iwht no errors. Could some one please take a look.
environment variables:
JAVA_HOME=C:\Java\jdk1.6.0_45
JBOSS_HOME=C:\bin\jboss-eap-6.1
Path=C:\Java\jdk1.6.0_45\bin;C:\WINDOWS\system32;
start up jboss with following parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
"
Error:
WARNING: failed to load the specified log manager class org.jboss.logmanager.LogManager
Error: Operation <"parallel-extension-add"> failed - address:<[]>
java.lang.RuntimeException: failed initializing module org.jboss.as.logging
==========================================================================
so to fix the error above. I have added logmanager parameter below.
start up jboss using parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
"
ERROR:
Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.logManager
==========================================================================
so to fix error above. I have added -xbootclasspath parameter.
start up jboss using parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager"
-Xbootclasspath:C:\bin\jboss-eap-6.1\modules\system\layers\base\org\jboss\logmanager\main\jboss-logmanager-1.4.0.Final-redhat-1.jar
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
"
ERROR:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
and now I have no idea what to do. I have tried reinstalling jdk but no luck.
when I enter "java -version" in CMD. Than I get result: "1.6.0_45". So I know jdk is set up. but when I start Jboss than jdk is not initialization.
To resolve this, do the following:
Go to the JBOSS_HOME location on the file system e.g. c:\jboss\appserver\jboss-eap-6.3, look in the bin folder and open the configuration file named, standalone.conf, in a text editor.
At the top of the file, add the following line - JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager".
Scroll-down the file, to where JVM options are specified and add the following two options:
JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.2.Final-redhat-1.jar"
Note: You may need to modify the exact path to the logmanager jar file, as the one on your jboss installation may differ from what applies here. The JBoss EAP version being used in this case was 6.3.0GA. A different version may have a different path to the logmanager jar file.
Simply save the modified 'standalone.conf' file, with these couple of changes, and re-attempt starting up of the JBoss App server (either on the CLI or within Eclipse).
Note: For fixing the issue for a JBoss EAP appserver instance running just within Eclipse, simply open the server's launch configuration and add the 2 JVM options to the VM arguments of the launch configuration, as shown in the screenshot below:
Voila! The startup issue with regards to failure to load the LogManager, should be resolved.
Check this blogpost for details and screenshots - http://obinnakalu.blogspot.com/2014/10/jboss-enterprise-application-platform.html
Although this is an old post, but if someone is still facing the issue:
-Xbootclasspath:C:\bin\jboss-eap-......
Above line replaces bootclasspath and now jvm will use only the specified jar to boot.
Use -Xbootclasspath\a:C:\bin\jboss-eap-......
instead. This will append the mentioned jar to existing bootclasspath.
For Jboss 7.1.1 I have solved this issue by adding following lines in standalone.conf.bat. All the jars are taken from JBoss 7.1.1 modules folder
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:E:/jboss-logmanager-1.2.2.GA.jar;E:/jboss-logmanager-log4j-1.0.0.GA.jar;E:/log4j-1.2.16.jar"
guys.
I'm using Rails 3.2.13, jruby-1.7.12, JBoss EAP 6.2 and warbler 1.4.3.dev(have tried 1.4.1 and 1.4.2 - it doesn't matter). And I got such error while entering first page of my application:
19:32:18,822 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (ServerService Thread Pool -- 68) ERROR: initialization failed: org.jruby.rack.RackInitializationException: no such file to load -- /home/alex/Projects/install_test/eap-6.2/jboss-eap-6.2/standalone/tmp/vfs/temp/temp37c8c04246e7d946/content-69d213af89011d97/home/alex/Projects/install_test/eap-6.2/jboss-eap-6.2/standalone/tmp/vfs/temp/temp37c8c04246e7d946/content-95fa3e2c22b1402c/config/environment.rb
I got this error only when there are two different deployments in my JBoss:
Where ap_ROOT.war is my rails application and rp_app.war is my java application. In case when there is only rails application there are no errors.
As I found
/home/alex/Projects/install_test/eap-6.2/jboss-eap-6.2/standalone/tmp/vfs/temp/temp37c8c04246e7d946/content-69d213af89011d97
is the path to the rp_app.war(java application) deployment folder and
/home/alex/Projects/install_test/eap-6.2/jboss-eap-6.2/standalone/tmp/vfs/temp/temp37c8c04246e7d946/content-95fa3e2c22b1402c
is the path to the app_ROOT.war(rails application) deployment folder.
Someway it get messed up and JBoss can't find 'config/environment.rb'.
Thanks,
Alex.
I am trying start jboss and I have an error. I use jboss 7.1.1 and Liferay. What is wrong?
12:25:26,707 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBA
S015877: Stopped deployment ROOT.war in 235420ms
12:25:35,754 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) Exception in thread "com.liferay.portal.kernel.deploy.auto.AutoDeployScann
er" java.lang.NoClassDefFoundError: org/apache/tools/ant/types/resources/FailFas
t
12:25:35,785 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at org.apache.tools.ant.types.resources.BaseResourceCollectionContainer.
iterator(BaseResourceCollectionContainer.java:142)
12:25:35,801 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:135)
12:25:35,801 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at com.liferay.util.ant.ExpandTask.expand(ExpandTask.java:33)
12:25:35,801 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.
java:955)
12:25:35,801 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.
java:889)
12:25:35,801 ERROR [stderr] (com.liferay.portal.kernel.deploy.auto.AutoDeploySca
nner) at com.liferay.portal.tools.deploy.BaseDeployer.autoDeploy(BaseDeployer.
java:198)
Step 1: To setup machine for Liferay development first of all you will need to download and install all required software as described below.
JAVA (JDK & JRE)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Eclipse IDE
http://www.eclipse.org/downloads/
Liferay JBOSS bundle (Community Edition or Enterprise Edition as per your requirements and preferences), Liferay Tomcat bundle (For server run time selection), Liferay Plugin SDK (For Development of plugins like hooks, portlets, themes etc.
http://www.liferay.com/downloads/liferay-portal/available-releases
Apache Ant (For build and deployment of projects).
Step 2: Now set environment variables in your machine.
Set JAVA_HOME
Set JBOSS_HOME
Set LIFERAY_HOME
Set ANT_HOME
Step 3: Open Eclipse and install Liferay IDE.
Go to Help -> Eclipse Marketplace
Search for "Liferay".
Install Liferay IDE and restart eclipse.
Step 4: To configure Liferay Plugin-SDK
Go to Window -> Preferences -> Liferay
Add Liferay Plugin-SDK
Here you will option to update build.<username>.properties file. Select
prompt.
That's it your system is ready with development environment for Liferay.
Step 6: In Liferay Plugin-SDK folder there will be a file called
build.username.properties
Set path of server to refer JBOSS directory.
Step 7:Create new Liferay Plugin Project.
Inside that Create New Portlet Project.
Select Liferay Portal Runtime as Tomcat, because Eclipse doesn't provide
runtime for JBOSS Application server so use some tricky way to deal with it.
After clicking on finish it will ask for updating build.<username>.properties file.
Select "No" option.
Okay Now you are done with project creation and Setting deployment server
as JBOSS.
Step 8: Deploy Liferay Portlet Project.
Step 9: Run standalone.bat from bin directory of JBOSS
For more details follow this blog http://liferaywithjboss.blogspot.in/.
Let me know if you need more details for the same.
Check your jboss-deployment-structure.xml file in ROOT.war/WEB-INF/ location to see any of the dependency modules mentioned in there uses ant-*.jars. The issue could be due to multiple jars with the same classname in the classpath.
new liferay versions provide a wildfly bundle... this could be a starting point, neverthelesse ClassNotFound typically originates from missing jars in that special context, whether physically or suppressed by the jboss modul-system ( starting is here the deployment-structure file, or even worse the module directory of your installation)
but in the end a guy like me decides often to get a new working environment before diving into that voluntarily...
When I try to deploy my application named shopping-1 to Glassfish 3 I get the following error:
'Publishing to GlassFish Server Open Source Edition 3 (Java EE 6)2 at localhost...'has encountered a problen.
cannot Deploy shopping-1
Deployment Error for module: shopping-1: Exception while loading the app :
java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException:
org.apache.catalina.LifecycleException:
java.lang.ClassNotFoundException:
org.springframework.web.servlet.DispatcherServlet
How do I track down and fix this issue?
apparently the shopping-1.war file doesn't include the archive containing the DispatcherServlet class.
unzip -l shopping-1.war | grep spring (on Linux) will give you the list of all spring-related included jar files
First run appserver admin-list applications
Check if there are any deployed applications on the server.
Undeploy by running them if there are.
Stop the application server.
Open the location folder where you have the war file for deployment
Check that there is only one war file at a time in it.
7.Start the application server
Deploy the war.
Should work fine.