You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/02/12 20:44:22 UTC

[GitHub] anik120 opened a new issue #424: JVM issue on Minikube while running Sample.java integration using 0.2.0 release of Kamel binary

anik120 opened a new issue #424: JVM issue on Minikube while running Sample.java integration using 0.2.0 release of Kamel binary
URL: https://github.com/apache/camel-k/issues/424
 
 
   I started by getting a minikube environment up and running by using `minikube start`. I then enabled the registry addon by using `minikube addons enable registry`.
   
   I then installed the operator into a namespace called operators by using `kamel install -n operators` which showed be the output "Camel K installed in namespace operators".
   
   Doing an `kubectl get pods -n operators` shows me that the operator is running :
   ```
   NAME                                           READY     STATUS    RESTARTS   AGE
   camel-k-operator-55445dc59c-6mhgq               1/1     Running       0       1h
   ```
   I then tried to run an integration using `kamel run examples/Sample.java` which was noticed by the operator: 
   
   ```
   $ kubectl logs camel-k-operator-55445dc59c-6mhgq  
   
   time="2019-02-12T02:30:00Z" level=info msg="Inform integrations about context ctx-bhh2va7ltpam33v5096g state change"
   {"level":"info","ts":1549938600.9991944,"logger":"controller_integration","msg":"Reconciling Integration","Request.Namespace":"operators","Request.Name":"sample"}
   time="2019-02-12T02:30:01Z" level=info msg="Apply trait: deployment"
   time="2019-02-12T02:30:01Z" level=info msg="Apply trait: owner"
   time="2019-02-12T02:30:01Z" level=info msg="Integration sample transitioning to state Deploying"
   {"level":"info","ts":1549938601.1018343,"logger":"controller_integration","msg":"Reconciling Integration","Request.Namespace":"operators","Request.Name":"sample"}
   ```
   I could also see that the integration pod was created but with an error: 
   
   ```
   $ kubectl get pods
   NAME                               READY     STATUS        RESTARTS   AGE
   camel-k-operator-55445dc59c-6mhgq   1/1       Running       0          1h
   sample-6c777c5bcd-2q7k5          0/1       CrashLoopBackOff   5          1h
   ```
   When I log the sample pod I see the following error: 
   
   ```
    $ kubectl logs sample-6c777c5bcd-2q7k5
    
   Starting the Java application using /opt/run-java/run-java.sh ...
   exec java -javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=9779:/opt/prometheus/prometheus-config.yml -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError -cp /etc/camel/resources:./resources org.apache.camel.k.jvm.Application
   OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
   Error: Could not find or load main class org.apache.camel.k.jvm.Application
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services