You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by goldi <go...@freenet.de> on 2007/08/03 16:58:15 UTC

Thread Configuration!

Hy everybody,

I need one of my components in a single thread this component I deployed to
lwcontainer and configured "lwcontainer-ExecutorConfig"  as follows (I'm
using jca-flow):

<property name="configs">
	<map>
		<entry key="flow.jca.servicemix-lwcontainer">
			<bean class="org.apache.servicemix.executors.impl.ExecutorConfig">
				<property name="corePoolSize" value="1"/>
				<property name="maximumPoolSize" value="1"/>
				<property name="queueSize" value="1000"/>
			</bean>
		</entry>
	</map>
</property>

But in the log-File I see that for my Component are more then one Thread
created. I also tried
entry-key I also tried:
	<entry key="pool-flow.jca.servicemix-lwcontainer">

but nothing changed. Can someone help?

Greets Goldi



-- 
View this message in context: http://www.nabble.com/Thread-Configuration%21-tf4213032s12049.html#a11984953
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: Thread Configuration!

Posted by goldi <go...@freenet.de>.
I tried the following:


<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="${servicemix.corePoolSize}"/>
						<property name="maximumPoolSize"
value="${servicemix.maximumPoolSize}"/>
						<property name="queueSize" value="${servicemix.queueSize}"/>
					</bean>
				</property>
				<property name="configs">
					<map>
						<entry key="flow.jca.fileToQueueTransmitter">
							<bean class="org.apache.servicemix.executors.impl.ExecutorConfig">
								<property name="corePoolSize" value="1"/>
								<property name="maximumPoolSize" value="1"/>
								<property name="queueSize" value="1000"/>
							</bean>
						</entry>
					</map>
				</property>
			</bean>
		</sm:executorFactory>


my activationspec:

<sm:activationSpec componentName="fileToQueueTransmitter"
service="prologsFQ:FileToQueueTransmitter" >
		<sm:component>
			<!--myBean-->
			
		</sm:component>
</sm:activationSpec>

but in the logfile I see something like following:

...fileToQueueTransmitter-thread-3 
...fileToQueueTransmitter-thread-3 
...fileToQueueTransmitter-thread-4 
...fileToQueueTransmitter-thread-4
...fileToQueueTransmitter-thread-5 
...fileToQueueTransmitter-thread-5
...fileToQueueTransmitter-thread-3 
...fileToQueueTransmitter-thread-6
...


So it don't seem to work I think.

Greets Goldi



gnodet wrote:
> 
> Each lightweight component deployed on the lwcontainer is actually
> considered as a jbi component.
> So you may want to try:
>    flow.jca.your-lightweight-component-name
> 
> You can choose the name with the componentName attribute on the
> activationSpec.
> 
> 
> On 8/3/07, goldi <go...@freenet.de> wrote:
>>
>> Hy everybody,
>>
>> I need one of my components in a single thread this component I deployed
>> to
>> lwcontainer and configured "lwcontainer-ExecutorConfig"  as follows (I'm
>> using jca-flow):
>>
>> <property name="configs">
>>         <map>
>>                 <entry key="flow.jca.servicemix-lwcontainer">
>>                         <bean
>> class="org.apache.servicemix.executors.impl.ExecutorConfig">
>>                                 <property name="corePoolSize" value="1"/>
>>                                 <property name="maximumPoolSize"
>> value="1"/>
>>                                 <property name="queueSize" value="1000"/>
>>                         </bean>
>>                 </entry>
>>         </map>
>> </property>
>>
>> But in the log-File I see that for my Component are more then one Thread
>> created. I also tried
>> entry-key I also tried:
>>         <entry key="pool-flow.jca.servicemix-lwcontainer">
>>
>> but nothing changed. Can someone help?
>>
>> Greets Goldi
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Thread-Configuration%21-tf4213032s12049.html#a11984953
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/
> 
> 

-- 
View this message in context: http://www.nabble.com/Thread-Configuration%21-tf4213032s12049.html#a12035858
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: Thread Configuration!

Posted by Guillaume Nodet <gn...@gmail.com>.
Each lightweight component deployed on the lwcontainer is actually
considered as a jbi component.
So you may want to try:
   flow.jca.your-lightweight-component-name

You can choose the name with the componentName attribute on the activationSpec.


On 8/3/07, goldi <go...@freenet.de> wrote:
>
> Hy everybody,
>
> I need one of my components in a single thread this component I deployed to
> lwcontainer and configured "lwcontainer-ExecutorConfig"  as follows (I'm
> using jca-flow):
>
> <property name="configs">
>         <map>
>                 <entry key="flow.jca.servicemix-lwcontainer">
>                         <bean class="org.apache.servicemix.executors.impl.ExecutorConfig">
>                                 <property name="corePoolSize" value="1"/>
>                                 <property name="maximumPoolSize" value="1"/>
>                                 <property name="queueSize" value="1000"/>
>                         </bean>
>                 </entry>
>         </map>
> </property>
>
> But in the log-File I see that for my Component are more then one Thread
> created. I also tried
> entry-key I also tried:
>         <entry key="pool-flow.jca.servicemix-lwcontainer">
>
> but nothing changed. Can someone help?
>
> Greets Goldi
>
>
>
>
> --
> View this message in context: http://www.nabble.com/Thread-Configuration%21-tf4213032s12049.html#a11984953
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/