I can't run payara 4.1.2.181 with java 7 (Orracle jdk 1.7.0_80).
I have no problem with java 8 and the previous build of Payara (4.1.2.172) runs fine with Java 7. I couldn't find any mention about stopping support for Java 7 in this version.
The error I got is this one (server.log):
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle fish.payara.microprofile.fault-tolerance.microprofile-fault-tolerance [149]: Unable to resolve 149.0: missing requirement [149.0] osgi.wiring.package; (&(osgi.wiring.package=org.eclipse.microprofile.config)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve 223.0: missing requirement [223.0] osgi.ee; (&(osgi.ee=JavaSE)(version=1.8))]
Co you have any idea how to solve it?
Regards
Piotr
Payara stopped supporting JDK7 for public releases in 4.1.2.173, as explained in this blog post. It is still available for paying customers until 2023. So either upgrade to JDK8 or get Payara support.
Related
Android Studio 3.4.
Project SDK (Android API 19 Platform).
Not using FindBugs or SpotBugs.
Every attempt to build, I get this error:
Information:9/05/2019 4:02 PM - Compilation completed with 1 error and 0 warnings in 1 s 763 ms
Error:Internal error: (java.lang.ClassNotFoundException) com.google.wireless.android.sdk.stats.IntellijIndexingStats$Index
java.lang.ClassNotFoundException: com.google.wireless.android.sdk.stats.IntellijIndexingStats$Index
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at com.intellij.util.indexing.counters.IndexCounters.<clinit>(IndexCounters.java:34)
at com.intellij.util.indexing.impl.MapReduceIndex.<init>(MapReduceIndex.java:86)
at org.jetbrains.jps.backwardRefs.index.CompilerReferenceIndex$CompilerMapReduceIndex.<init>(CompilerReferenceIndex.java:214)
at org.jetbrains.jps.backwardRefs.index.CompilerReferenceIndex.<init>(CompilerReferenceIndex.java:73)
at org.jetbrains.jps.backwardRefs.JavaCompilerBackwardReferenceIndex.<init>(JavaCompilerBackwardReferenceIndex.java:12)
at org.jetbrains.jps.backwardRefs.JavaBackwardReferenceIndexWriter.initialize(JavaBackwardReferenceIndexWriter.java:74)
at org.jetbrains.jps.backwardRefs.JavaBackwardReferenceIndexBuilder.buildStarted(JavaBackwardReferenceIndexBuilder.java:40)
at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:358)
at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:178)
at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:138)
at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:302)
at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:135)
at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:229)
at org.jetbrains.jps.service.impl.SharedThreadPoolImpl.lambda$executeOnPooledThread$0(SharedThreadPoolImpl.java:42)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Solved for me, finally, after months. Note that I have never used FindBugs or SpotBugs, although most posts related to this error mention it.
The solution is to change the compiler from javac to Eclipse. I followed the picture here (don't worry if you don't read Chinese; you won't need to; the picture just makes it clear how to change the compiler).
I have no idea why this works and would highly appreciate informed commentary.
I am facing the same issue with android studio 3.4 and 3.4.1 as well but this work fine with android studio 2.3.3 and 3.0 as well.
Bug seems to be in Android Studio 3.4.x so I downloaded beta version of Android Studio 3.5 and error is gone.
You can download preview version from here :
https://developer.android.com/studio/preview/index.html
Partial and temporary fix.
I downgraded Android Studio to 2.3.3 (!) and it worked. I will need to track down what is hard-linking the project to this particular version and fix that, but I need to ship a fix now for the issue at hand.
I get this error message in a Flutter project, when I try to build the project (menu Build/Make Module) whith Android Studio 3.4.2. But I don't get the error when I run the app (menu Run/Run). Running the app does build the project correctly. It seems that menu Build/Make module does not build the app correctly...
So, the solution for me is to run the app, not build it ;-)
Solution
I was able to fix this problem by deleting the system subfolder in Android Studio's configuration folder. No user data is lost and the build starts working again!
Android Studio configuration folder can be found under this locations (for more information see this question):
Linux / MacOSX: /home/USERNAME/.AndroidStudio
Windows: C:/Users/USERNAME/.AndroidStudio
Note that the name of the configuration folder can vary based on the version: it could be .AndroidStudio3.5, .AndroidStudioBeta or others.
Cause
This problem is most probably caused by some corrupted/invalid gradle build files in your project, that cause the system-wide Android Studio configuration to break. So if the problem shows up again after using the solution above, remove cache and build files generated by gradle by following these steps:
./gradlew clean (Linux/MacOS) or .\gradlew.bat clean (Windows): this should work, as it should clean all files generated by gradle.
If you are in a git repository try to remove all untracked files (but please note that this could delete files you want to keep... be sure to commit them first!)
Manually delete build folders, in case the above steps did not work.
Firstly, I installed tomcat 7, then i could deploy adf application acc to following url: https://blogs.oracle.com/adfthoughts/entry/running_adf_essentials_in_tomcat
But i want server to run a j2ee application which has model project with jpa and hibernate etc, so i need to TomEE for that. I installed TomEE 1.5.2 version on my win7 system, i applied the same steps that already done for tomcat 7, result is failure.
Plz help me, I am getting following errors:
Caused by: org.apache.tomee.catalina.TomEERuntimeException: org.apache.openejb.OpenEJBException: Cannot unmarshall the JSP tag library definition file: jar:file:/u02/RTE/apache-tomee-plus-1.5.2/webapps/rcf-dvt-demo/WEB-INF/lib/adf-richclient-impl-12-abrams-SNAPSHOT.jar!/META-INF/afu.tld: unexpected element (uri:"http://java.sun.com/xml/ns/javaee", local:"code"). Expected elements are <{^#}text>
at org.apache.tomee.catalina.TomcatWebAppBuilder.loadApplication(TomcatWebAppBuilder.java:1903)
at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1073)
at org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1033)
at org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:124)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5179)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
I believe the problem is not in ADF, your problem is in the implementation that Tomee is using for EJB (JPA) which is openEJB, see if you configured your EJB Layer correctly?
After upgrading to Solr 4.2.1, deploying the Solr war file to GlassFish version 3.1.1 results in the following error:
2013-04-09 10:45:06,144 [main] ERROR org.apache.solr.servlet.SolrDispatchFilter - Could not start Solr. Check solr/home property and the logs
2013-04-09 10:45:06,224 [main] ERROR org.apache.solr.core.SolrCore - null:org.apache.http.conn.ssl.SSLInitializationException: Failure initializing default system SSL context
at org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:368)
at org.apache.http.conn.ssl.SSLSocketFactory.getSystemSocketFactory(SSLSocketFactory.java:204)
at org.apache.http.impl.conn.SchemeRegistryFactory.createSystemDefault(SchemeRegistryFactory.java:82)
at org.apache.http.impl.client.SystemDefaultHttpClient.createClientConnectionManager(SystemDefaultHttpClient.java:118)
at org.apache.http.impl.client.AbstractHttpClient.getConnectionManager(AbstractHttpClient.java:466)
at org.apache.solr.client.solrj.impl.HttpClientUtil.setMaxConnections(HttpClientUtil.java:179)
Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:772)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55)
at java.security.KeyStore.load(KeyStore.java:1214)
at org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:281)
at org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:366)
... 50 more
Caused by: java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:770)
... 54 more
It seems like people have had this problem when using Solr version 4.2 and the bug fix release 4.2.1 was supposed to fix it (?). Any pointers will be greatly appreciated.
Had the same problems a few days ago. Solved it by downgrading to solr 4.1.0. But there is a solution (found it by googling my personally well known search terms once again ;) Just add two JVM options. Start glassfish with:
asadmin start-domain
and enter:
asadmin create-jvm-options -- -Djavax.net.ssl.keyStorePassword=changeit
asadmin create-jvm-options -- -Djavax.net.ssl.trustStorePassword=changeit
Don't forget to restart glassfish:
asadmin restart-domain
Tried it for myself and works like a charm. Obviously this is working only if you never changed those passwords before.
I try to install SOLR 3.6.0 on a Websphere Portal 7.0. It gives me the following messages in the log:
java.lang.NoSuchMethodError: org/apache/lucene/store/FSDirectory.open(Ljava/io/File;)Lorg/apache/lucene/store/FSDirectory;
at org.apache.solr.core.StandardDirectoryFactory.open(StandardDirectoryFactory.java:33)
After some research I found some lucene which comes with the Portal server.
This is the place, where it's found:
/opt/IBM/WebSphere/PortalServer/prereq/prereq.lucene/shared/app/lucene.jar.
I suspect that this messed up the classloader. I have changed the classloader policy of the application :(
Have anyone experienced the same and did you find a work around?
Thats in advance for your answers
Cheers,
-Fred
I really appreciate the help i've been getting on Stack Overflow, it's helping me become a better programmer.
Im currently learning how to use the Google App Engine, and ive just developed my first app, but im finding it difficult to run. When i run it, it throws the following exceptions:
WARNING: Use on a JRE prior to version 1.6 is deprecated
2011-06-04 12:19:21.190 java[1921:80f] [Java CocoaComponent compatibility mode]: Enabled
2011-06-04 12:19:21.191 java[1921:80f] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Initializing AppEngine server
[WARN] ********************************************************
Warning: Future versions of the Dev App Server will require Java 1.6 or later. Please upgrade your JRE.
********************************************************
Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Successfully processed /Users/josiahuma/Projects/Eclipse/JWorkspace/HelloWorld/war/WEB-INF/appengine-web.xml
Successfully processed /Users/josiahuma/Projects/Eclipse/JWorkspace/HelloWorld/war/WEB-INF/web.xml
Ive tried looking for ways to download and install JRE 1.6 or maybe upgrade it like the error say, but haven't found any on MAC...
Please can anyone help put me through on what exactly i need to do so i can get my first app running. Would really appreciate it.
Upgrade to 10.6. The default JVM is Java 6 there.