You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2006/10/05 20:17:09 UTC
[jira] Commented: (SM-672) SedaFlow - OutOfMemoryError
[ https://issues.apache.org/activemq/browse/SM-672?page=comments#action_37109 ]
Guillaume Nodet commented on SM-672:
------------------------------------
Just made a test with the loan-broker example,
running twice 'ant run-loop' which sends 100.000
messages on the seda flow.
I do not have any memory problems.
Do you have a servicemix.xml configuration file, or SA
to reproduce it, it would ease the process ;)
Will try to investigate more.
> SedaFlow - OutOfMemoryError
> ---------------------------
>
> Key: SM-672
> URL: https://issues.apache.org/activemq/browse/SM-672
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.0
> Environment: windows
> jdk5.0
> Reporter: Michal
>
> When I send lots of messages to a queue inside servicemix using SedaFlow then I run out of memory. Switching to ST flow works fine.
> I used pretty much default settings.
> The flow was:
> - WS client calls WS
> - WS service receives Element (anytype)
> - validates it with xsd (sendSync to validate component)
> - sends message to jms queue (using sendSync)
> http://www.nabble.com/SedaFlow---OutOfMemoryError-tf2382645.html
> activemq.xml
> <broker useJmx="true" xmlns="http://activemq.org/config/1.0" persistent="true">
> <persistenceAdapter>
> <journaledJDBC journalLogFiles="5" dataDirectory="file:./data/amq"/>
> </persistenceAdapter>
> <memoryManager>
> <usageManager id="memory-manager" limit="20048576"/>
> </memoryManager>
> <transportConnectors>
> <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
> </transportConnectors>
> <networkConnectors>
> <networkConnector uri="multicast://default"/>
> </networkConnectors>
> </broker>
> servicemix.xml
> <sm:container id="jbi"
> rootDir="./data/smx"
> MBeanServer="#jmxServer"
> installationDirPath="./install"
> deploymentDirPath="./deploy"
> monitorInterval="1"
> dumpStats="true"
> statsInterval="10"
> transactionManager="#transactionManager"
> workManager="#workManager"
> createJmxConnector="false"
> depends-on="jndi">
> <sm:broker>
> <sm:securedBroker authorizationMap="#authorizationMap">
> <sm:flows>
> <sm:sedaFlow />
> <!--sm:stFlow /-->
> <sm:jcaFlow bootstrapContext="#bootstrapContext"
> connectionManager="#connectionManager"
> jmsURL="tcp://localhost:61616" />
> </sm:flows>
> </sm:securedBroker>
> </sm:broker>
> <sm:activationSpecs>
> </sm:activationSpecs>
> </sm:container>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira