July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1133) MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services

by David Bosschaert (JIRA)

MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services ----------------------------------------------------------------------------------------------------- Key: AS7-1133 URL: https://issues.jboss.org/browse/AS7-1133 Project: Application Server 7 Issue Type: Bug Components: MSC, Web Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Minor When deploying a .war file that contains a META-INF/service/org.jboss.msc.service.ServiceActivator this file is only processed when it's in the WEB-INF/classes/META-INF/services location, where I think it should really be picked up fro /META-INF/services -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8824) Cardinality constraints on children are not enforced after parsing

by Brian Stansberry (JIRA)

Cardinality constraints on children are not enforced after parsing ------------------------------------------------------------------ Key: JBAS-8824 URL: https://issues.jboss.org/browse/JBAS-8824 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta1 The parsers enforce cardinality constraints on child elements in the model, but they aren't enforced thereafter. So, for example, a second "profile" or "socket-binding-group" could be added to a standalone server via a management operation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-1317) STABLE: compress STABLE messages

by Bela Ban (JIRA)

STABLE: compress STABLE messages -------------------------------- Key: JGRP-1317 URL: https://issues.jboss.org/browse/JGRP-1317 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12.2, 3.1 For large clusters, stable messages are quite large, and should be compressed. E.g.: - Don't send the entire view (with all members), but only the ViewId, then the indices of a digest array would point to the rank of a member within the referred-to ViewId - A digest has 3 longs (low, highest_received and highest_delivered). Do we need all 3 every time ? - Compress the 3 longs into 1 long and 2 shorts: the latter 2 are offsets from the first seqno - Use a bit set (consisting of a variable number of ints) to set the 3 variables - If we have a digest (0), 0, 0: send a special marker - Canonicalize digests: if everyone has (14) 20, 22, then we could write it once, give it an ID of (say) 1 and then only refer to 1 again if we encounter the same digest. Actually, as a matter of fact, most of the digests would be the same, so this optimization could have a big effect ! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (JGRP-1052) Ergonomics

by Bela Ban (JIRA)

Ergonomics ---------- Key: JGRP-1052 URL: https://jira.jboss.org/jira/browse/JGRP-1052 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 The goal is to (a) reduce the number of properties needed and (b) determine the values dynamically. Examples: - Determine the best min/max size of a thread pool - Find out what the best timeout values are for retransmission, e.g. based on average retransmission times - Determine the optimal number of credits in FC This is similar to the JVM setting where, starting with 1.5, the initial values can be set, but over time, the JVM dynamically changes them. In the best case, a config contains only a list of protocols without any properties, and JGroups will figure out the correct values. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2438) loading multiple sheets of single Excel book by one change-set xml

by Toshiya Kobayashi (JIRA)

loading multiple sheets of single Excel book by one change-set xml ------------------------------------------------------------------ Key: JBRULES-2438 URL: https://jira.jboss.org/jira/browse/JBRULES-2438 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Toshiya Kobayashi Assignee: Mark Proctor I'm trying to use rules via DecisionTable using change-set. I wrote rules in multiple sheets of single Excel book. Then I configured my change-set xml like: ... <add> <resource source='classpath:data/dtable.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="sheet1" /> </resource> <resource source='classpath:data/dtable.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="sheet2" /> </resource> </add> ... But only rules of sheet1 were loaded. As far as I observed source codes, KnowledgeAgentImpl.java puts resource into "Map<Resource, ResourceMapping> resources". But even if multiple resources are configured in change-set, it appears to me like those resources are considered as the same resource and eventually only one resource will be registered. -- 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, 2 months

4
22
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, 2 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, 2 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, 2 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, 2 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, 2 months

5
20
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011