Issues karaf-wrapper

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issues karaf-wrapper

Pablo Oswaldo Portillo Alvarado
Hey guys, looking for some help here, for some reason im getting this
problem in our environment every time that the CPU load is about 70%+ the
wrapper just kill the JVM and then is not able to launch a new one, DEBUG
mode is already set up so not sure how to address this problem, any idea
will be more than welcome.

Service mix version: 7.0.1
JDK: Oracle JDK 1.8

ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM did not exit on request,
terminated
DEBUG  | wrapperp | 2019/09/07 22:44:37 | server listening on port 32001.
DEBUG  | wrapper  | 2019/09/07 22:44:37 | Waiting 5 seconds before
launching another JVM.
DEBUG  | wrapper  | 2019/09/07 22:44:37 | Signal trapped.  Details:
DEBUG  | wrapper  | 2019/09/07 22:44:37 |   signal number=17 (SIGCHLD),
source="unknown"
DEBUG  | wrapper  | 2019/09/07 22:44:37 | Received SIGCHLD, checking JVM
process status.
STATUS | wrapper  | 2019/09/07 22:44:37 | JVM exited in response to signal
SIGKILL (9).
DEBUG  | wrapper  | 2019/09/07 22:44:37 | JVM process exited with a code of
1, however the wrapper exit code was already 1.
ERROR  | wrapper  | 2019/09/07 22:44:37 | Unable to start a JVM
STATUS | wrapper  | 2019/09/07 22:44:38 | <-- Wrapper Stopped

Pablo Portillo

Team Lead | IT Information Services - Architecture and Integrations

Ext: 326329 M: +503 79865573

TELUS International Central America | El Salvador

telusinternational.com <https://www.telusinternational.com/>



We give where we live

TELUS Days of Giving 2017: We built a new school at Paraje Concepción.

Click here to watch the video <https://www.youtube.com/watch?v=GqskeuCB-lw>.

--
*Confidentiality Notice: *
This e-mail transmission, and any documents,
files or previous e-mail messages attached to it may contain confidential
information that is legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of any of the information contained in or attached to
this transmission is STRICTLY PROHIBITED.  If you have received this
transmission in error, please immediately notify the sender. Please destroy
the original transmission and its attachments without reading or saving in
any manner.
Reply | Threaded
Open this post in threaded view
|

Re: Issues karaf-wrapper

Jean-Baptiste Onofré
Hi,

do you have something in servicemix.log ?

SMX is using a "old" version of Karaf, so the wrapper. Maybe you can try
a new Karaf version.

Regards
JB

On 09/09/2019 01:16, Pablo Oswaldo Portillo Alvarado wrote:

> Hey guys, looking for some help here, for some reason im getting this
> problem in our environment every time that the CPU load is about 70%+ the
> wrapper just kill the JVM and then is not able to launch a new one, DEBUG
> mode is already set up so not sure how to address this problem, any idea
> will be more than welcome.
>
> Service mix version: 7.0.1
> JDK: Oracle JDK 1.8
>
> ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM appears hung: Timed out
> waiting for signal from JVM.
> ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM did not exit on request,
> terminated
> DEBUG  | wrapperp | 2019/09/07 22:44:37 | server listening on port 32001.
> DEBUG  | wrapper  | 2019/09/07 22:44:37 | Waiting 5 seconds before
> launching another JVM.
> DEBUG  | wrapper  | 2019/09/07 22:44:37 | Signal trapped.  Details:
> DEBUG  | wrapper  | 2019/09/07 22:44:37 |   signal number=17 (SIGCHLD),
> source="unknown"
> DEBUG  | wrapper  | 2019/09/07 22:44:37 | Received SIGCHLD, checking JVM
> process status.
> STATUS | wrapper  | 2019/09/07 22:44:37 | JVM exited in response to signal
> SIGKILL (9).
> DEBUG  | wrapper  | 2019/09/07 22:44:37 | JVM process exited with a code of
> 1, however the wrapper exit code was already 1.
> ERROR  | wrapper  | 2019/09/07 22:44:37 | Unable to start a JVM
> STATUS | wrapper  | 2019/09/07 22:44:38 | <-- Wrapper Stopped
>
> Pablo Portillo
>
> Team Lead | IT Information Services - Architecture and Integrations
>
> Ext: 326329 M: +503 79865573
>
> TELUS International Central America | El Salvador
>
> telusinternational.com <https://www.telusinternational.com/>
>
>
>
> We give where we live
>
> TELUS Days of Giving 2017: We built a new school at Paraje Concepción.
>
> Click here to watch the video <https://www.youtube.com/watch?v=GqskeuCB-lw>.
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Issues karaf-wrapper

Pablo Oswaldo Portillo Alvarado
Hi thanks for you prompt response, unfortunately no, servicemix.log doesn't
have any useful entry, just the CPU load of 75%, after that the wrapper
just kill the jvm.

Thanks for the suggestion do you have more documentation about how to
upgrade the karaf version in SMX? Or I need to replace the SMX for a newer
version of Karaf?

Thanks in advance.

Pablo Portillo

El dom., 8 sep. 2019 9:53 p. m., Jean-Baptiste Onofré <[hidden email]>
escribió:

> Hi,
>
> do you have something in servicemix.log ?
>
> SMX is using a "old" version of Karaf, so the wrapper. Maybe you can try
> a new Karaf version.
>
> Regards
> JB
>
> On 09/09/2019 01:16, Pablo Oswaldo Portillo Alvarado wrote:
> > Hey guys, looking for some help here, for some reason im getting this
> > problem in our environment every time that the CPU load is about 70%+ the
> > wrapper just kill the JVM and then is not able to launch a new one, DEBUG
> > mode is already set up so not sure how to address this problem, any idea
> > will be more than welcome.
> >
> > Service mix version: 7.0.1
> > JDK: Oracle JDK 1.8
> >
> > ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM appears hung: Timed out
> > waiting for signal from JVM.
> > ERROR  | wrapper  | 2019/09/07 22:44:36 | JVM did not exit on request,
> > terminated
> > DEBUG  | wrapperp | 2019/09/07 22:44:37 | server listening on port 32001.
> > DEBUG  | wrapper  | 2019/09/07 22:44:37 | Waiting 5 seconds before
> > launching another JVM.
> > DEBUG  | wrapper  | 2019/09/07 22:44:37 | Signal trapped.  Details:
> > DEBUG  | wrapper  | 2019/09/07 22:44:37 |   signal number=17 (SIGCHLD),
> > source="unknown"
> > DEBUG  | wrapper  | 2019/09/07 22:44:37 | Received SIGCHLD, checking JVM
> > process status.
> > STATUS | wrapper  | 2019/09/07 22:44:37 | JVM exited in response to
> signal
> > SIGKILL (9).
> > DEBUG  | wrapper  | 2019/09/07 22:44:37 | JVM process exited with a code
> of
> > 1, however the wrapper exit code was already 1.
> > ERROR  | wrapper  | 2019/09/07 22:44:37 | Unable to start a JVM
> > STATUS | wrapper  | 2019/09/07 22:44:38 | <-- Wrapper Stopped
> >
> > Pablo Portillo
> >
> > Team Lead | IT Information Services - Architecture and Integrations
> >
> > Ext: 326329 M: +503 79865573
> >
> > TELUS International Central America | El Salvador
> >
> > telusinternational.com <https://www.telusinternational.com/>
> >
> >
> >
> > We give where we live
> >
> > TELUS Days of Giving 2017: We built a new school at Paraje Concepción.
> >
> > Click here to watch the video <
> https://www.youtube.com/watch?v=GqskeuCB-lw>.
> >
>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

--
*Confidentiality Notice: *
This e-mail transmission, and any documents,
files or previous e-mail messages attached to it may contain confidential
information that is legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of any of the information contained in or attached to
this transmission is STRICTLY PROHIBITED.  If you have received this
transmission in error, please immediately notify the sender. Please destroy
the original transmission and its attachments without reading or saving in
any manner.