You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by spgv <si...@nsn.com> on 2008/04/02 11:00:39 UTC
Degraded performance and Exceptions using Servicemix CXF components
Hi,
I have use case where in a client like soapUI pumps SOAP msgs to a cxf bc
which is then redirected to a cxf se, in the cxf se , the attachement (of
size 50kb) from the SOAP msg is extracted and sent to a service mix file
bc which ouputs it a directory.
While performing load tests for the above use case where the client (SOAPUI)
is running on windows and servicemix instance on linux, there are exceptions
thrown and only a few hundred msgs are dumped.
What happens is that while the msgs are being processed, components are
deactivated one by one and
thereafter a flood of exceptions occur.
I am using a listener to see the msgs going between the components.
09:01:29,800 | INFO | ServiceMix ShutdownHook | JBIContainer |
mix.jbi.container.JBIContainer 940 | Deactivating component
#SubscriptionManager#
09:01:29,800 | INFO | ServiceMix ShutdownHook | JBIContainer |
mix.jbi.container.JBIContainer 940 | Deactivating component
#SubscriptionManager#
09:01:29,396 | INFO | btpool0-1 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:578|1206934286645|1206934289396|2751
09:01:29,396 | INFO | btpool0-116 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:577|1206934286645|1206934289396|2751
09:01:29,816 | INFO | ServiceMix ShutdownHook | ServiceAssemblyLifeCycle |
ework.ServiceAssemblyLifeCycle 161 | Stopping service assembly:
ne3snotifcataions-cxf-sa
09:01:29,816 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle |
framework.ServiceUnitLifeCycle 115 | Stopping service unit:
ne3snotifcataions-cxfse-su
09:01:29,822 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle |
framework.ServiceUnitLifeCycle 115 | Stopping service unit:
ne3snotifcataions-cxfbc-su
09:01:29,823 | WARN | btpool0-177 | DefaultBroker |
rvicemix.jbi.nmr.DefaultBroker 344 | ServiceName
({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}notificationService)
specified for routing, but can't find it registered
09:01:29,823 | WARN | btpool0-177 | DefaultBroker |
rvicemix.jbi.nmr.DefaultBroker 352 | InterfaceName
({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}NE3SBasicNotificationsPort)
specified for routing, but can't find any matching components
09:01:29,824 | WARN | btpool0-177 | DefaultBroker |
rvicemix.jbi.nmr.DefaultBroker 344 | ServiceName
({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}notificationService)
specified for routing, but can't find it registered
09:01:29,824 | WARN | btpool0-177 | DefaultBroker |
rvicemix.jbi.nmr.DefaultBroker 352 | InterfaceName
({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}NE3SBasicNotificationsPort)
specified for routing, but can't find any matching components
09:01:29,825 | INFO | ServiceMix ShutdownHook | ServiceAssemblyLifeCycle |
ework.ServiceAssemblyLifeCycle 207 | Shutting down service assembly:
ne3snotifcataions-cxf-sa
09:01:29,825 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle |
framework.ServiceUnitLifeCycle 134 | Shutting down service unit:
ne3snotifcataions-cxfse-su
09:01:29,649 | INFO | btpool0-202 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:696|1206934287745|1206934289649|1904
09:01:29,830 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle |
framework.ServiceUnitLifeCycle 134 | Shutting down service unit:
ne3snotifcataions-cxfbc-su
09:01:29,647 | INFO | btpool0-114 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:693|1206934287742|1206934289647|1905
09:01:29,643 | INFO | btpool0-154 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:692|1206934287741|1206934289643|1902
09:01:29,642 | INFO | btpool0-222 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:690|1206934287741|1206934289642|1901
09:01:29,859 | INFO | ServiceMix ShutdownHook | QuartzScheduler |
rg.quartz.core.QuartzScheduler 415 | Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED paused.
09:01:29,641 | INFO | btpool0-10 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:758|1206934288690|1206934289641|951
09:01:29,651 | INFO | btpool0-134 | NMRExchangeListener |
servicemix.NMRExchangeListener 42 |
ID:10.58.116.38-11902e2362a-18:768|1206934288703|1206934289651|948
09:01:29,868 | ERROR | btpool0-114 | CxfSeComponent |
ervicemix.common.BaseLifeCycle 48 | Error processing exchange InOut[
Are there any known issues performance with servicemix on linux ?? Since
windows this problem does not occur.
--
View this message in context: http://www.nabble.com/Degraded-performance-and-Exceptions-using-Servicemix-CXF-components-tp16445833p16445833.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Degraded performance and Exceptions using Servicemix CXF components
Posted by Guillaume Nodet <gn...@gmail.com>.
I've already hit such problems which are AFAIK related to the number of
resources opened by the process. In Unix, you can modify these settings
using the ulimit command.
The reason for the components to shutdown is that the auto deployer checks
the files: if it can't open those, it thinks they have been removed and thus
uninstall the components.
On Wed, Apr 2, 2008 at 11:00 AM, spgv <si...@nsn.com> wrote:
>
> Hi,
>
> I have use case where in a client like soapUI pumps SOAP msgs to a cxf bc
> which is then redirected to a cxf se, in the cxf se , the attachement (of
> size 50kb) from the SOAP msg is extracted and sent to a service mix file
> bc which ouputs it a directory.
> While performing load tests for the above use case where the client
> (SOAPUI)
> is running on windows and servicemix instance on linux, there are
> exceptions
> thrown and only a few hundred msgs are dumped.
>
> What happens is that while the msgs are being processed, components are
> deactivated one by one and
> thereafter a flood of exceptions occur.
>
> I am using a listener to see the msgs going between the components.
>
>
> 09:01:29,800 | INFO | ServiceMix ShutdownHook | JBIContainer
> |
> mix.jbi.container.JBIContainer 940 | Deactivating component
> #SubscriptionManager#
> 09:01:29,800 | INFO | ServiceMix ShutdownHook | JBIContainer
> |
> mix.jbi.container.JBIContainer 940 | Deactivating component
> #SubscriptionManager#
> 09:01:29,396 | INFO | btpool0-1 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:578|1206934286645|1206934289396|2751
> 09:01:29,396 | INFO | btpool0-116 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:577|1206934286645|1206934289396|2751
> 09:01:29,816 | INFO | ServiceMix ShutdownHook | ServiceAssemblyLifeCycle
> |
> ework.ServiceAssemblyLifeCycle 161 | Stopping service assembly:
> ne3snotifcataions-cxf-sa
> 09:01:29,816 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle
> |
> framework.ServiceUnitLifeCycle 115 | Stopping service unit:
> ne3snotifcataions-cxfse-su
> 09:01:29,822 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle
> |
> framework.ServiceUnitLifeCycle 115 | Stopping service unit:
> ne3snotifcataions-cxfbc-su
> 09:01:29,823 | WARN | btpool0-177 | DefaultBroker |
> rvicemix.jbi.nmr.DefaultBroker 344 | ServiceName
> ({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}notificationService<http://www.nsn.com/schemas/ne3s/wsdl/common/1.0%7DnotificationService>
> )
> specified for routing, but can't find it registered
> 09:01:29,823 | WARN | btpool0-177 | DefaultBroker |
> rvicemix.jbi.nmr.DefaultBroker 352 | InterfaceName
> ({
> http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}NE3SBasicNotificationsPort<http://www.nsn.com/schemas/ne3s/wsdl/common/1.0%7DNE3SBasicNotificationsPort>
> )
> specified for routing, but can't find any matching components
> 09:01:29,824 | WARN | btpool0-177 | DefaultBroker |
> rvicemix.jbi.nmr.DefaultBroker 344 | ServiceName
> ({http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}notificationService<http://www.nsn.com/schemas/ne3s/wsdl/common/1.0%7DnotificationService>
> )
> specified for routing, but can't find it registered
> 09:01:29,824 | WARN | btpool0-177 | DefaultBroker |
> rvicemix.jbi.nmr.DefaultBroker 352 | InterfaceName
> ({
> http://www.nsn.com/schemas/ne3s/wsdl/common/1.0}NE3SBasicNotificationsPort<http://www.nsn.com/schemas/ne3s/wsdl/common/1.0%7DNE3SBasicNotificationsPort>
> )
> specified for routing, but can't find any matching components
> 09:01:29,825 | INFO | ServiceMix ShutdownHook | ServiceAssemblyLifeCycle
> |
> ework.ServiceAssemblyLifeCycle 207 | Shutting down service assembly:
> ne3snotifcataions-cxf-sa
> 09:01:29,825 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle
> |
> framework.ServiceUnitLifeCycle 134 | Shutting down service unit:
> ne3snotifcataions-cxfse-su
> 09:01:29,649 | INFO | btpool0-202 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:696|1206934287745|1206934289649|1904
> 09:01:29,830 | INFO | ServiceMix ShutdownHook | ServiceUnitLifeCycle
> |
> framework.ServiceUnitLifeCycle 134 | Shutting down service unit:
> ne3snotifcataions-cxfbc-su
> 09:01:29,647 | INFO | btpool0-114 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:693|1206934287742|1206934289647|1905
> 09:01:29,643 | INFO | btpool0-154 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:692|1206934287741|1206934289643|1902
> 09:01:29,642 | INFO | btpool0-222 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:690|1206934287741|1206934289642|1901
> 09:01:29,859 | INFO | ServiceMix ShutdownHook | QuartzScheduler
> |
> rg.quartz.core.QuartzScheduler 415 | Scheduler
> DefaultQuartzScheduler_$_NON_CLUSTERED paused.
> 09:01:29,641 | INFO | btpool0-10 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:758|1206934288690|1206934289641|951
> 09:01:29,651 | INFO | btpool0-134 | NMRExchangeListener |
> servicemix.NMRExchangeListener 42 |
> ID:10.58.116.38-11902e2362a-18:768|1206934288703|1206934289651|948
> 09:01:29,868 | ERROR | btpool0-114 | CxfSeComponent |
> ervicemix.common.BaseLifeCycle 48 | Error processing exchange InOut[
>
> Are there any known issues performance with servicemix on linux ?? Since
> windows this problem does not occur.
> --
> View this message in context:
> http://www.nabble.com/Degraded-performance-and-Exceptions-using-Servicemix-CXF-components-tp16445833p16445833.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/