January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1107) Less noisy client-side failover

by Ovidiu Feodorov (JIRA)

Less noisy client-side failover ------------------------------- Key: JBMESSAGING-1107 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Clustering Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear. If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails. Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. The logging information should be naturally still available, but at DEBUG level. -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..

by Clebert Suconic (JIRA)

Routing problem on Browsing when using mixed deliveries.. --------------------------------------------------------- Key: JBMESSAGING-1144 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP1 Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: Stable branch I believe the error is due to mixed delivery modes... but that's just a guess as I didn't have time to look at logs. I'm committing a testcase on BrowserTest for this. This testcase was reported by Carlo.. I just converted this testcase from his original test on EJB3. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1189) JBossMessaging_1_4_0_SP1 patch for JBossAS5

by Scott M Stark (JIRA)

JBossMessaging_1_4_0_SP1 patch for JBossAS5 ------------------------------------------- Key: JBMESSAGING-1189 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1189 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP1 Reporter: Scott M Stark Assigned To: Tim Fox We need a patch to JBossMessaging_1_4_0_SP1 to better integrate into the jbossas5 beta3 server. This patch addresses the issues raised in the forum: - externalize the name of the aop-messaging-server.xml so these aspects can be overriden in the server integration project. - externalize the SecurityStore implementation so this can be overriden by the server integration project. The messaging-service.xml is the corresponding update to the messaging integration version. -- 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, 6 months

3
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1216) getJMSDestination() is returning an incorrect object type after a message has been delivered.

by Phillip Thurmond (JIRA)

getJMSDestination() is returning an incorrect object type after a message has been delivered. --------------------------------------------------------------------------------------------- Key: JBMESSAGING-1216 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1216 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Phillip Thurmond Assigned To: Clebert Suconic Seems to only happen to durable messages sent to a Topic. -- 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, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1224) Bridge bug in copying JMSX properties

by Tim Fox (JIRA)

Bridge bug in copying JMSX properties ------------------------------------- Key: JBMESSAGING-1224 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1224 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.1.beta1 Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor -- 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, 6 months

1
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues

by Mike Clark (JIRA)

Closing connection does not delete associated TemporaryQueues ------------------------------------------------------------- Key: JBMESSAGING-1215 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1215 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Environment: N/A Reporter: Mike Clark Assigned To: Tim Fox When a temporary queue is created, it is not deleted on Connection.close(). This leaves the queue on the system, but unusable since only consumers that are created from the same Connection are allowed to consume from a TemporaryQueue (i.e., it is a resource leak). To reproduce, simply create a Connection, Session, and TemporaryQueue. Close the Connection and examine the Destinations attribute of the jboss.messaging:service=ServerPeer MBean. See attached code. -- 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, 6 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1205) Add SecurityBlocks on JBMExecutor

by Clebert Suconic (JIRA)

Add SecurityBlocks on JBMExecutor --------------------------------- Key: JBMESSAGING-1205 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1205 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: Stable branch JBMExecutor is doing set/get ClassLoaderOperations without a SecurityPriviledgeBlock. We should add that to avoid problems under a SecurityManager. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1135) Tart up documention for SOA-P, EAP-P

by Tim Fox (JIRA)

Tart up documention for SOA-P, EAP-P ------------------------------------ Key: JBMESSAGING-1135 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1135 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Vinu S Renish Fix For: Stable branch -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4858) SecurityDeployer changes with metadata

by Anil Saldhana (JIRA)

SecurityDeployer changes with metadata -------------------------------------- Key: JBAS-4858 URL: http://jira.jboss.com/jira/browse/JBAS-4858 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 The Security Deployer needs to be changed as per the following rant from Adrian ============================= To me this is the wrong approach anyway. There shouldn't be any code that does if (ejbdeployment) doThis(); else if (webdeployment) doThat(); else if (unknowntype) // OOPS (pun intended ;-) cantDoIt(); The webservice deployers should be working off some generic metadata that triggers them to operate. Then each type of deployment can populate that metadata to say "I want a webservice endpoint for this". This is a seperate deployer for each type we know how to map to a webservice it takes the ejb/web/other metadata and maps or bridges it to the webservice metadata. It shouldn't just be restricted to ejbs and wars. e.g. An MBean should be capable of being an endpoint if there is a deployer that creates the relevant metadata attachment from say a META-INF/jboss-webservice.xml in the sar. The security deployers take the same brain dead (non object orientated) approach. ============================================================ -- 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, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-879) SRP Authentication sometimes fails

by David Lloyd (JIRA)

SRP Authentication sometimes fails ---------------------------------- Key: JBREM-879 URL: http://jira.jboss.com/jira/browse/JBREM-879 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: Remoting 3 M1 Reporter: David Lloyd Assigned To: David Lloyd Fix For: Remoting 3 M2 The failure is sporadic. -- 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, 6 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 2008