December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-25) Create subprojects in security for spi, jbosssx and optional

by Anil Saldhana (JIRA)

Create subprojects in security for spi, jbosssx and optional ------------------------------------------------------------ Key: SECURITY-25 URL: http://jira.jboss.com/jira/browse/SECURITY-25 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Repository, SPI Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Currently the security project has the Security SPI as well as the JBossSX implementation in the same workspace. It is mavenized with no current capability to publish the archives into the maven repository. The "Common" project has sub projects. Along those lines, there is a need to create sub projects. This will enable us to publish artifacts to maven repository as well as make the dependencies clearer/manageable. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-152) Moving threads

by Carlo de Wolf (JIRA)

Moving threads -------------- Key: JBFORUMS-152 URL: http://jira.jboss.com/jira/browse/JBFORUMS-152 Project: JBoss Forums Issue Type: Feature Request Reporter: Carlo de Wolf Assigned To: Ryszard Kozmik Please add the capability of moving threads. (I think it's already in, so this should be easy to resolve :-) But just to be certain.) -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-843) Data versions do not replicate properly alongside data

by Manik Surtani (JIRA)

Data versions do not replicate properly alongside data ------------------------------------------------------ Key: JBCACHE-843 URL: http://jira.jboss.com/jira/browse/JBCACHE-843 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Critical Fix For: 1.4.1.GA, 2.0.0.GA In some cases, data versions are not replicated at all while in others, data versions are replicated but updating them causes problems. See org.jboss.cache.options.ExplicitVersionsReplTest in the "tests/functional" directory of Branch_JBossCache_1_4_0. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-329) Parameter annotations do not get copied across

by Kabir Khan (JIRA)

Parameter annotations do not get copied across ---------------------------------------------- Key: JBAOP-329 URL: http://jira.jboss.com/jira/browse/JBAOP-329 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2 Reporter: Kabir Khan Assigned To: Kabir Khan Modify MethodExecutionTransformer.moveAnnotations() and use the jbaop316annotationsinwrapperonly 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

17 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-714) Make sure all dependent instances of the failed connection (ConnectionFailureListener included) are propery garbage collected after failover

by Ovidiu Feodorov (JIRA)

Make sure all dependent instances of the failed connection (ConnectionFailureListener included) are propery garbage collected after failover -------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-714 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-714 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.Beta2 -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-359) Add serialVersionUID to subclasses of Swing types

by Brian Stansberry (JIRA)

Add serialVersionUID to subclasses of Swing types ------------------------------------------------- Key: JGRP-359 URL: http://jira.jboss.com/jira/browse/JGRP-359 Project: JGroups Issue Type: Sub-task Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.5 In the demos package there are number of classes that descend from Swing types and thus inherit Serializable. None of these are meant to be serialized, but we should add serialVersionUIDs just to prevent spurious failures on serialization compatibility tests. -- 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, 9 months

2
1
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

17 years, 9 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

17 years, 9 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

17 years, 9 months

1
2
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

17 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006