[JBoss JIRA] Created: (JBAS-3704) Add a notion of available interfaces to org.jboss.test.util.server.*
by Scott M Stark (JIRA)
Add a notion of available interfaces to org.jboss.test.util.server.*
--------------------------------------------------------------------
Key: JBAS-3704
URL: http://jira.jboss.com/jira/browse/JBAS-3704
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.4.GA
Reporter: Scott M Stark
Fix For: JBossAS-4.0.6.CR1
An issue with automating testing involving binding to specific addresses is that there is no predefined set of properties a testsuite descriptor can reference. The qa env has MYTESTIP_1 type of env vars set, and java 1.4.2+ has java.net.NetworkInterface, that could be used as the basis for defining jboss.server.iface.0..N system properties that configurations could rely on for setting one or more bind interfaces.
We need to add this functionality to the server startup tasks.
--
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
[JBoss JIRA] Created: (EJBTHREE-761) SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
by John Gilbert (JIRA)
SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
-------------------------------------------------------------------------------------
Key: EJBTHREE-761
URL: http://jira.jboss.com/jira/browse/EJBTHREE-761
Project: EJB 3.0
Issue Type: Patch
Components: Security
Affects Versions: EJB 3.0 RC8 - FD
Reporter: John Gilbert
The exception happens in org.jboss.security.plugins.JaasSecurityManager.getPrincipal(Principal principal) when it is synchronized on domainCache. domainCache is null because org.jboss.ejb3.embedded.JaasSecurityManagerService does not initialize it.
There are two possible fixes:
1 - org.jboss.security.plugins.JaasSecurityManager should check for null first like it does in most of the methods.
2 - have org.jboss.ejb3.embedded.JaasSecurityManagerService initialize the cache with a mock cache policy. This is what I did to fix mine.
private static JaasSecurityManager getSecurityManager(String name) {
...
manager = new JaasSecurityManager(name,
new SecurityAssociationHandler());
manager.setCachePolicy(new MockCachePolicy()); //MockCachePolicy is just a noop impl
...
}
--
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
[JBoss JIRA] Created: (JBMESSAGING-553) Run AS (4.x and 5.x) integration tests with Messaging
by Ovidiu Feodorov (JIRA)
Run AS (4.x and 5.x) integration tests with Messaging
-----------------------------------------------------
Key: JBMESSAGING-553
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-553
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Richard Achmatowicz
Priority: Critical
Fix For: 1.2.0.Beta1
This is the container task for everthing required to run JBoss AS JMS integration tests with JBoss Messaging. The existing integration test framework should be modified in such a manner to allow interchangeably running the same JMS tests with JBossMQ and JBoss Messaging. None of the existing JBossMQ tests should be removed, they must be at most refactored so the JBossMQ-specific tests will be executed with JBossMQ only (as part of the JBossMQ functional testsuite) and generic JMS tests will be executed with both JBossMQ and JBoss Messaging.
More details in the sub-tasks.
--
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, 7 months