[JBoss JIRA] Created: (JBMESSAGING-625) ClassCastException String to ManagedDestination
by ya xiang (JIRA)
ClassCastException String to ManagedDestination
-----------------------------------------------
Key: JBMESSAGING-625
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-625
Project: JBoss Messaging
Issue Type: Patch
Components: Messaging Core
Affects Versions: 1.2.0.Alpha1
Reporter: ya xiang
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Alpha2, 1.2.0.Alpha1
in code :/trunk/src/main/org/jboss/jms/server/DestinationJNDIMapper.java
there are two type errors.
maybe it should be:
263 Set queues=new HashSet(queueMap.values());
265 Set topics = new HashSet(topicMap.values());
source code as follows:
67 // Map <name , destination holder>
68 private Map queueMap;
69 private Map topicMap;
261 public void stop() throws Exception
262 {
263 Set queues = new HashSet(queueMap.keySet());
264
265 Set topics = new HashSet(topicMap.keySet());
266
267 // remove all destinations from JNDI
268 for(Iterator i = queues.iterator(); i.hasNext(); )
269 {
270 unregisterDestination((ManagedDestination)i.next());
271 }
272
273 for(Iterator i = topics.iterator(); i.hasNext(); )
274 {
275 unregisterDestination((ManagedDestination)i.next());
276 }
277
278 initialContext.unbind(serverPeer.getDefaultQueueJNDIContext());
279 initialContext.unbind(serverPeer.getDefaultTopicJNDIContext());
280
281 initialContext.close();
282 }
--
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
18 years, 2 months
[JBoss JIRA] Resolved: (JBPORTAL-585) Sorting and Localization for Navigation Portlet
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-585?page=all ]
Roy Russo resolved JBPORTAL-585.
--------------------------------
Resolution: Done
> Sorting and Localization for Navigation Portlet
> -----------------------------------------------
>
> Key: JBPORTAL-585
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-585
> Project: JBoss Portal
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2 Final, 2.4 Final
> Reporter: Doug Schnelzer
> Assigned To: Roy Russo
> Fix For: 2.6.Alpha1, 2.6 Final
>
> Attachments: default-object.xml, NavigationPortlet.java, Resource.properties
>
>
> The navigation portlet currently only supports sorting by the page name. This patch adds support for sorting by a Declared Property named "order" in the -objects.xml. This patch also supports using a resource properties file for looking up page labels. The Declared Property name for the resource properties file key is "resourceKey". An example -object.xml file is attached. The relevant section is:
> <page>
> <page-name>default</page-name>
> <properties>
> <property>
> <name>order</name>
> <value>1</value>
> </property>
> <property>
> <name>resourceKey</name>
> <value>home</value>
> </property>
> </properties>
> ...
--
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
18 years, 2 months
[JBoss JIRA] Reopened: (JBPORTAL-585) Sorting and Localization for Navigation Portlet
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-585?page=all ]
Roy Russo reopened JBPORTAL-585:
--------------------------------
Add to 2.6Alpha1
> Sorting and Localization for Navigation Portlet
> -----------------------------------------------
>
> Key: JBPORTAL-585
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-585
> Project: JBoss Portal
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2 Final, 2.4 Final
> Reporter: Doug Schnelzer
> Assigned To: Roy Russo
> Fix For: 2.6 Final, 2.6.Alpha1
>
> Attachments: default-object.xml, NavigationPortlet.java, Resource.properties
>
>
> The navigation portlet currently only supports sorting by the page name. This patch adds support for sorting by a Declared Property named "order" in the -objects.xml. This patch also supports using a resource properties file for looking up page labels. The Declared Property name for the resource properties file key is "resourceKey". An example -object.xml file is attached. The relevant section is:
> <page>
> <page-name>default</page-name>
> <properties>
> <property>
> <name>order</name>
> <value>1</value>
> </property>
> <property>
> <name>resourceKey</name>
> <value>home</value>
> </property>
> </properties>
> ...
--
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
18 years, 2 months
[JBoss JIRA] Commented: (JBMESSAGING-355) Remove possibility of delivery race conditions
by Tim Fox (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-355:
-------------------------------------
I believe I have already fixed this in TRUNK - the change should be ported from TRUNK to Branch_1_0.
BTW This bug report is not the same issue as the original issue of this JIRA task - so should really be in a different task.
> Remove possibility of delivery race conditions
> ----------------------------------------------
>
> Key: JBMESSAGING-355
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 1.0.2.CR1
>
> Attachments: race-condition.log
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Currently race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned.
> In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring.
> See ChannelSupport::deliver() and ChannelState.cancelDelivery.
> This approach has the following problems:
> Complexity of code to maintain and understand.
> Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput.
> A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention.
> This can be done by adding a confirm() method on Delivery.
> When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in.
> This is a very simple change.
--
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
18 years, 2 months