[jboss-jira] [JBoss JIRA] Updated: (JBAS-4306) Invalid invoker mbean names in standardjboss.xml
Dimitris Andreadis (JIRA)
jira-events at lists.jboss.org
Mon Dec 3 06:21:51 EST 2007
[ http://jira.jboss.com/jira/browse/JBAS-4306?page=all ]
Dimitris Andreadis updated JBAS-4306:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta3)
This issue needs a forum thread, I suppose? Can't figure out whats the real issue.
> Invalid invoker mbean names in standardjboss.xml
> ------------------------------------------------
>
> Key: JBAS-4306
> URL: http://jira.jboss.com/jira/browse/JBAS-4306
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-5.0.0.Beta2
> Reporter: Scott M Stark
> Assigned To: Scott M Stark
> Fix For: JBossAS-5.0.0.CR1
>
>
> The following invoker-proxy-binding is useless in terms of defining the invoker-mbean such that it can be used as a ejb container dependency:
> <invoker-proxy-binding>
> <name>message-driven-bean</name>
> <invoker-mbean>default</invoker-mbean>
> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
> <proxy-factory-config>
> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
> <CreateJBossMQDestination>false</CreateJBossMQDestination>
> <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
> <MinimumSize>1</MinimumSize>
> <MaximumSize>15</MaximumSize>
> <KeepAliveMillis>30000</KeepAliveMillis>
> <MaxMessages>1</MaxMessages>
> <MDBConfig>
> <ReconnectIntervalSec>10</ReconnectIntervalSec>
> <DLQConfig>
> <DestinationQueue>queue/DLQ</DestinationQueue>
> <MaxTimesRedelivered>10</MaxTimesRedelivered>
> <TimeToLive>0</TimeToLive>
> </DLQConfig>
> </MDBConfig>
> </proxy-factory-config>
> </invoker-proxy-binding>
> Either there should be an mbean representing the state of the default invoker, or the mdb invoker config specified in another way such that dependencies can be configured.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list