August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1335) Network disconnect reconnect testing

by Tim Fox (JIRA)

Network disconnect reconnect testing ------------------------------------ Key: JBMESSAGING-1335 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1335 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We need to do full network disconnect reconnect testing with JBM2.0. For bridge, for split brain 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

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-211) Destination programmatic deployment example/integration test

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-211?page=com.atlassian.jir... ] Tim Fox updated JBMESSAGING-211: -------------------------------- Fix Version/s: 2.0.0.beta5-tmp (was: 2.0.0.beta5) > Destination programmatic deployment example/integration test > ------------------------------------------------------------ > > Key: JBMESSAGING-211 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-211 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Optional > Fix For: 2.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Write the corresponing docs/example/programmatic-deployment integration test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1666) Add "messageCount" attribute on Address MBean

by Bijith Kumar (JIRA)

Add "messageCount" attribute on Address MBean --------------------------------------------- Key: JBMESSAGING-1666 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1666 Project: JBoss Messaging Issue Type: Feature Request Reporter: Bijith Kumar Assignee: Tim Fox Value shown in "messageCount" attribute of a queue MBean does not include the number of messages that are paged. This is because messages are paged to disk before they are routed in the postoffice. So, for the user to be able to find the total number of messages that are added to a queue, Tim suggested that, we add a "messageCount" attribute to the Address MBean. That would indicate how many messages are paged for a particular destination address. Please refer http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157325 for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1556) Add additional core management notifications

by Jeff Mesnil (JIRA)

Add additional core management notifications -------------------------------------------- Key: JBMESSAGING-1556 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1556 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Reporter: Jeff Mesnil Assignee: Tim Fox Fix For: 2.0.0.CR1 Add additional management notifications for the following events in JBM server: 1/ notifications for start/stop of some messaging component: - ACCEPTOR_STARTED / ACCEPTOR_STOPPED - BRIDGE_STARTED / BRIDGE_STOPPED - BROADCAST_GROUP_STARTED / BROADCAST_GROUP_STOPPED - CLUSTER_CONNECTION_STARTED / CLUSTER_CONNECTION_STOPPED - DISCOVERY_GROUP_STARTED / DISCOVERY_GROUP_STOPPED 2/ I was also thinking to add notifications when messages are expired/moved to the dead letter address but I'm not sure these notifications should be enabled by default (they can potentially generate a lot of notifications): EXPIRED_MESSAGE -> when a message is expired MOVED_TO_DEAD_LETTER_ADDRESS -> when a message is moved to the DLA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1194) Investigate quorum for mitigating split brain

by Tim Fox (JIRA)

Investigate quorum for mitigating split brain --------------------------------------------- Key: JBMESSAGING-1194 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1194 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta -- 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

15 years, 3 months

4
8
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-377) Competing consumer on subscriptions

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-377?page=com.atlassian.jir... ] Tim Fox updated JBMESSAGING-377: -------------------------------- Fix Version/s: 2.0.0.beta5-tmp (was: 2.0.0.beta5) > Competing consumer on subscriptions > ----------------------------------- > > Key: JBMESSAGING-377 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-377 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assignee: Tim Fox > Priority: Minor > Fix For: 2.0.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1882) Bring in the fixes for EJBTHREE-1738, in the plugin

by jaikiran pai (JIRA)

Bring in the fixes for EJBTHREE-1738, in the plugin --------------------------------------------------- Key: EJBTHREE-1882 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1882 Project: EJB 3.0 Issue Type: Task Components: plugin Reporter: jaikiran pai Assignee: jaikiran pai Include the fixes done in EJBTHREE-1738, in the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6543) @RunAs no longer works on @Service beans

by Jeff Schnitzer (JIRA)

@RunAs no longer works on @Service beans ---------------------------------------- Key: JBAS-6543 URL: https://jira.jboss.org/jira/browse/JBAS-6543 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.1.GA Reporter: Jeff Schnitzer Assignee: Carlo de Wolf The behavior of security domains on @Service beans has changed from 4.2 to 5.0.1. @RunAs no longer works. This seems to make it impossible for a @Service to call a secured bean. Take two @Services, one ClientService and one ServerService. Here's the ServerService, note that it requires the "admin" role: @Service(objectName="test:service=Server") @SecurityDomain("foo") @RolesAllowed("admin") public class ServerService implements ServerManagement, Server { public void serve() {...} } The client tries to call the server: @Service(objectName="test:service=Client") @SecurityDomain("foo") @RunAs("admin") public class ClientService implements ClientManagement { @EJB Server server; public void start() { server.serve(); } } This generates exceptions "No security context set". Alternatively, if the Server is a stateless session ejb, the exception is "Caller unauthorized". This same code works in 4.2. If it will help I can attach a simple test project but since the error occurs on deployment (service start), I don't know how to create a unit test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBBOOT-105) JMX notification not sent until after shutdown is complete

by Paul Ferraro (JIRA)

JMX notification not sent until after shutdown is complete ---------------------------------------------------------- Key: JBBOOT-105 URL: https://jira.jboss.org/jira/browse/JBBOOT-105 Project: JBoss Bootstrap Issue Type: Bug Components: impl-base Affects Versions: impl-base-2.0.0-alpha-3 Reporter: Paul Ferraro Assignee: Andrew Lee Rubinger In bootstrap 1.0.x, and in the legacy implementation, the org.jboss.system.server.stopped JMX notification was sent prior to the shutdown of the server. The AS TomcatService relies on this mechanism to stop its http/ajp connectors before stopping the service, along with any deployed web applications. In 2.0.0-alpha-3, however, this notification is not sent until after shutdown is complete. Consequently, the http/ajp connectors are not getting stopped until after all web applications are undeployed. It is now possible for a web request to reach the connectors before they are stopped, but after the requested web application was already undeployed, causing a 404 (page not found) error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1881) Service Proxy Factory not uninstalled

by Andrew Lee Rubinger (JIRA)

Service Proxy Factory not uninstalled ------------------------------------- Key: EJBTHREE-1881 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1881 Project: EJB 3.0 Issue Type: Bug Components: proxy-impl Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger When redeploying a @Service (that had previously failed during start()): Caused by: org.jboss.ejb3.common.registrar.spi.DuplicateBindException: Cannot install org.jboss.ejb3.proxy.impl.factory.session.service.ServiceRemoteProxyFactory@4cc4ee24 under name "ProxyFactory/ejbthree1738/RunAsService/RunAs/remote" as there is already an existing object there: org.jboss.ejb3.proxy.impl.factory.session.service.ServiceRemoteProxyFactory@4c6cb02a Note that an explicit jndiBinding has been provided. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2009