May 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1809) Set package level attributes as defaults for rule attributes

by Greg Barton (JIRA)

Set package level attributes as defaults for rule attributes ------------------------------------------------------------ Key: JBRULES-1809 URL: https://jira.jboss.org/jira/browse/JBRULES-1809 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M2 Reporter: Greg Barton Assignee: Mark Proctor Priority: Optional Fix For: 5.0.0.M3 It would be nice if default values for rule attributes could be set at the package level. -- 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

12 years, 6 months

7
20
0 / 0

[JBoss JIRA] Created: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

by Geoffrey De Smet (JIRA)

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/jira/browse/JBRULES-2079 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.1.0.M1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator. -- 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

12 years, 6 months

6
16
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1287) SOA-P test suite failures

by Aleksandar Kostadinov (JIRA)

SOA-P test suite failures ------------------------- Key: JBMESSAGING-1287 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1287 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP01 Reporter: Aleksandar Kostadinov Assigned To: Tim Fox I'm running the JBM test suite against the binaries in the SOA-P Platform 4.2 CP01. I see 4 failures. * TEST-org.jboss.test.messaging.jms.bridge.BridgeTest-Remote-bisocket.xml. * org.jboss.test.messaging.jms.clustering.MultipleFailoverTest(Clustering).testFailoverFloodTwoServers * org.jboss.test.messaging.jms.clustering.NoFailoverTest(Clustering).testCrashNoFailover * org.jboss.test.messaging.jms.ManifestTest.testManifestEntries Failure details in here http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-JBM-testsuite/73... 3 of the failures are timeout (see console log for BridgeTest). We are running on a 2 CPU DualCore physical machine so system speed should not be an issue. -- 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

12 years, 7 months

6
30
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1491) add support for Ingres RDBMS to JBoss Messaging

by murray armfield (JIRA)

add support for Ingres RDBMS to JBoss Messaging ----------------------------------------------- Key: JBMESSAGING-1491 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1491 Project: JBoss Messaging Issue Type: Patch Affects Versions: 1.4.0.SP3.CP06, EAP/SOA-P Integration, 2.0.0 Beta, 1.4.3.GA, 2.0.0.GA, Unscheduled, AS 5.0 Integration Environment: N/A Reporter: murray armfield Assignee: Tim Fox Priority: Minor I've been working on JBoss support on Ingres. I've written an ingres-persistence-service.xml file for use with Ingres for inclusion as part of JBoss Messaging -- 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

12 years, 7 months

6
44
0 / 0

[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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 months

4
20
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2009