January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JGRP-226) Remove thread which sends state response in pbcast.STATE_TRANSFER

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-226?page=all ] Bela Ban resolved JGRP-226. --------------------------- Resolution: Done done > Remove thread which sends state response in pbcast.STATE_TRANSFER > ----------------------------------------------------------------- > > Key: JGRP-226 > URL: http://jira.jboss.com/jira/browse/JGRP-226 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.2.9.1 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.5 > > > Remove the separate thread started send the state response (to avoid a deadlock) in pbcast.STATE_TRANSFER. This is in down() [GET_APPLSTATE_OK]. -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-688) Provide for message forwarding among nodes for a distributed queue.

by Ovidiu Feodorov (JIRA)

Provide for message forwarding among nodes for a distributed queue. ------------------------------------------------------------------- Key: JBMESSAGING-688 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-688 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 There is a test that fails (currently commented out) DistributedQueueTest.testForwardingMessageAmongNodes. Implement functionality and uncomment the test. -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-393) NAKACK/UNICAST: headers are removed from message when passing the message up; retransmit will fail

by Bela Ban (JIRA)

NAKACK/UNICAST: headers are removed from message when passing the message up; retransmit will fail --------------------------------------------------------------------------------------------------- Key: JGRP-393 URL: http://jira.jboss.com/jira/browse/JGRP-393 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Issue appears with UNICAST or NAKACK, example below uses NAKACK: - Message M1 is received and placed into received_msgs. M1 has a FragHeader attached (FRAG2 was somewhere above NAKACK) - M1 is retrieved from received_msgs and passed up - FRAG2 *removes* the FragHeader - A retransmission request is received for M1 - M1 is retrieved from received_msgs and passed down. Problem: the FragHeader is missing ! The receiver will not recognize M1 as a fragment and FRAG2 will *not* handle M1 ! SOLUTION 1: all protocols (maybe only the ones above UNICAST/NAKACK) should *never* remove headers. We could ensure this is the case by simply making removeHeader() a no-op SOLUTION 2: investigate into who owns the message and who is allowed to modify it. Look into sealing techniques -- 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

19 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-389) TLS: performance slow in ATL lab

by Bela Ban (JIRA)

TLS: performance slow in ATL lab -------------------------------- Key: JGRP-389 URL: http://jira.jboss.com/jira/browse/JGRP-389 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Setup: - cluster 01 and 02 - 2 members, 2 senders - send 100'000 1K messages With use_threadless_stack (and default udp.xml from distribution), we get 5600 msgs/sec. With use_threadless_stack="false", we get * 17000 msgs/sec* ! -- 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

19 years, 4 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JGRP-181) Concurrent stack

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-181?page=all ] Bela Ban resolved JGRP-181. --------------------------- Resolution: Done Documentation: section 5.5. of http://www.jgroups.org/javagroupsnew/docs/manual/html/index.html > Concurrent stack > ---------------- > > Key: JGRP-181 > URL: http://jira.jboss.com/jira/browse/JGRP-181 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.9.1, 2.2.8, 2.2.9 > Reporter: Bela Ban > Assigned To: Bela Ban > Priority: Critical > Fix For: 2.5 > > > Investigate setting all down_thread and up_thread properties to false by default > Performance tests have shown that in almost all cases this is always faster, so why not make it the default. This is e.g. already the case in fc-fast-minimalthreads.xml -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-405) Get rid of the old STATE_TRANSFER, GMS and FLUSH protocols

by Bela Ban (JIRA)

Get rid of the old STATE_TRANSFER, GMS and FLUSH protocols ---------------------------------------------------------- Key: JGRP-405 URL: http://jira.jboss.com/jira/browse/JGRP-405 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 - Get rid of these old protocols - Possibly refactor the packages, name them e.g. default, total, vsync etc -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1133) after created a new window & placed he page, the 'Preview link' in management portlet cause exception

by Boleslaw Dawidowicz (JIRA)

after created a new window & placed he page, the 'Preview link' in management portlet cause exception ----------------------------------------------------------------------------------------------------- Key: JBPORTAL-1133 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1133 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.DR1 Reporter: Boleslaw Dawidowicz Assigned To: Julien Viet Priority: Critical Fix For: 2.6.Alpha1 Also, after we have created a new window & placed it on the page, when following the 'Preview link' we receive the following error: javax.servlet.ServletException org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:405) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.lang.NullPointerException org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl.stateChanged(MaximizingStrategyImpl.java:103) org.jboss.portal.core.aspects.controller.PageNavigationInterceptor.updatePageNavigationalState(PageNavigationInterceptor.java:138) org.jboss.portal.core.controller.command.InvokeWindowRenderCommand.execute(InvokeWindowRenderCommand.java:115) org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:134) org.jboss.portal.core.aspects.controller.WindowCacheInterceptor.invoke(WindowCacheInterceptor.java:129) org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:183) org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-9) Streaming state transfer, for large states

by Vladimir Blagojevic (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-9?page=all ] Vladimir Blagojevic resolved JBCACHE-9. --------------------------------------- Resolution: Done Fix Version/s: (was: 2.1.0.GA) Fix Version/s: 2.0.0.ALPHA2 Implemented in 2.0 branch only. Streaming state transfer is completely transparent to user and cache API. User has to simply replace STATE_TRANSFER with STREAMING_STATE_TRANSFER. See JGroups documentation for details. > Streaming state transfer, for large states > ------------------------------------------- > > Key: JBCACHE-9 > URL: http://jira.jboss.com/jira/browse/JBCACHE-9 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 2.1.0.GA > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.0.0.ALPHA2 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Streaming state transfer, for large states -- 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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-675) Make client side load balancing policy pluggable

by Ovidiu Feodorov (JIRA)

Make client side load balancing policy pluggable ------------------------------------------------ Key: JBMESSAGING-675 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-675 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Make client side load balancing policy pluggable (what server is chosen when a new connection is created) -- 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

19 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-403) add support for observation

by Michael Neale (JIRA)

add support for observation --------------------------- Key: JBRULES-403 URL: http://jira.jboss.com/jira/browse/JBRULES-403 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This can be done as "hooks" so that on a resource change, an email could be sent to an interested party (perhaps even when the status changes, to allow simple workflow so when a rule is changed, the approver is notified). -- 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

19 years, 4 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007