We're using Jdev 12.2.1.4, while starting the integrated wls instance it's throwing below error-
Caused by: java.io.FileNotFoundException: Unable to locate file distributions\JDeveloper_Integrated_Server_Suite_12.2.1.4.0.xml under lookup locations.
JDK version- jdk 1.8.162
You should update your Oracle-Jdk.I dont think 12.2.1.4 version not supported by Jdk 1.6. Read this documentation:
https://www.oracle.com/application-development/technologies/jdeveloper/1212-cert.html
There was some JAVA_HOME related issues in .globalEnv.properties file. Additionally some permission issues were there in JDeveloper_Integrated_Server_Suite_12.2.1.4.0.xml file. Pointing to correct java_home and giving my permission to this xml file has resolved the issue for me.
Related
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 created a new app using command play new hello and cd'ed into the directory. When I type play in the directory, I receive the following error:
akshay#Akshay:~/play/testn$ play -help
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Getting org.scala-sbt sbt 0.13.0 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
0 artifacts copied, 43 already retrieved (0kB/45ms)
Error: Could not retrieve sbt 0.13.0: missing sbt.xMain
Play was working fine in my old Ubuntu box. Today only I got a fresh copy of Ubuntu 12.04 32 bit. I know it is error due to change in version, but certainly, I am not able to solve this. Please help me on this.
In checked .sbt/boot/update.log and I can see this :
trying http://repo.typesafe.com/typesafe/ivy-releases/org.sonatype.oss/oss-parent/7/jars/oss-parent.jar
tried http://repo.typesafe.com/typesafe/ivy-releases/org.sonatype.oss/oss-parent/7/jars/oss-parent.jar
HTTP response status: 404 url=http://repo.typesafe.com/typesafe/ivy-releases/org.sonatype.oss/oss-parent/7/jars/oss-parent.jar
CLIENT ERROR: Not Found url=http://repo.typesafe.com/typesafe/ivy-releases/org.sonatype.oss/oss-parent/7/jars/oss-parent.jar
typesafe-ivy-releases: resource not reachable for org.sonatype.oss#oss-parent;7: res=http://repo.typesafe.com/typesafe/ivy-releases/org.$
trying http://repo1.maven.org/maven2/org/sonatype/oss/oss-parent/
Though error was coming from a fresh ubuntu installation with oracle jdk 8, I tried completely removing jdk and then installing jdk 7, but still no solution. Since it was a fresh installation, I reinstalled ubuntu and installed jdk 7 and problem is solved. Not sure why is it contradictory to Play's recomendation of using Jdk 6 or above. Notifying Play Google Groups about this.
I was getting the same error while trying to build using sbt-launcher.jar which was invoked through jenkins. In my case there were two Scala versions within ~/.sbt/boot/ and removing the older version solved the issue.
I was trying to setup my development environment for one of our projects when I hit this issue. The problem was the sbt.version parameter in the build.properties file of our project which specifically mentioned the version of sbt as 0.13.8 and I had sbt 0.13.11.
After removing sbt 0.13.11 and installing 0.13.8, the issue got resolved. Or if it is possible for you to change the sbt version in your build.properties file, you can do that as well.
I am using JBOSS EAP 6.1 using JDK 1.6. I have registered all my dependencies as static module. I have dependencies on JDK apis.
During deployment I am faced with following issue:
java.lang.NoClassDefFoundError: javax/crypto/CipherInputStream
java.lang.NoClassDefFoundError: org/omg/CORBA/portable/IDLEntity
java.lang.NoClassDefFoundError: javax/swing/ImageIcon
I was able to resolve the above issue by creating a static module and adding rt.jar and des.jar as resources in moudle.xml but then I am facing another issue regarding algorithm not found.
java.security.NoSuchAlgorithmException: PBEWithMD5AndDES SecretKeyFactory not available
at javax.crypto.SecretKeyFactory.(DashoA13*..)
at javax.crypto.SecretKeyFactory.getInstance(DashoA13*..)
at utilities.algorithm.DesEncrypter.(DesEncrypter.java:49)
at utilities.algorithm.DesEncrypter.decryptStream(DesEncrypter.java:177)
I want to add include these dependencies from system without creating static module as shown on different forums.
https://community.jboss.org/thread/195182
https://community.jboss.org/message/717881#717881#717881
Can we do it in for EAP 6.1 or its just available for JBOSS AS 7. Can someone please show me an example for EAP 6.1.
I have been able to fix the issue. The api included in JDK are exported in different modules and we need to include those modules in our modules as dependences.
For Example: org/omg/CORBA/portable/IDLEntity was available in org.omg.api module.
Similarly, javax/swing/ImageIcon & javax/crypto/CipherInputStream was available in javax.api.
I don't know what problem with my JasperReports report, when I try to add new datasource in iReport, I got this error
Unsupported major.minor version 51.0
(unable to load class com.foundation.service.datasource.JsDataSourceService).
I followed all the answer on StackOverflow, and I changed the complicance level to 1.7, jre also is set to jre7 too, I already check the environment variable
JAVA_HOME: C:\Program Files\Java\jdk1.7.0_25,
but still got this error. Please help me to fix that!
This happened to me also - I had recently installed JDK 7, which is what that incompatible class version is. The root cause for me was that I was compiling my jasper reports using the maven plugin, which does not have a way to set -target 1.6. So, my solution was to run maven from a shell in which I'd made the following change:
export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home
do mvn --version to confirm you now get a 1.6 Javac instead of the 1.7. That's a more brute force way of setting the target class format.
I'm on OS X 10.8 - if you aren't, you may have to change that slightly, but hopefully the idea helps.
Your environment variable is already correct/set to jdk1.7.0_25.
I bet the issue is with your IDE.
If you're using Eclipse, go to Configure Build Path
Edit existing JRE System Library (previously set to jdk1.6)
Choose Alternate JRE
Browse to Installed JREs... (normally in C:/Program Files/Java..)
Click Finish
I installed scala 2.8.0 last night and I seem to be having some issues getting it running. If I type scala at the command prompt it comes up with the following:
> scala
Exception in thread "main" java.lang.NoSuchMethodError: scala.collection.mutable.ListBuffer.toList()Lscala/collection/immutable/List;
at scala.collection.TraversableOnce$class.toList(TraversableOnce.scala:399)
at scala.collection.mutable.ArrayOps.toList(ArrayOps.scala:34)
at scala.tools.nsc.MainGenericRunner$.main(MainGenericRunner.scala:33)
at scala.tools.nsc.MainGenericRunner.main(MainGenericRunner.scala)
Anyone have any ideas? I'm on Windows 7 professional, with Oracle JRE 1.6.0_21
Did you set the SCALA_HOME environment variable to point to the correct directory?
Did you have an older version installed? If that's still on your path then it may be causing problems...
EDIT
Can you paste the contents of your PATH and CLASSPATH environment variables? Perhaps using pastie or pastebin if they're on the large side.
You should also update to Java 1.6.0_22 if at all possible, due to this bug which was present in update 21: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6969236
Turns out this problem occurred because I put the sbt-launch.jar in the lib directory for my scala installation. Once I moved it into another directory scala worked fine.