Gradle 'android' project refresh failed After Installed Android Studio 2.2.1 - java

Gradle 'android' project refresh failed
Caused by: org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:153)
at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:136)
at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:111)
at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:89)
at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:122)
at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:80)
at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:77)
at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:46)
at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:60)
at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:34)
at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:150)
at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:135)
at org.gradle.tooling.internal.provider.DefaultConnection.run(DefaultConnection.java:202)
at org.gradle.tooling.internal.consumer.connection.CancellableConsumerConnection$CancellableActionRunner.run(CancellableConsumerConnection.java:116)
at org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:64)
at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter$1.run(DefaultBuildActionExecuter.java:59)
at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:79)
at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45)
at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58)
at org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38)
at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
... 3 more
2016-10-20 18:48:29,661 [ 41611] WARN - nal.AbstractExternalSystemTask - Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
com.intellij.openapi.externalSystem.model.ExternalSystemException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
at org.jetbrains.plugins.gradle.service.project.AbstractProjectImportErrorHandler.createUserFriendlyError(AbstractProjectImportErrorHandler.java:106)
at org.jetbrains.plugins.gradle.service.project.BaseProjectImportErrorHandler.getUserFriendlyError(BaseProjectImportErrorHandler.java:158)
at org.jetbrains.plugins.gradle.service.project.BaseGradleProjectResolverExtension.getUserFriendlyError(BaseGradleProjectResolverExtension.java:579)
at org.jetbrains.plugins.gradle.service.project.AbstractProjectResolverExtension.getUserFriendlyError(AbstractProjectResolverExtension.java:158)
at com.android.tools.idea.gradle.project.AndroidGradleProjectResolver.getUserFriendlyError(AndroidGradleProjectResolver.java:405)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$ProjectConnectionDataNodeFunction.fun(GradleProjectResolver.java:772)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$ProjectConnectionDataNodeFunction.fun(GradleProjectResolver.java:752)
at org.jetbrains.plugins.gradle.service.execution.GradleExecutionHelper.execute(GradleExecutionHelper.java:238)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:112)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:73)
at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:41)
at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:37)
at com.intellij.openapi.externalSystem.service.remote.AbstractRemoteExternalSystemService.execute(AbstractRemoteExternalSystemService.java:59)
at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl.resolveProjectInfo(RemoteExternalSystemProjectResolverImpl.java:37)
at com.intellij.openapi.externalSystem.service.remote.wrapper.ExternalSystemProjectResolverWrapper.resolveProjectInfo(ExternalSystemProjectResolverWrapper.java:49)
at com.intellij.openapi.externalSystem.service.internal.ExternalSystemResolveProjectTask.doExecute(ExternalSystemResolveProjectTask.java:51)
at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:138)
at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:124)
at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$3.execute(ExternalSystemUtil.java:419)
at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$4$2.run(ExternalSystemUtil.java:500)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:563)
at com.intellij.openapi.progress.impl.CoreProgressManager$2.run(CoreProgressManager.java:142)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:446)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:392)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:54)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:127)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$1.run(ProgressManagerImpl.java:126)
at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:369)
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)
2016-10-20 18:48:29,664 [ 41614] WARN - radle.project.ProjectSetUpTask -
2016-10-20 18:48:29,664 [ 41614] INFO - radle.project.ProjectSetUpTask - Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Consult IDE log for more details (Help | Show Log)
2016-10-20 18:48:29,664 [ 41614] INFO - ls.idea.gradle.GradleSyncState - Sync with Gradle for project 'android' failed: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Consult IDE log for more details (Help | Show Log)
2016-10-20 18:48:29,733 [ 41683] WARN - roid.tools.ndk.GradleWorkspace - NDK support for project 'android' is disabled because the project doesn't contain any valid native configurations.
2016-10-20 18:48:29,823 [ 41773] INFO - #com.jetbrains.cidr.lang - Clearing symbols finished in 0 s.
2016-10-20 18:48:29,823 [ 41773] INFO - #com.jetbrains.cidr.lang - Loading symbols finished in 0 s.
2016-10-20 18:48:29,823 [ 41773] INFO - #com.jetbrains.cidr.lang - Building symbols finished in 0 s.
2016-10-20 18:48:29,824 [ 41774] INFO - #com.jetbrains.cidr.lang - Saving symbols finished in 0 s.
This issue happens only Cordova/Phonegap projects, works fine on native Android(Java) project.
I checked all questions and answers on StackOverFlow, and tried installing/uninstalling many times, but didn't fix it.
OS: Windows 10 x64, Android Studio 2.2.1.
Does anyone know how to fix this?

Related

Java Jar starts from command line , but not from intellij idea

I am able to start the server with the command line 'java -jar jarname.jar
But , while running main method of the spring boot application , server start fails ,saying that a class from an imported dependency project does not exists
Caused by: java.lang.NoClassDefFoundError: Lcom/jj/db/repositories/KKRepository;
Also there is a warning message in the console :
2021-11-15 11:04:47 WARN WebappClassLoaderBase:173 - - The web application [MM] appears to have started a thread named [RxIoScheduler-1 (Evictor)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
Can anyone please help ?
Instead of a multi-module project, make it as a single module project or specify appropriately in the manifest.

Maven Java Compile

I'm new to Maven and Java but when in search for a good EID reader this looked like the best choice (https://github.com/grakic/jfreesteel/).
I've ran "mvn install" and made the .jar file which when ran resulted in:
The terminal waiting for me to insert the card
When the card is inserted the terminal recognises it and continues .
And finally it crashes
This is the full log of what happens:
[main] INFO net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp - Starting web extensions native messaging background app...
[main] INFO net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp - Using terminal factory type PC/SC
[Thread-0] INFO net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp - Card inserted
[Thread-0] INFO net.devbase.jfreesteel.EidCard - exclusive
[Thread-0] INFO net.devbase.jfreesteel.EidCard - exclusive free
[Thread-0] INFO net.devbase.jfreesteel.EidCard - photo exclusive
[Thread-0] INFO net.devbase.jfreesteel.EidCard - photo exclusive free
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
at net.devbase.jfreesteel.Utils.image2Base64String(Utils.java:220)
at net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp.inserted(EidWebExtensionApp.java:261)
at net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp.access$400(EidWebExtensionApp.java:25)
at net.devbase.jfreesteel.nativemessaging.EidWebExtensionApp$2.run(EidWebExtensionApp.java:155)
at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 5 more

Gradle: java.io.IOException: The pipe is being closed

On my CI machine (Windows 10) I run Gradle tests.
Basically on the machine a git pull and a java compile is performed before the test task.
This task...
test --tests my.package.SomeTestClass
failed with this exception...
00:00:32,989 INFO - Successfully started process 'Gradle Test Executor 1'
00:00:35,925 INFO - Error occurred during initialization of VM
00:00:35,927 INFO - Unable to allocate 16384KB bitmaps for parallel garbage collection for the requested 524288KB heap.
00:00:35,927 ERROR - Error: Could not create the Java Virtual Machine.
00:00:35,929 ERROR - Error: A fatal exception has occurred. Program will exit.
00:00:35,930 INFO -
00:00:35,930 ERROR - Could not write standard input to Gradle Test Executor 1.
00:00:35,932 ERROR - java.io.IOException: The pipe is being closed
00:00:35,932 ERROR - at java.io.FileOutputStream.writeBytes(Native Method)
00:00:35,934 ERROR - at java.io.FileOutputStream.write(FileOutputStream.java:326)
00:00:35,934 ERROR - at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
00:00:35,934 ERROR - at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
00:00:35,934 ERROR - at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:67)
00:00:35,934 ERROR - at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:52)
00:00:35,934 ERROR - at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
00:00:35,934 ERROR - at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
00:00:35,934 ERROR - at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
00:00:35,934 ERROR - at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
00:00:35,934 ERROR - at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
00:00:35,934 ERROR - at java.lang.Thread.run(Thread.java:748)
00:00:35,934 INFO -
00:00:35,935 INFO - > Task :test FAILED
I am using the Gradle wrapper 5.4.1.
My gradle.properties looks like:
org.gradle.daemon=false
org.gradle.jvmargs=-Xmx2g
I experienced the same issue some months back when I enabled the Gradle daemon.
I am monitoring my CI machines and I can see that at this time the machine had about 750MB free memory which is more than the required 512MB (see exception).
Not sure if this is relevant but the node is running the Quickbuild agent.
What does this error exactly mean and how can I get rid of it?

This problem might be caused by incorrect configuration of the daemon

Getting This Type Error Help needed
Complete Error Message:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
-----------------------

"groovy.lang.MissingFieldException: No such field: metaClass for class: java.lang.Class" error in Play Framework

We're running play 1.2.4 (mbknor-3 version) on our ubuntu CI server, Java 7.
Today, for no apparent reason, we started getting these errors on all branches, even those where no code was committed, and a previous build had completed successfully.
The error is happening when I do play start and then curl localhost:9000. I've tried running play clean and play deps --sync, and rebooting the server, and also verified the server didn't run out of harddrive space.
Any idea what could cause this? How to debug it?
2012-06-11 08:47:51,255 INFO (play) ~ Starting /home/ubuntu/programs/teamcity/buildAgent/work/a9561c50f06f33d5/portal/src
2012-06-11 08:47:51,259 INFO (play) ~ Module less is available (/home/ubuntu/programs/teamcity/buildAgent/work/a9561c50f06f33d5/portal/src/modules/less-0.9)
2012-06-11 08:47:51,260 INFO (play) ~ Module secure is available (/home/ubuntu/programs/play/play-1.2.4-mbknor-3/modules/secure)
2012-06-11 08:47:51,261 INFO (play) ~ Module crud is available (/home/ubuntu/programs/play/play-1.2.4-mbknor-3/modules/crud)
2012-06-11 08:47:53,608 DEBUG (com.asual.lesscss.LessEngine) ~ Initializing LESS Engine.
2012-06-11 08:47:53,945 DEBUG (com.asual.lesscss.LessEngine) ~ Using implementation version: Rhino 1.7 release 3 2011 07 19
2012-06-11 08:47:55,396 WARN (play) ~ You're running Play! in DEV mode
2012-06-11 08:47:55,716 INFO (play) ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...
2012-06-11 08:48:04,566 ERROR (play) ~
#6ajlb3agi
Internal Server Error (500) for request GET /
Oops: ExceptionInInitializerError
An unexpected error occured caused by exception ExceptionInInitializerError: null
play.exceptions.UnexpectedException: Unexpected Error
at play.Invoker$Invocation.onException(Invoker.java:244)
at play.Invoker$Invocation.run(Invoker.java:286)
at Invocation.HTTP Request(Play!)
Caused by: java.lang.ExceptionInInitializerError
at play.templates.TemplateLoader.load(TemplateLoader.java:78)
at play.mvc.Router.parse(Router.java:162)
at play.mvc.Router.parse(Router.java:190)
at play.mvc.Router.parse(Router.java:164)
at play.mvc.Router.load(Router.java:48)
at play.mvc.Router.detectChanges(Router.java:219)
... 1 more
Caused by: groovy.lang.MissingFieldException: No such field: metaClass for class: java.lang.Class
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:1074)
at groovy.lang.MetaClassImpl.getStaticProperty(MetaClassImpl.java:1308)
at groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:707)
at org.codehaus.groovy.runtime.Invoker.getProperty(Invoker.java:727)
at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:206)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:295)
at Script1.run(Script1.groovy:1)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:521)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:496)
at play.templates.GroovyTemplate.<clinit>(GroovyTemplate.java:62)
... 7 more
2012-06-11 08:48:04,569 ERROR (play) ~ Error during the 500 response generation
java.lang.NoClassDefFoundError: Could not initialize class play.templates.GroovyTemplate
at play.templates.TemplateLoader.load(TemplateLoader.java:78)
at play.templates.TemplateLoader.load(TemplateLoader.java:172)
at play.server.PlayHandler.serve500(PlayHandler.java:778)
at play.server.PlayHandler$NettyInvocation.run(PlayHandler.java:237)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
This is a weird problem, but I have a resolution.
The problem seems to be caused by a jar collision with the - groovy -> groovy-all-1.0-jsr 05 dependency.
I added this dependency to my project a long time ago, in order to run groovy scripts from my project.
Since then, it seems this dependency is no longer necessary for my project.
In fact, my project's build has been ignoring this dependency for quite some time:
:: problems summary :: :::: WARNINGS
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: groovy#groovy-all-1.0-jsr;05: java.text.ParseException:
inconsistent module descriptor file found in
'http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom':
bad module name: expected='groovy-all-1.0-jsr' found='groovy-all'; bad
revision: expected='05' found='1.0-jsr-05';
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS mavenCentral: bad module name found in
http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom:
expected='groovy-all-1.0-jsr found='groovy-all'
mavenCentral: bad revision found in
http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom:
expected='05 found='1.0-jsr-05'
Yesterday, for some voodoo reason, on our CI machine (and no other machine), this dependency started resolving correctly, fetching this file, and causing class loading issues. This is rather unsettling, as I still don't know what has changed, and I'm a bit concerned this could happen to our production machines.
The resolution was getting rid of this dependency.

Categories

Resources