Hi,
we were using Servicemix 3.2.1 and it worked fine except of some haevy load
issues. But we needed to deploy the new Servicemix 3.3 version for some new
services which weren't running on the older 3.2.1 servicemic core. First it
seems everything works like expected but now we got Exchange aborts from the
DeliveryChannelImpl. We found out that every thing works fine after
restarting servicemix but after 0,5-1 hour every new request is aborted and
we can't find out why. Below you can see a snapshot of servicemix log.
1:52:20,013 | DEBUG | btpool0-2 | CxfBcComponent |
emix.common.AsyncBaseLifeCycle 626 | Created correlation id:
ID:172.30.32.51-12188665756-10:26
11:52:20,014 | DEBUG | btpool0-2 | DeliveryChannelImpl |
.messaging.DeliveryChannelImpl 458 | SendSync
ID:172.30.32.51-12188665756-10:26 in DeliveryChannel{servicemix-cxf-bc}
11:52:20,014 | DEBUG | btpool0-2 | SecuredBroker |
mix.jbi.security.SecuredBroker 66 | send exchange with secure
broker
11:52:20,015 | DEBUG | btpool0-2 | SecuredBroker |
mix.jbi.security.SecuredBroker 72 | service name :{http://xxx}xxx
11:52:20,015 | DEBUG | btpool0-2 | SecuredBroker |
mix.jbi.security.SecuredBroker 73 | operation name
:{http://xxx}xxx
11:52:20,015 | DEBUG | btpool0-2 | SedaFlow |
emix.jbi.nmr.flow.AbstractFlow 118 | Called Flow send
11:52:20,016 | DEBUG | btpool0-2 | DeliveryChannelImpl |
.messaging.DeliveryChannelImpl 703 | Waiting for exchange
ID:172.30.32.51-12188665756-10:26 (e38971) to be answered in
DeliveryChannel{servicemix-cxf-bc} from sendSync
11:52:50,016 | DEBUG | btpool0-2 | DeliveryChannelImpl |
.messaging.DeliveryChannelImpl 714 | Notified:
ID:172.30.32.51-12188665756-10:26(e38971) in
DeliveryChannel{servicemix-cxf-bc} from sendSync
11:52:50,017 | DEBUG | btpool0-2 | DeliveryChannelImpl |
.messaging.DeliveryChannelImpl 502 | Exchange
ID:172.30.32.51-12188665756-10:26 has been aborted
I looked into servicemix with jconsole thoughting it has something to do
with the java heap but it seems not. The only thing I found out that the
current class loaded goes up with every request I send.
VM Summary:
Donnerstag, 4. Juni 2009 13.02 Uhr CEST
Connection name: x...@xxxx:1099
Virtual Machine: Java HotSpot(TM) Server VM version 11.0-b15
Vendor: Sun Microsystems Inc.
Name: 1...@xxx
Uptime: 6 days 16 hours 56 minutes
Process CPU time: 1 hour 41 minutes
JIT compiler: HotSpot Tiered Compilers
Total compile time: 28,657 seconds
Live threads: 342
Peak: 415
Daemon threads: 235
Total threads started: 32.885
Current classes loaded: 51.027
Total classes loaded: 51.361
Total classes unloaded: 334
Current heap size: 51.655 kbytes
Maximum heap size: 518.464 kbytes
Committed memory: 130.112 kbytes
Pending finalization: 0 objects
Garbage collector: Name = 'Copy', Collections = 6.646, Total time spent =
31,983 seconds
Garbage collector: Name = 'MarkSweepCompact', Collections = 173, Total time
spent = 50,595 seconds
Operating System: Linux 2.6.27.24
Architecture: i386
Number of processors: 2
Committed virtual memory: 907.144 kbytes
Total physical memory: 1.533.548 kbytes
Free physical memory: 115.572 kbytes
Total swap space: 4.096.564 kbytes
Free swap space: 4.096.560 kbytes
VM arguments: -Xms128M -Xmx512M
-Dderby.system.home=/opt/servicemix/data/derby
-Dderby.storage.fileSyncTransactionLog=true -Dcom.sun.management.jmxremote
-Dxxx_LOG_DIR=/opt/xxx/log
-Dclassworlds.conf=/opt/servicemix/conf/servicemix.conf
-Dservicemix.home=/opt/servicemix -Dcygwin.user.home=
-Djava.endorsed.dirs=/opt/servicemix/lib/endorsed
Class path: :/opt/servicemix/conf:/opt/servicemix/lib/classworlds-1.0.1.jar
Library path:
/opt/jdk1.6.0_10/jre/lib/i386/server:/opt/jdk1.6.0_10/jre/lib/i386:/opt/jdk1.6.0_10/jre/../lib/i386::/opt/servicemix/lib:/usr/java/packages/lib/i386:/lib:/usr/lib
Boot class path:
/opt/jdk1.6.0_10/jre/lib/resources.jar:/opt/jdk1.6.0_10/jre/lib/rt.jar:/opt/jdk1.6.0_10/jre/lib/sunrsasign.jar:/opt/jdk1.6.0_10/jre/lib/jsse.jar:/opt/jdk1.6.0_10/jre/lib/jce.jar:/opt/jdk1.6.0_10/jre/lib/charsets.jar:/opt/jdk1.6.0_10/jre/classes
CXF-BC Config looks like:
<?xml version="1.0" encoding="UTF-8"?>
<beans
xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0";
xmlns:order="http://xxxx/";>
<bean
class="net.xxx.common.util.spring.StagePropertiesPlaceholderConfigurer"/>
<cxfbc:consumer
wsdl="classpath:orderService.wsdl"
targetService="order:OrderService"
targetInterface="order:orderServicePort"
timeout="${xxx.components.cxf-bc.timeout}"
locationURI="${xxx.components.order.service.soapurl}"/>
</beans>
The Timout is set to 60000 which are 60 seconds.
Anyone with a hint about the aborting problem?
Regards
Crimor
--
View this message in context:
http://www.nabble.com/Switched-from-Servicemix-3.2.1-auf-3.3.3-got-now-exchange-aborts-tp23867981p23867981.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
