January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1490) BridgeService should be JAAS aware

by Nicholas Sayer (JIRA)

BridgeService should be JAAS aware ---------------------------------- Key: JBMESSAGING-1490 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1490 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.2.GA Environment: n/a Reporter: Nicholas Sayer Assignee: Tim Fox Priority: Optional org.jboss.jms.server.bridge.BridgeService currently requires a username and password for the source and destination. It would be better if it could be configured with a JAAS login context name. This would allow username and password information to be set in, for example, a SecureIdentityLoginModule. For example: <application-policy name = "JmsBridgeRealm"> <authentication> <login-module code = "org.jboss.resource.security.SecureIdentityLoginModule" flag = "required"> <module-option name = "principal">${bridge.user}</module-option> <module-option name = "userName">${bridge.user}</module-option> <module-option name = "password">${bridge.encryptedPassword}</module-option> <module-option name = "ignoreMissigingMCF">true</module-option>  <module-option name = "managedConnectionFactoryName">jboss.nonexistent:service=NonExistent,name=NonExistent</module-option> </login-module> </authentication> </application-policy> There is undoubtedly a better way to accomplish this (probably to pass the JAAS context directly into the JMS connection factory used to vend connections for the bridge), but we're using this as a crude hack for now: import java.util.Set; import javax.security.auth.Subject; import javax.security.auth.login.LoginContext; import javax.security.auth.login.LoginException; import javax.security.auth.login.CredentialNotFoundException; import javax.resource.spi.security.PasswordCredential; import org.jboss.jms.server.bridge.BridgeService; public class JAASAwareBridgeService extends BridgeService { private String sourceContext, targetContext; public void setSourceLoginContext(String ctxName) { this.sourceContext = ctxName; } public String getSourceLoginContext() { return this.sourceContext; } public void setTargetLoginContext(String ctxName) { this.targetContext = ctxName; } public String getTargetLoginContext() { return this.targetContext; } public void start() throws Exception { setupSourceCredentials(); setupTargetCredentials(); super.start(); } private void setupSourceCredentials() throws LoginException { PasswordCredential pc = getPasswordCredential(this.sourceContext); super.setSourceUsername(pc.getUserName()); super.setSourcePassword(new String(pc.getPassword())); } private void setupTargetCredentials() throws LoginException { PasswordCredential pc = getPasswordCredential(this.targetContext); super.setTargetUsername(pc.getUserName()); super.setTargetPassword(new String(pc.getPassword())); } private static PasswordCredential getPasswordCredential(String contextName) throws LoginException { LoginContext ctx = new LoginContext(contextName); ctx.login(); Subject s = ctx.getSubject(); Set<PasswordCredential> creds = s.getPrivateCredentials(PasswordCredential.class); if (creds.isEmpty()) throw new CredentialNotFoundException("Login context '" + contextName + "' subject has no PasswordCredential"); return creds.iterator().next(); // get 1st } } -- 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

11 years, 12 months

4
21
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1478) inconsistent test suite performance

by Aleksandar Kostadinov (JIRA)

inconsistent test suite performance ----------------------------------- Key: JBMESSAGING-1478 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1478 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.4.0.SP3.CP04 Reporter: Aleksandar Kostadinov Assignee: Tim Fox I see inconsistent performance running the JBM test suite. Here I have 2 builds on the same physical machine (windows), using local disk storage so environment should be pretty stable. The mysql database is shared but I doubt it is the culprit. I run the test suite with the following options: property( name: "functional.tests.database", value: dbname ) property( name: "stress.tests.database", value: dbname ) property( name: "clustering.tests.database", value: dbname ) property( name: "test.target", value: "report" ) property( name: "test.bind.address", value: properties["env.MYTESTIP_1"] ) property( name: "jboss.messaging.groupname", value: properties["env.BUILD_TAG"]) property( name: "jboss.messaging.datachanneludpaddress", value: properties["env.MCAST_ADDR"] ) property( name: "jboss.messaging.controlchanneludpaddress", value: properties["env.MCAST_ADDR"] ) Are there any other options I can add to increase isolation from other processes in the same LAN? Would you be able to look at these 2 builds and based on the logs, say why is the first one taking longer and eventually timeout? http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbm/163/ http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbm/164/ -- 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

11 years, 12 months

4
24
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1401) Unverified: Restarting a Queue will delete persistent messages in the queue.

by Jay Howell (JIRA)

Unverified: Restarting a Queue will delete persistent messages in the queue. ---------------------------------------------------------------------------- Key: JBMESSAGING-1401 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1401 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Jay Howell Assignee: Tim Fox Restarting a queue in a running server will delete persistent messages out of the database. This bug was found while troubleshooting a case. When a customer restarted the queues, they noticed that all of the persistent messages in the database were gone. I have yet to verify this and will verify as soon as possible. I wanted to make sure that I didn't forget to put it in. So at this point this is an unverified bug. -- 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

11 years, 12 months

5
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1594) Provide support for a List of Strings (in StreamMessage) with a size > 64K

by Colin Mondesir (JIRA)

Provide support for a List of Strings (in StreamMessage) with a size > 64K -------------------------------------------------------------------------- Key: JBMESSAGING-1594 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1594 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.0.SP3 Reporter: Colin Mondesir Assignee: Tim Fox Looking at the code, there is support for 'longstring' for java.lang.String. But that doesn't happen for a List of Strings. -- 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

11 years, 12 months

4
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1517) Malformed HTTP POST from Post Office management page in JMX Console

by Paul Kaiser (JIRA)

Malformed HTTP POST from Post Office management page in JMX Console ------------------------------------------------------------------- Key: JBMESSAGING-1517 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1517 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP03 Environment: All Reporter: Paul Kaiser Assignee: Tim Fox When trying to submit changes to the configuration of the Messaging Post Office from the JMX Console interface, the improper quoting of configuration strings results in an improper HTTP POST. This prevents the submission of any updates to the component. -- 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

11 years, 12 months

4
24
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1513) Database maintenance scripts

by Len DiMaggio (JIRA)

Database maintenance scripts ---------------------------- Key: JBMESSAGING-1513 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1513 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: 1.4.2.GA.SP1 Reporter: Len DiMaggio Assignee: Tim Fox Project JIRA for SOA-P platform JIRA: https://jira.jboss.org/jira/browse/SOA-310 -- 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

11 years, 12 months

4
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1615) Programmatic to check the state of a topic

by Colin Mondesir (JIRA)

Programmatic to check the state of a topic ------------------------------------------ Key: JBMESSAGING-1615 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1615 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.1.GA Reporter: Colin Mondesir Assignee: Howard Gao Priority: Minor When the deployTopic(String, String) method is called we have found there is a slight delay before the topic is available to create MessageConsumer. Is there a programmatic way of checking the state that the topic is in, so that we don't have to wait an arbitrary period of time before creating the Consumer? -- 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

11 years, 12 months

5
22
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1610) expose jbossInternalLifecycle method on jms destination mbeans

by Emanuel Muckenhuber (JIRA)

expose jbossInternalLifecycle method on jms destination mbeans -------------------------------------------------------------- Key: JBMESSAGING-1610 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1610 Project: JBoss Messaging Issue Type: Task Components: AS Integration Affects Versions: 1.4.3.GA Reporter: Emanuel Muckenhuber Assignee: Tim Fox Currently the Queue and Topic xmbean definitions don't expose the jbossInternalLifecycle(String method). This method is needed that the lifecycle and state changes of a mbean are handled by microcontainer (AS5). Otherwise profileservice cannot determine the current state and a stopped jms destination would be still exposed as running to JON/JOPR. -- 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

11 years, 12 months

4
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1619) add example TCP cluster configuration

by Dennis Reed (JIRA)

add example TCP cluster configuration ------------------------------------- Key: JBMESSAGING-1619 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1619 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP07 Reporter: Dennis Reed Assignee: Tim Fox Add an example TCP cluster configuration (commented out) to all the example *-persistence-service.xml files. This will make it easier for users who have issues with UDP multicast to configure it to use TCP clustering. (The same thing is being done to all the EAP configurations that don't already include this). -- 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

11 years, 12 months

4
22
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1648) Bridge may stop working after long time idle

by Howard Gao (JIRA)

Bridge may stop working after long time idle -------------------------------------------- Key: JBMESSAGING-1648 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1648 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.3.GA Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.5.GA Bridge service may stop working after a long time idle -- 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

11 years, 12 months

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010