I believe there was a similar issue some time back where u needed
maxSessions and maxMessagesPerSession to be equal. So can you try
giving both and making them equal. The jira is
https://issues.apache.org/jira/browse/GERONIMO-3783
David Jencks had fixed this issue to the best of my knowledge and so
this shouldn't happen but just try whether that makes any difference.
Another thing that you can try is increasing the number of threads in
the thread pool for the RA.
Regards
Manu.
On Fri, Jul 18, 2008 at 6:55 PM, Mario Kofler <[EMAIL PROTECTED]> wrote:
> hello,
>
> after all i specify it in my mdb via
>
> @MessageDriven(activationConfig = {
> @ActivationConfigProperty(propertyName = "destinationType",
> propertyValue = "javax.jms.Queue"),
> @ActivationConfigProperty(propertyName = "maxSessions",
> propertyValue = "20"),
> @ActivationConfigProperty(propertyName = "destination",
> propertyValue = "queue/videoupdate")})
>
> HOWEVER after i inserted the maxSessions property no messages get
> delivered anymore. also when i change back the prop by commenting it
> out i dont get messages anymore through my queue. so my database is
> never updated.
>
> after this error i do not know anything else than reinstalling the
> whole server. i dont even get an error. just no update in the database
> anymore and that's it.
>
> maybe some ideas?
>
> thanks a lot,
>
> mario.
>
> 2008/7/17 Lin Sun <[EMAIL PROTECTED]>:
>> Did you try increasing the maxSessions and maxMessagesPerSessions
>> values in your openejb deployment plan? The default is 10.
>>
>> Here is some information on this -
>> http://activemq.apache.org/activation-spec-properties.html
>>
>> Lin
>>
>> On Thu, Jul 17, 2008 at 1:17 PM, Mario Kofler <[EMAIL PROTECTED]> wrote:
>>> 2008/7/16 David Jencks <[EMAIL PROTECTED]>:
>>>> I think there's a setting for the mdb pool size in the activation spec.
>>>> Also it looks like the DefaultWorkManager only has 30 threads which is
>>>> pretty low but I don't see offhand how this would result in only 10 worker
>>>> threads.
>>>
>>> hello,
>>>
>>> i suppose it is right to set the MDB container instance size in the
>>> config.xml for this?
>>>
>>> <gbean
>>> name="org.apache.geronimo.configs/j2ee-server/2.1.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-server/2.1.1/car,j2eeType=GBean,name=CustomPropertiesGBean"
>>> gbeanInfo="org.apache.geronimo.system.properties.SystemProperties">
>>> <attribute name="systemProperties">Default\ MDB\
>>> Container.InstanceLimit=32</attribute>
>>> </gbean>
>>> </module>
>>>
>>> but still i just get 10 concurrent worker threads to my database....
>>> very strange.
>>>
>>> regards,
>>>
>>> mario.
>>>
>>
>
