You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Tomasz Mazan (JIRA)" <ji...@apache.org> on 2008/01/24 18:58:35 UTC
[jira] Created: (GERONIMO-3783) MessageDrivenBean delivery problem
MessageDrivenBean delivery problem
----------------------------------
Key: GERONIMO-3783
URL: https://issues.apache.org/jira/browse/GERONIMO-3783
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 2.1
Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
Reporter: Tomasz Mazan
Priority: Critical
MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
After restart a few next messages are delivered to MDB, and it stops again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3783) MessageDrivenBean delivery problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-3783:
--------------------------------------
Assignee: David Jencks
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Assignee: David Jencks
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563020#action_12563020 ]
Manu T George commented on GERONIMO-3783:
-----------------------------------------
Modified plan
----------------------
<?xml version="1.0" encoding="UTF-8"?>
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2" xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2">
<sys:environment>
<sys:moduleId>
<sys:groupId>org.apache.geronimo.test.mdb</sys:groupId>
<sys:artifactId>MessageReceiversDestinations</sys:artifactId>
<sys:version>1.0</sys:version>
<sys:type>jar</sys:type>
</sys:moduleId>
<sys:dependencies>
<sys:dependency>
<sys:groupId>org.apache.geronimo.configs</sys:groupId>
<sys:artifactId>activemq-broker</sys:artifactId>
<sys:type>car</sys:type>
</sys:dependency>
</sys:dependencies>
</sys:environment>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>NewWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversResp</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>NewWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>NewWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<adminobject>
<adminobject-interface>javax.jms.Queue</adminobject-interface>
<adminobject-class>org.apache.activemq.command.ActiveMQQueue</adminobject-class>
<adminobject-instance>
<message-destination-name>MRRequests</message-destination-name>
<config-property-setting name="PhysicalName">MRRequests</config-property-setting>
</adminobject-instance>
<adminobject-instance>
<message-destination-name>MRResponses</message-destination-name>
<config-property-setting name="PhysicalName">MRResponses</config-property-setting>
</adminobject-instance>
</adminobject>
<gbean name="NewConnectorThreadPool" class="org.apache.geronimo.pool.ThreadPool">
<attribute name="keepAliveTime">1000</attribute>
<attribute name="poolSize">500</attribute>
<attribute name="poolName">NewConnectorThreadPool</attribute>
<attribute name="waitWhenBlocked">false</attribute>
</gbean>
<gbean name="NewWorkManager" class="org.apache.geronimo.connector.work.GeronimoWorkManagerGBean">
<reference name="SyncPool">
<name>NewConnectorThreadPool</name>
</reference>
<reference name="StartPool">
<name>NewConnectorThreadPool</name>
</reference>
<reference name="ScheduledPool">
<name>NewConnectorThreadPool</name>
</reference>
<reference name="TransactionManager">
<name>TransactionManager</name>
</reference>
</gbean>
<!-- <sys:gbean name="AdminObjectBindings" class="org.apache.geronimo.connector.globaljndi.AdminObjectBindings">
<sys:attribute name="nameInNamespace">jms:dest</sys:attribute>
<sys:attribute name="type">javax.jms.Destination</sys:attribute>
<sys:attribute name="regularExpression">^MR.+$</sys:attribute>
</sys:gbean>
<sys:gbean name="ConnectionFactoryBindings" class="org.apache.geronimo.connector.globaljndi.ConnectionFactoryBindings">
<sys:attribute name="nameInNamespace">jms:conn</sys:attribute>
<sys:attribute name="type">javax.jms.ConnectionFactory</sys:attribute>
<sys:attribute name="regularExpression">^MR.*ConnectionFactory$</sys:attribute>
</sys:gbean> -->
</connector>
---------------------------------
the below values were working with the instanceLimit of the Mdb at 20
@MessageDriven(name = "SimpleMessageReceiver",
activationConfig = {
@ActivationConfigProperty(propertyName="destination", propertyValue="MRRequests"),
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge"),
@ActivationConfigProperty(propertyName="InitialRedeliveryDelay", propertyValue="30000"),
@ActivationConfigProperty(propertyName="MaximumRedeliveries", propertyValue="9999"),
@ActivationConfigProperty(propertyName="maxMessagesPerSessions", propertyValue="20"),
@ActivationConfigProperty(propertyName="maxSessions", propertyValue="20")
})
-------------------------------------
Setting the instance limit via SystemProperties
There is actually a Gbean for setting system property.The GBean needs to
be added to the j2ee-server configuration in the config.xml file as
follows
<module name="org.apache.geronimo.configs/j2ee-server/2.0.1/car">
<gbean gbeanInfo="org.apache.geronimo.system.properties.SystemProperties" name="org.apache.geronimo.configs/j2ee-server/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-server/2.0.1/car,j2eeType=GBean,name=CustomPropertiesGBean">
<attribute name="systemProperties">Default\ MDB\ Container.InstanceLimit=20</attribute>
</gbean>
</module>
---------------------------------------------
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563159#action_12563159 ]
Kevan Miller commented on GERONIMO-3783:
----------------------------------------
Hi Tomasz,
the pool size attributes settable on ThreadPool are:
minPoolSize
maxPoolSize
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean
delivery problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565525#action_12565525 ]
beniamin edited comment on GERONIMO-3783 at 2/4/08 1:00 PM:
----------------------------------------------------------------
I've edited deployment plan and finally have RAs like below:
<pre>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
</pre>
It's not working if <code>maxSessions</code> not equals <code>maxMessagesPerSessions</code>
was (Author: beniamin):
I've edited deployment plan and finally have RAs like below:
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
It's not working if <code>maxSessions</code> not equals <code>maxMessagesPerSessions</code>
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581498#action_12581498 ]
David Jencks commented on GERONIMO-3783:
----------------------------------------
After talking with Manu I discovered the problem was that after a message delivery is committed there is no attempt to send the next prefetch batch. Fixed in https://issues.apache.org/activemq/browse/AMQ-1632 in activemq branch 4.1. Leaving open until at least a 4.1.2-SNAPSHOT is available.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Assignee: David Jencks
> Priority: Critical
> Fix For: 2.1.1, 2.2
>
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean
delivery problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565525#action_12565525 ]
beniamin edited comment on GERONIMO-3783 at 2/4/08 1:02 PM:
----------------------------------------------------------------
I've edited deployment plan and finally have RAs like below:
{noformat}
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
{noformat}
It's not working if {{maxSessions}} not equals {{maxMessagesPerSessions}}
was (Author: beniamin):
I've edited deployment plan and finally have RAs like below:
<pre>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
</pre>
It's not working if <code>maxSessions</code> not equals <code>maxMessagesPerSessions</code>
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3783) MessageDrivenBean delivery problem
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn updated GERONIMO-3783:
-------------------------------
Fix Version/s: 2.2
2.1.1
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Assignee: David Jencks
> Priority: Critical
> Fix For: 2.1.1, 2.2
>
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581416#action_12581416 ]
David Jencks commented on GERONIMO-3783:
----------------------------------------
I modified the test a bit to fit into our testsuite and committed it in rev 640238 in trunk.
Its still broken. I've been working with a copy of activemq with ACTIVEMQ-1438 applied so the vm transport works.
To enable the test, uncomment the checking part of MessageSenderTest.
Things that make the test pass:
1. turning off transactions on the mdb. Leaving transactions on but not sending the response message does not make any difference.
2. Increasing the maxMessagesPerSessions in the activation spec to at least 10. I think this means that all the messages fit in a prefetch for a session attached to an mdb.
By turning on a queue browser I can see that the messages are piling up in the request queue and not getting delived to the mdb.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Assignee: David Jencks
> Priority: Critical
> Fix For: 2.1.1, 2.2
>
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3783) MessageDrivenBean delivery problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomasz Mazan updated GERONIMO-3783:
-----------------------------------
Description:
MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
After restart a few next messages are delivered to MDB, and it stops again.
Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
was:
MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
After restart a few next messages are delivered to MDB, and it stops again.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565525#action_12565525 ]
Tomasz Mazan commented on GERONIMO-3783:
----------------------------------------
I've edited deployment plan and finally have RAs like below:
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversMDB</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MRConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>MessageSender</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>MSConnectionFactory</name>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<max-size>20</max-size>
<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
<select-one-assume-match/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
It's not working if <code>maxSessions</code> not equals <code>maxMessagesPerSessions</code>
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562990#action_12562990 ]
Tomasz Mazan commented on GERONIMO-3783:
----------------------------------------
Thanks for your advice. I'll check that way ASAP.
Please, give me the instruction how to provide enough threads to RA. How can I manage them ?
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3783) MessageDrivenBean delivery problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-3783.
----------------------------------
Resolution: Fixed
This should be fixed in branches/2.1 and trunk now using activemq 4.1-SNAPSHOT and openejb 3.1-SNAPSHOT. Both of these should be released and included in g. 2.1.1.
Porting commit from trunk to branches/2.1 rev 643217.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Assignee: David Jencks
> Priority: Critical
> Fix For: 2.1.1, 2.2
>
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean
delivery problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562155#action_12562155 ]
beniamin edited comment on GERONIMO-3783 at 1/25/08 2:25 PM:
-----------------------------------------------------------------
Example to show my problem.
Requirements:
1. installed Geronimo 2.1-snapshot
2. Ant 1.7.0
3. not to have Junit 3 on the classpath
You need to:
- edit build.properties file
- run targets:
- deploy
- test / test-with-report
was (Author: beniamin):
Example to show my problem.
Requirements:
1. installed Geronimo 2.1-snapshot
You need to:
- edit build.properties file
- run targets:
- deploy
- test / test-with-report
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3783) MessageDrivenBean delivery problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomasz Mazan updated GERONIMO-3783:
-----------------------------------
Attachment: mdb-issue.zip
Example to show my problem.
Requirements:
1. installed Geronimo 2.1-snapshot
You need to:
- edit build.properties file
- run targets:
- deploy
- test / test-with-report
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563154#action_12563154 ]
Tomasz Mazan commented on GERONIMO-3783:
----------------------------------------
Nonetheless exception above Setting maxSessions == maxMessagesPerSessions could avoid stop in processing messages
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579171#action_12579171 ]
David Jencks commented on GERONIMO-3783:
----------------------------------------
Is this still a problem with the latest 4.1 activemq code and using tcp rather than vm transport?
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564283#action_12564283 ]
Kevan Miller commented on GERONIMO-3783:
----------------------------------------
Right. In src/conf/MessageReceiversJmsPlan.xml update the MessageReceiversResp resourceadapter-instance as follows:
<resourceadapter-instance>
<resourceadapter-name>MessageReceiversResp</resourceadapter-name>
<config-property-setting name="UseInboundSession">true</config-property-setting>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
It looked like messages were being processed correctly, but am not 100% sure. The log messages indicated that all messages were being received by the MDB. I tried to get HermesJMS set up to introspect the ActiveMQ queues, to be sure. However, I didn't get it working right away, and haven't gotten back to it...
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Tomasz Mazan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563136#action_12563136 ]
Tomasz Mazan commented on GERONIMO-3783:
----------------------------------------
I got exception when I try to set ThreadPool's attribute <i>poolSize</i>. I want to emphasize I use Geronimo 2.1-SNAPSHOT
14:06:48,968 WARN [ConfigurationUtil] Could not load gbean org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/jar?J2EEApplicatio
n=null,ResourceAdapterModule=org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/jar,j2eeType=GBean,name=MRConnectorThreadPool
org.apache.geronimo.gbean.InvalidConfigurationException: Could not inject configuration data into the GBean org.apache.geronimo.test.mdb/Mes
sageReceiversDestinations/1.0/jar?J2EEApplication=null,ResourceAdapterModule=org.apache.geronimo.test.mdb/MessageReceiversDestinations/1.0/j
ar,j2eeType=GBean,name=MRConnectorThreadPool
at org.apache.geronimo.gbean.runtime.GBeanInstance.<init>(GBeanInstance.java:375)
at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:354)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:433)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:515)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865)
at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at sun.reflect.GeneratedMethodAccessor133.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: Attribute is not persistent Attribute Name: poolSize, Type: int, GBeanInstance: org.apache.geron
imo.pool.ThreadPool
at org.apache.geronimo.gbean.runtime.GBeanAttribute.setPersistentValue(GBeanAttribute.java:360)
at org.apache.geronimo.gbean.runtime.GBeanInstance.setAttribute(GBeanInstance.java:762)
at org.apache.geronimo.gbean.runtime.GBeanInstance.<init>(GBeanInstance.java:370)
... 43 more
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564184#action_12564184 ]
David Jencks commented on GERONIMO-3783:
----------------------------------------
Kevan and I did some experiments and found a configuration that works. I'm pretty sure there's a bug in the AMQ transaction handling causing the actual issue, but we didn't look for it.
You need 2 amq resource adapters set up.
The mdb uses one, and in the ra config properties you set useInboundSession to true.
The session bean (that sends the original messages) uses the other, and it has the default useInboundSession false set.
This makes the mdb reuse the inbound session to send out the response messages and it appears to work fine for lots of messages. Maybe kevan can post a patch or the updated code we used.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562902#action_12562902 ]
Manu T George commented on GERONIMO-3783:
-----------------------------------------
Hi Tomaz,
One thing that you can check is whether the ActivationConfigProperties maxSessions and maxMessagesPerSessions are both set to 10. Actually the instanceLimit by default is 10 in geronimo for Mdbs and so only 10 instances of the same MDB exist. If you are rasing the instance limit to say 100 then raise both maxSessions and maxMessagesPerSessions (refer AMQ http://activemq.apache.org/activation-spec-properties.html) such that they are also 100 or <100.
Both should be same i.e maxSessions == maxMessagesPerSessions <= instanceLimit.
The instance limit can be set via the system property Default MDB Container.InstanceLimit=125.
You can set it via the SystemPropertiesGbean or pass it during startup as a system property.
eg: usage (modify the config.xml )
Change
<module name="org.apache.geronimo.configs/j2ee-server/2.0.1/car"/>
to
<module name="org.apache.geronimo.configs/j2ee-server/2.0.1/car">
<gbean gbeanInfo="org.apache.geronimo.system.properties.SystemProperties" name="org.apache.geronimo.configs/j2ee-server/2.0.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-server/2.0.1/car,j2eeType=GBean,name=CustomPropertiesGBean">
<attribute name="systemProperties">Default\ MDB\ Container.InstanceLimit=100</attribute>
</gbean>
</module>
Another thing to note is that you should provide enough threads to the RA. Atleast 100 free threads for 100 parallel Mdbs. So its recommended to increase the size of the server thread pool or provide a separate threadpool to the resource adapter that your Mdb uses.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery
problem
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564087#action_12564087 ]
Jarek Gawor commented on GERONIMO-3783:
---------------------------------------
I've been debugging this issue a little and I'm getting lost in the activemq code since I'm not familiar with it.
What I see is that sometimes the messages get dispatched right away and sometimes they get queued. Once there are messages in the queue , the new incoming messages will be queued (which makes sense). However, the messages in the queue are never dispatched until the mdb is restarted. There is a method to process the queued messages but it appears not to be called. That's where I'm getting lost. I'm not sure when or what should be calling this method. Btw, the decision to queue or dispatch right away happens in PrefetchSubscription.add(MessageReference) function.
Increasing the prefetchSize value (or how it is known as 'maxMessagesPerSessions' in the activation spec) helps but does not completely remove the problem.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.