I tried upgrading to GGTS 3.2 on windows7 64bit and java 7.0.21. running on works pc with a proxy config enabled in internet settings
i create a new project in a new workspace. I then try and run the console for the app.
the console fires up and you can use for ~60 seconds. After that the sts ide throws a timeout error and the console is killed
error in log looks like this :
!ENTRY org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE Problem executing: console
!STACK 1
org.eclipse.core.runtime.CoreException: The command 'C:\Program Files (x86)\Java\jdk1.7.0_21\bin\javaw.exe (18 Jun 2013 22:06:14)' was terminated because it didn't produce new output for some time.
See details for the output produced so far.
If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.
See menu Windows >> Preferences >> Grails >> Launch
at org.grails.ide.eclipse.core.launch.SynchLaunch$LaunchResult.getCoreException(SynchLaunch.java:168)
at org.grails.ide.eclipse.core.launch.SynchLaunch.synchExec(SynchLaunch.java:57)
at org.grails.ide.eclipse.commands.GrailsExecutor.synchExec(GrailsExecutor.java:131)
at org.grails.ide.eclipse.commands.GrailsCommand.synchExec(GrailsCommand.java:169)
at org.grails.ide.eclipse.ui.internal.inplace.GrailsLaunchUtils$1.run(GrailsLaunchUtils.java:120)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Contains: ------System.out:-----------
| Loading Grails 2.2.1
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
Contains: ------System.err:-----------
Terminating process: Timeout: no new output for 60000 milliseconds
!SUBENTRY 1 org.grails.ide.eclipse.core 4 4 2013-06-18 22:08:15.103
!MESSAGE The command 'C:\Program Files (x86)\Java\jdk1.7.0_21\bin\javaw.exe (18 Jun 2013 22:06:14)' was terminated because it didn't produce new output for some time.
See details for the output produced so far.
If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.
See menu Windows >> Preferences >> Grails >> Launch
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE ------System.out:-----------
| Loading Grails 2.2.1
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE ------System.err:-----------
Terminating process: Timeout: no new output for 60000 milliseconds
There was something like this is the sts/ggts forum which claimed it had been fixed in 3.3m2. and might have been to do with pref>groovy>grails>launch - keep running flag - however i enebaled and diabsled this and it made no difference
i tried installing 3.3m2 and tried the same - new workspace - new project. I run the console, 60 seconds later i get a timeout buty the console stays up - error now reads
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
Contains: ------System.err:-----------
!SUBENTRY 1 org.grails.ide.eclipse.core 4 4 2013-06-18 23:27:11.110
!MESSAGE Command terminated with an exception: java.io.IOException: Cannot run program "jps": CreateProcess error=2, The system cannot find the file specified (see details for partial output)
!STACK 0
java.io.IOException: Cannot run program "jps": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.exec(GrailsProcessStackTracer.java:104)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.getGrailsProcessId(GrailsProcessStackTracer.java:72)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.getStackTraces(GrailsProcessStackTracer.java:92)
at org.grails.ide.eclipse.longrunning.client.GrailsClient.executeCommand(GrailsClient.java:381)
at org.grails.ide.eclipse.longrunning.client.GrailsCommandExecution.execute(GrailsCommandExecution.java:85)
at org.grails.ide.eclipse.longrunning.LongRunningProcessGrailsExecutor.synchExec(LongRunningProcessGrailsExecutor.java:82)
at org.grails.ide.eclipse.commands.GrailsCommand.synchExec(GrailsCommand.java:169)
at org.grails.ide.eclipse.ui.internal.inplace.GrailsLaunchUtils$1.run(GrailsLaunchUtils.java:127)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 10 more
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 23:27:11.110
!MESSAGE ------System.out:-----------
Loading Grails 2.2.2
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 23:27:11.110
!MESSAGE ------System.err:-----------
Any one else had this and is there a workaround?
The "Execute Grails Command" function wasn't designed to support persistent processes. It worked previously by chance, but no longer does.
The recommended way to execute long-running grails processes in Eclipse/STS/GGTS is to configure an eclipse run configuration to execute the long-running grails commands. (Run -> Run Configurations...)
Related
Consider a small existing project ffttest https://github.com/javadba/Swift-FFT-Example/tree/upgrade_swift52 . This works :
> Amplitude: 8.0
Frequency: 4.0
Phase: -1.1102230246251565e-15
0 0.0 -8.038073113980855e-15
1 0.7841371226364848 0.7841371226364765
2 1.560722576129026 1.5607225761290189
..
509 -2.3222774180357333 -2.3222774180357075
510 -1.5607225761290364 -1.560722576129034
511 -0.784137122636526 -0.7841371226364928
Program ended with exit code: 0
The program has the following directory structure:
Now I would like to add dependencies and other things traditionally performed in a Package.swift. Is there a tool to build/infer it from this existing project?
I tried to create a Linux image based on "yocto project mega Manuel".But I got an error in building image step.
I followed the mega Manuel.
I'm using Ubuntu 18.04.1 LTS.
Error:
aju#aju-HP-15-Notebook-PC:~/poky/build$ bitbake core-image-sato
WARNING: Host distribution "Ubuntu-18.04" has not been validated with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Parsing recipes: 100% |#########################################| Time: 00:00:49
Parsing of 899 .bb files complete (0 cached, 899 parsed). 1330 targets, 38 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration: BB_VERSION = "1.28.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-18.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "2.0.3" TUNE_FEATURES = "m32 i586"
TARGET_FPU = "" meta meta-yocto
meta-yocto-bsp = "jethro:331275422b2c3f326f605c23ae89eedb4e222eb5"
NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE:
Executing RunQueue Tasks ERROR: oe_runmake failed ERROR: Function
failed: do_compile (log file is located at
/home/aju/poky/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.301)
ERROR: Logfile of failure stored in:
/home/aju/poky/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.301
Log data follows: | DEBUG: Executing shell function do_compile | NOTE:
make -j 4 | : && /bin/mkdir -p doc && {
PATH='/home/aju/poky/build/tmp/work/x86_64-linux/automake-native/1.15-r0/build/t/wrap:'$PATH
&& export PATH; } && /usr/bin/perl
/home/aju/poky/build/tmp/work/x86_64-linux/automake-native/1.15-r0/automake-1.15/doc/help2man
--output=doc/automake-1.15.1 automake-1.15
| help2man: can't get --help' info from automake-1.15
| Try--no-discard-stderr' if option outputs to stderr
| Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
| make: *** [doc/automake-1.15.1] Error 255
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (log file is located at /home/aju/poky/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.301)
ERROR: Task 403 (virtual:native:/home/aju/poky/meta/recipes-devtools/automake/automake_1.15.bb,
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 73 tasks of which 53 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:
Summary: 1 task failed: virtual:native:/home/aju/poky/meta/recipes-devtools/automake/automake_1.15.bb,
do_compile Summary: There was 1 WARNING message shown. Summary: There
were 2 ERROR messages shown, returning a non-zero exit code.
Is it the problem with this latest version or is it something else?
Why are you using such an old release of Yocto? 2.0.x was first released in 2015 and isn't supported on modern distributions. If you need to use 2.0.x then you can pick a patch from a recent release to fix autoconf, but I really do recommend using 2.5 (or 2.6, due to release any day now) instead.
I've had an auto-generated unit test file as follows:
package com.yuanjianlvye.szws
import grails.test.mixin.*
import org.junit.*
/**
* See the API for {#link grails.test.mixin.services.ServiceUnitTestMixin} for usage instructions
*/
#TestFor(ScreenResolutionService)
class ScreenResolutionServiceTests {
void testSomething() {
fail "Implement me"
}
}
If I run the unit test with grails command in GGTS as follows: "test-app com.yuanjianlvye.szws.ScreenResolutionService", I can get the expected answer.
Loading Grails 2.2.1
| Environment set to test.....
| Compiling 1 source files..
| Compiling 1 source files.....
| Running 1 unit test... 1 of 1
| Failure: testSomething(com.yuanjianlvye.szws.ScreenResolutionServiceTests)
| junit.framework.AssertionFailedError: Implement me
at junit.framework.Assert.fail(Assert.java:50)
at com.yuanjianlvye.szws.ScreenResolutionServiceTests.testSomething(ScreenResolutionServiceTests.groovy:15)
| Completed 1 unit test, 1 failed in 207ms
However, if I run the unit test by right clicking the file and select "Run As->JUnit Test" in the popup menu, I got the following error message:
Class not found com.yuanjianlvye.szws.ScreenResolutionServiceTests
java.lang.ClassNotFoundException: com.yuanjianlvye.szws.ScreenResolutionServiceTests
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClass(RemoteTestRunner.java:693)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClasses(RemoteTestRunner.java:429)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Does anybody have any idea about this?
I've experienced this periodically. Stopping any 'grails run-app' commands from running in the background and cleaning the app using the 'Project/Clean...' menu option sometimes helps.
I have installed apache archiva stand alone in my system.But when i try to start it,itshows the error apache archiva failed to start.My codes are given below
D:\apache-archiva-1.3.5>java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin;D:\apache-archiva-1.3.5\bin
D:\apache-archiva-1.3.5>archiva.bat install
wrapper | Apache Archiva installed.
D:\apache-archiva-1.3.5>archiva.bat start
wrapper | Starting the Apache Archiva service...
wrapper | The Apache Archiva service was launched, but failed to start.
Press any key to continue . . .
Instead of using
C:\apache-archiva-2.2.1\bin>archiva start
if you use console it will work.
C:\apache-archiva-2.2.1\bin>archiva console
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.ContextDeployer:ContextDeployer is deprecated. Use ContextProvider
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.WebAppDeployer:WebAppDeployer is deprecated. Use WebAppProvider
jvm 1 | 2016-06-05 01:11:49.147:INFO:oejs.Server:jetty-8.1.14.v20131031
jvm 1 | 2016-06-05 01:11:49.178:INFO:oejs.NCSARequestLog:Opened C:\apache-archiva-2.2.1\logs\request-20160604.log
jvm 1 | 2016-06-05 01:11:49.225:INFO:oejd.ContextDeployer:Deploy C:\apache-archiva-2.2.1\contexts\archiva.xml -> o.e.j.w.WebAppContext{/,null},C:\apache-archiva-2.2.1/apps/archiva
jvm 1 | 2016-06-05 01:11:53.149:INFO:oejpw.PlusConfiguration:No Transaction manager found - if your webapp requires one, please configure one.
jvm 1 | 2016-06-05 01:11:53.453:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
jvm 1 | 2016-06-05 01:11:54.755:INFO:/:Initializing Spring root WebApplicationContext
jvm 1 | Jun 05, 2016 1:12:09 AM org.apache.tomcat.jdbc.pool.ConnectionPool init
jvm 1 | WARNING: maxIdle is larger than maxActive, setting maxIdle to: 20
jvm 1 | 2016-06-05 01:12:25.275:INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080
How do I determine if my Jetty6-service run with administrative rights?
I need to setup Jetty on my XP dev box to run as a service.
http://docs.codehaus.org/display/JETTY/Win32Wrapper
It installs OK and I can see the Jetty6 Service in windows services manager.
But when I try to start it I get this error in the log file:
STATUS | wrapper | 2010/02/26 10:17:10 | Launching a JVM...
INFO | jvm 2 | 2010/02/26 10:17:10 | Error occurred during initialization of VM
INFO | jvm 2 | 2010/02/26 10:17:10 | Too small initial heap for new size specified
ERROR | wrapper | 2010/02/26 10:17:10 | JVM exited while loading the application.
from above link:
Note: The above application (Jetty-Service.exe) must execute with administrator rights otherwise, it fails.
I do have local administrative access to my XP dev box.
And when I run the jetty server as standalone from cmd.exe then it works fine.
(java -jar start.jar etc/jetty.xml)
Does anyone know how to solve this problem / where to look?
/Thanks.