Sorry, the <sm:executorFactory /> element is meant
to be inside the <sm:container /> tag.
It points to the setExecutorFactory method on the JBI
container. So it should look like:
<sm:container ...>
<sm:executorFactory>
...
</sm:executorFactory>
...
</sm:container>
On 9/26/06, Charles Souillard <[EMAIL PROTECTED]> wrote:
Guillaume,
thanks for your help.
As I am using sm as a webapp, I have added these lines into
WEB-INF/applicationContext.xml file.
Now, when my webapp is being deployed, I get a ClassNotFoundException
(see under).
I tried to add geronimo-j2ee-connector_1.5_spec-1.0.1.jar into my webapp
lib dir but this does not change anything. I tied to search a class with
this name and I found one in servicemix-services. This jar was already
in my webapp.
Perhaps there is a jar file to add of spring ?
Can you help me ?
Thanks
Charles
java.lang.ClassNotFoundException: executorFactory; nested exception is
java.lang.ClassNotFoundException: executorFactory
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:423)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:360)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:335)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:142)
at
org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:123)
at
org.apache.xbean.spring.context.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:71)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:294)
at
org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
... 5 more
Caused by:
org.springframework.beans.factory.BeanDefinitionStoreException: Failed
to load type: executorFactory. Reason: java.lang.ClassNotFoundException:
executorFactory; nested exception is java.lang.ClassNotFoundException:
executorFactory
at
org.apache.xbean.spring.context.v2.XBeanQNameHelper.getBeanInfo(XBeanQNameHelper.java:75)
at
org.apache.xbean.spring.context.v2.XBeanQNameHelper.coerceNamespaceAwarePropertyValues(XBeanQNameHelper.java:54)
at
org.apache.xbean.spring.context.v2b.XBeanBeanDefinitionParserDelegate.parseBeanDefinitionElement(XBeanBeanDefinitionParserDelegate.java:62)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:398)
at
org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:205)
at
org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:253)
at
org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:153)
at
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1118)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:141)
at
org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:39)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:496)
at
org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:406)
... 17 more
Caused by: java.lang.ClassNotFoundException: executorFactory
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
at
org.apache.xbean.spring.context.v2.XBeanQNameHelper.loadClass(XBeanQNameHelper.java:107)
at
org.apache.xbean.spring.context.v2.XBeanQNameHelper.getBeanInfo(XBeanQNameHelper.java:72)
... 31 more
Guillaume Nodet wrote:
> If you use lots of sendSync, which is your case, you will need
> to change the default configuration of your thread pool, so that
> you can have an unbounded number of threads, without queuing
> the requests (as the queue will only be processed by existing
> threads). See http://servicemix.goopen.org/site/thread-pools.html
>
> Try with the following snippet
> <sm:executorFactory>
> <bean
> class="org.apache.servicemix.executors.impl.ExecutorFactoryImpl">
> <property name="defaultConfig">
> <bean
> class="org.apache.servicemix.executors.impl.ExecutorConfig">
> <property name="corePoolSize" value="4"/>
> <property name="maximumPoolSize" value="-1"/>
> <property name="queueSize" value="0"/>
> </bean>
> </property>
> </bean>
> </sm:executorFactory>
>
> It changes the default configuration to not use any queues. It means
> that it's not really SEDA anymore, but SEDA is not very effective when
> using only sendSync (as there is always a waiting thread). The above
> configuration should allow the thread pool to grow as needed.
>
> On 9/26/06, Charles Souillard <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I have a factorial service example which was running well with a nightly
>> build from last thursday (2006/09/21) and it is not working at all since
>> yesterday (nightly build 2006/09/25).
>> Between these two dates, I have seen that a thread pool has been added.
>> Is it possible that there is a problem with that ?
>> My example is as follow :
>>
>> client -> sm-http -> BPEL SE -> BPEL Engine -> BPEL-SE.... -> sm-http ->
>> client
>>
>> You can find hereafter the traces I get. In fact, in a normal execution,
>> the following calls are performed :
>>
>
--
Cheers,
Guillaume Nodet
