[JBoss JIRA] Created: (JBAS-4945) Messages transfered from DLQ to working queue will never be resent to DLQ
by Mike Clark (JIRA)
Messages transfered from DLQ to working queue will never be resent to DLQ
-------------------------------------------------------------------------
Key: JBAS-4945
URL: http://jira.jboss.com/jira/browse/JBAS-4945
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.5.GA
Reporter: Mike Clark
Assigned To: Adrian Brock
Messages that are retreived from the DLQ have their JMSXDeliveryCount set to 1. Inside org.jboss.ejb.plugins.jms.DLQHander, this leads to the code that redirects failed messages to the DLQ. Starting on line 454, the count gets set to 1, then is decremented to zero. On the next redelivery, the same thing happens again. The JMS_JBOSS_REDELIVERY_COUNT is incremented on each cylce but never gets checked:
try
{
if (msg.propertyExists(PROPERTY_DELIVERY_COUNT)) // Is 1 for a message transferred from DLQ <<<<
count = msg.getIntProperty(PROPERTY_DELIVERY_COUNT);
}
catch (JMSException ignored)
{
}
if (count > 0)
{
// The delivery count is one too many
--count; // Becomes zero for message transferred from DLQ <<<
}
else if (msg.propertyExists(JMS_JBOSS_REDELIVERY_COUNT))
count = msg.getIntProperty(JMS_JBOSS_REDELIVERY_COUNT);
else
{
id = msg.getJMSMessageID();
if (id == null)
{
// if we can't get the id we are basically f**ked
log.error("Message id is null, can't handle message");
return false;
}
count = incrementResentCount(id);
fromMessage = false;
}
if (count > max) // Count is always zero for a message that has been transfered from DLQ <<<<
{
id = msg.getJMSMessageID();
log.warn("Message resent too many times; sending it to DLQ; message id=" + id);
sendMessage(msg);
deleteFromBuffer(id);
handled = true;
}
Cheers,
Mike C.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBPORTAL-1783) Handling Oracle (OC4J) WSRP Producers - Preference Information
by Dave Rowe (JIRA)
Handling Oracle (OC4J) WSRP Producers - Preference Information
--------------------------------------------------------------
Key: JBPORTAL-1783
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1783
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.2 Final
Environment: Oracle OC4J 10.1.3.3.0, JBoss bundled 2.6 release (downloaded yesterday 11/06/2007)
Reporter: Dave Rowe
Assigned To: Chris Laprun
Currently the Oracle WSRP implementation doesn't support PortletPropertyDescriptions, so when trying to use Oracle portlets, exceptions are thrown "Not yet implemented".
In org.jboss.portal.wsrp.consumer.portlet.info.WSRPPortletInfo, there needs to be a try / catch or something around the ' originatingProducer.getPropertyDescriptionsFor(portletHandle); to fail safely.
--
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
17 years, 1 month
[JBoss JIRA] Commented: (JBAS-1802) Need a way to support refreshing security roles within a session
by Anil Saldhana (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1802?page=comments#action_12386581 ]
Anil Saldhana commented on JBAS-1802:
-------------------------------------
Going forward, we will fix this in a suitable way for JBoss5, but for JBoss 3.2,4.0 and 4.2, you need to follow the work around for this custom requirement.
> Need a way to support refreshing security roles within a session
> ----------------------------------------------------------------
>
> Key: JBAS-1802
> URL: http://jira.jboss.com/jira/browse/JBAS-1802
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.1 Final
> Reporter: Rick Wong
> Assigned To: Anil Saldhana
> Attachments: JBossGenericPrincipal.java, OccSecurityMgrRealm.java
>
>
> Currently, JBoss SX creates an instance of JBossGenericPrincipal with a fixed list of security roles obtained from JAAS LoginModule. This special principal is cached into Tomcat, and unchanged during the course of a user session. There is no trivial way to refresh security roles within a session.
> I have this need because my application has an administration interface that grants permissions to various web application. I need to have user permission changes to be reflected immediately without having current sessions to log out and then log back in to take effect.
> Unfortuately, due to the product requirement, I have to recompile JBoss and modify JBossGenericPrincipal to make it a public class. I hope to get rid of this custom change, and adopt a supported method from JBoss in the future releases.
> Please refer to forum topic
> http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63676
> Thanks a lot!
--
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
17 years, 1 month