One more thing while you're here, what is the cleanest way to have the MDB inactive on startup?
"jaikiran" wrote:
You mean to avoid messages from being delivered during the startup of JBoss (while your MDB hasn't yet started)? Look for DeliveryActive on this wiki http://www.jboss.org/community/docs/DOC-9334
org.jboss.deployment.DeploymentException: Error for ActivationSpec class org.jboss.resource.adapter.jms.inflow.JmsActivationSpec as JavaBean; - nested throwable: (java.beans.IntrospectionException: No property found for: DeliveryActive on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@2975fa(ra=null destination=topic/NoeudsPerdusDestination isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5))
"chtimi2" wrote:
I tried using DeliveryActive but it says the property doesn't exist?
Thanks, well that's one more reason to try JBoss5 i suppose.