I start wildfly server in eclipse and go to cmd and type:
C:\eclipse-workspace\gg\resteasy-examples\resteasy-examples>mvn clean compile wildfly:redeploy
But this error occurs:
Error executing REDEPLOY:
C:\eclipse-workspace\gg\resteasy-examples\resteasy-examples\target\resteasy-examples.war
(The system cannot find the file specified)
But project have this file in this path /resteasy-examples/target/resteasy-examples-1.0-SNAPSHOT.war.
What am I doing wrong?
I am trying to deploy a gradle web project using tomcat in eclipse and when I am trying to access the application it throws me an exception as follows:
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [36] in the generated java file: [......plugins\org.eclipse.wst.server.core\tmp0\work\Catalina...\org\apache\jsp\error_jsp.java]
The method getJspApplicationContext(ServletContext) is undefined for the type JspFactory
Stacktrace:
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
The same application I am able to deploy manually in the tomcat server with out using eclipse then it is working perfectly.
Please provide me a solution.
While deploying the application into server using eclipse it is adding some dependencies which are conflicted to dependencies added using gradle, after removing the conflicted jars the solved the issue.
the generated war only have the jars which are configured in the gradle so that is working when we deploy it manually on the server.
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"
I am using eclipse kepler IDE. I installed JBoss Tools plugin in my eclipse IDE. When i run an ant target first time got a error console in my eclipse IDE . But it will run successfully if i run the same target on second time. Here follows the message appears on the error console
Errors occurred during the build.
Errors running builder 'Integrated External Tool Builder' on project 'MY_PROJECT'.
Launch configuration type id "org.maven.ide.eclipse.Maven2BuilderConfigurationType" does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
Launch configuration type id "org.maven.ide.eclipse.Maven2BuilderConfigurationType" does not exist.
Possible causes:
Missing specification of a launch type (missing plug-in)
Incorrect launch configuration XML
When I try to debug an Errai app in Eclipse, I get the following error:
[WARN] Failed startup of context org.jboss.errai.cdi.server.gwt.JettyLauncher$WebAppContextWithReload#a9acff{/,/home/matthew/git/PressGangCCMSUI/src/main/webapp}
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
How can I fix this?
I don't know the specific cause, but when the project is cleaned, I can't run it in debug mode in Eclipse. To fix that I run the project with
mvn gwt:run
and once that launcher has come up I can then run the project in debug in Eclipse again.