Ramesh,
Yes sorry I inverse the order of the properties into my email. Here is the the server.log and my MDB configuration. As I said before the value is not set even if I change it to EndpointExceptionRedeliveryAttempts
@MessageDriven(
name = "OrganizerMDB", mappedName= UlysseConstants.ARCHIVE_REQUEST_QUEUE_NAME,
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destinationName", propertyValue = UlysseConstants.ARCHIVE_REQUEST_QUEUE_NAME),
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "flow = '"+HCRArchiveRequest.FLOW_VOLUME_MANAGER+"'"),
@ActivationConfigProperty(propertyName = "EndpointExceptionRedeliveryAttempts", propertyValue = "777"),
@ActivationConfigProperty(propertyName = "sendUndeliverableMsgsToDMQ", propertyValue = "false")
}
Regards. Yvan
-----Original Message-----
From: Ramesh.Parthasarathy_at_Sun.COM [mailto:Ramesh.Parthasarathy_at_Sun.COM]
Sent: vendredi, 24. août 2007 12:28
To: Hess Yvan
Subject: Re: How to change the property "endpointExceptionRedeliveryAttempts" of JMS queue for a MDB
Hi Yvan,
I guess you meant that you changed it from endpointExceptionRedeliveryAttempts to EndpointExceptionRedeliveryAttempts
Anyway the MDB activation spec should be like this
@ActivationConfigProperty(propertyName = "EndpointExceptionRedeliveryAttempts", propertyValue = "777"),
If this is not working then could you please send me the logs
Thanks
-Ramesh
Hess Yvan wrote On 08/24/07 09:03,:
> Ramesh,
>
> I opened an issue for the problem, have a look at https://glassfish.dev.java.net/issues/show_bug.cgi?id=3530.
> Changing the property from EndpointExceptionRedeliveryAttempts to
> endpointExceptionRedeliveryAttempts doens'nt change the
> problem...Still the same situation. I will wait that the bug will be
> fix
>
> Thanks for you help. Regards. Yvan
>
> -----Original Message-----
> From: Ramesh.Parthasarathy_at_Sun.COM
> [mailto:Ramesh.Parthasarathy_at_Sun.COM]
> Sent: vendredi, 24. août 2007 10:19
> To: users_at_glassfish.dev.java.net
> Subject: Re: How to change the property
> "endpointExceptionRedeliveryAttempts" of JMS queue for a MDB
>
> Hi Yvan,
> Yes this looks like a bug, when setting the properties on the jmsra.
> Before setting the properties in the jmsra we try to merge the jmsra default properties and the MDB properties. The default property is "EndpointExceptionRedeliveryAttempts" (note the change in case in the first character). This seems to be overriding whatever you set on the MDB.
> As a workaround could you change the propertyName in your MDB to "EndpointExceptionRedeliveryAttempts".
>
> Please raise an issue in the Issue tracker, we will address this for the next release.
>
> Thanks
> -Ramesh
>
>
>
>
>
> Hess Yvan wrote On 08/24/07 07:20,:
>
>>Hi Ramesh
>>
>>First thanks for your help. I changed the log level for the different
>>components you specified and you can find the server log as attachement. Just be carefull because I deployed an EAR application containing two MDB. The concerned one is the "OrganizerMDB". Here is the definition of the bean @MessageDriven(
>> name = "OrganizerMDB", mappedName= UlysseConstants.ARCHIVE_REQUEST_QUEUE_NAME,
>> activationConfig = {
>> @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
>> @ActivationConfigProperty(propertyName = "destinationName", propertyValue = UlysseConstants.ARCHIVE_REQUEST_QUEUE_NAME),
>> @ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "flow = '"+HCRArchiveRequest.FLOW_VOLUME_MANAGER+"'"),
>> @ActivationConfigProperty(propertyName = "endpointExceptionRedeliveryAttempts", propertyValue = "777"),
>> @ActivationConfigProperty(propertyName = "sendUndeliverableMsgsToDMQ", propertyValue = "false")
>> }
>>)
>>
>>As you can see I tried to change "endpointExceptionRedeliveryAttempts" and "sendUndeliverableMsgsToDMQ" properties. In my first test I changed only the "endpointExceptionRedeliveryAttempts". Analyzing the log I detected that the sendUndeliverableMsgsToDMQ value is realy change, but not the endpointExceptionRedeliveryAttempts even if the method is called. It is a bug of glassfish V2 RC1 or am I doing something wrong ? If it is a bug of glassfish is it solved into version V2 RC4 ?
>>
>>One more time, thanks for you help
>>
>>Yvan
>>
>>-----Original Message-----
>>From: Ramesh.Parthasarathy_at_Sun.COM
>>[mailto:Ramesh.Parthasarathy_at_Sun.COM]
>>Sent: vendredi, 24. août 2007 04:14
>>To: users_at_glassfish.dev.java.net
>>Subject: Re: How to change the property
>>"endpointExceptionRedeliveryAttempts" of JMS queue for a MDB
>>
>>Hi Yvan,
>> Could you set the jms, resource-adapter and connector log levels to FINEST and send the logs that are generated when you deploy the MDB.
>>This will help us find out if these properties are really getting set on the jmsra Thanks -Ramesh Hess Yvan wrote:
>>
>>
>>>Hi,
>>>Throwing an exception from a Message Driven Bean from glassfish
>>>server
>>>V2 RC1 , I got into the server.log the message:
>>>
>>>[#|2007-08-23T18:05:35.563+0200|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=29;_ThreadName=p:
>>>thread-pool-1; w:
>>>12;_RequestID=e2bc5c00-653c-4b7d-ad4a-23de8d440cd4;|
>>>MQRA:OMR:run:Exhausted redeliveryAttempts-spec=ActvationSpec
>>>configuration=
>>>DestinationType =javax.jms.Queue
>>>Destination =achiveRequestPhysical
>>>MessageSelector =flow = 'VOLUME_MANAGER'
>>>AcknowledgeMode =Auto-acknowledge
>>>SubscriptionDurability =NonDurable
>>>ClientId =null
>>>SubscriptionName =null
>>>EndpointPoolMaxSize =32
>>>EndpointPoolSteadySize =0
>>>EndpointPoolResizeCount =8
>>>EndpointPoolResizeTimeout =600
>>>EndpointExceptionRedeliveryAttempts =1
>>>EndpointExceptionRedeliveryInterval =500
>>>SendUndeliverableMsgsToDMQ =true
>>>GroupName =null
>>>RAUID =null
>>>InClusteredContainer =false
>>>MdbName =null
>>>UserName =null
>>>AddressList (in effect) =localhost:7676
>>>|#]
>>>
>>>
>>>I would like to change the value of
>>>endpointExceptionRedeliveryAttempts from 1 to 7 for my MDB from the
>>>glassfish admin console or directly inside the definition of my MDB
>>>using annotation. I am new in the usage of glassfish application
>>>server and I tested a lot of solutions to change this value and I
>>>never succeed. It seems it is linked to "jmsra" resource but I don't
>>>know how I can change the properties of this resource.
>>>I tested for example to add the
>>>@ActivationConfigProperty(propertyName
>>>= "endpointExceptionRedeliveryAttempts", propertyValue = "7") into my
>>>@MessageDriven annotation of my MDB but nothing change.I am a little
>>>be lost and HELP will be appreciate.
>>>
>>>Regards and thanks in advance for your help
>>>
>>>Yvan
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>>----------------------------------------------------------------------
>>--
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>