Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: Sprint 4.1.2
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Data
-
HD-Enabler:Kurento
Description
Hello,
I'm using the Kurento image from the lab (kurento-image-R5.0.33
<https://cloud.lab.fi-ware.org/#nova/images/7af4b98a-2528-4114-9614-b8879e033811>
).
After deploy the machine and connection by ssh, i use the command "mvn
compile exec:java" to deploy the example "kurento-hello-world".
The application doesn't deploy and if the user press th "Ctrl" + "c" it
prints an error blocking the shell, as show in the following code:
root@kurento:~/kurento-tutorial-java/kurento-hello-world# mvn compile
exec:java
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Kurento Java Tutorial 1 5.0.3
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] — maven-resources-plugin:2.3:resources (default-resources) @
kurento-hello-world —
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO]
[INFO] — maven-compiler-plugin:2.0.2:compile (default-compile) @
kurento-hello-world —
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] — exec-maven-plugin:1.3.2:java (default-cli) @ kurento-hello-world
—
[WARNING] Warning: killAfter is now deprecated. Do you need it ? Please
comment on MEXEC-6.
. ____ _ __ _ _
/
/ __' __ _ ()_ __ __ _ \ \ \ \
( ( )___ | '_ | '| | ' \/ _` | \ \ \ \
/ __)| |)| | | | | || (_| | ) ) ) )
' |___| .|| ||| |_, | / / / /
=========||==============|_/=////
:: Spring Boot :: (v1.1.4.RELEASE)
19:14:17.628 [App.main()] INFO - o.k.tutorial.helloworld.HelloWorldApp
- Starting HelloWorldApp on kurento.novalocal with PID 1242
(/root/kurento-tutorial-java/kurento-hello-world/target/classes started by
root in /root/kurento-tutorial-java/kurento-hello-world)
19:14:17.632 [App.main()] DEBUG - o.k.tutorial.helloworld.HelloWorldApp - Running with Spring Boot v1.1.4.RELEASE, Spring v4.0.6.RELEASE
19:14:19.709 [App.main()] INFO - o.h.validator.internal.util.Version - HV000001: Hibernate Validator 5.0.3.Final
^C19:14:35.077 [ Thread-1] WARN -
ationConfigEmbeddedWebApplicationContext - Exception thrown from
LifecycleProcessor on context close
java.lang.IllegalStateException: LifecycleProcessor not initialized - call
'refresh' before invoking lifecycle methods via the context:
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@1531dde4:
startup date [Fri Oct 31 19:14:17 CET 2014]; root of context hierarchy
at
org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:359)
~[spring-context-4.0.6.RELEASE.jar:4.0.6.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:888)
~[spring-context-4.0.6.RELEASE.jar:4.0.6.RELEASE]
at
org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.doClose(EmbeddedWebApplicationContext.java:152)
[spring-boot-1.1.4.RELEASE.jar:1.1.4.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext$1.run(AbstractApplicationContext.java:809)
[spring-context-4.0.6.RELEASE.jar:4.0.6.RELEASE]
Regards,
--Hugo Fonseca
htfonseca@onesource.pt
[image: OneSource]
http://onesource.pt
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Hugo Fonseca <htfonseca@onesource.pt>]
Issue Links
- is duplicated by
-
HELP-942 FIWARE.Request.Tech.Data.Stream-oriented.Error_deploying_a_Kurento_example
- Closed
The application is started when you see the following line
[App.main()] INFO - o.k.tutorial.groupcall.GroupCallApp - Started GroupCallApp in 10.624 seconds (JVM running for 30.12)
It takes very little time, but in virtual machines you should add the flag
so that Tomcat may start as usual. You can read more about this here. We've already made a note in our documentation about this, and will be included in the next release of the docs.
About pressing ctrl + c, you are seeing that error because you interrupted the startup process.
Please give it a try with the aforementioned flag, and see if it deploys correctly.