[JBoss JIRA] Created: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
by Juergen Zimmermann (JIRA)
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
I'm having 2 different EARs and stateless session beans of the 2nd EAR are referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
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
15 years, 2 months
[JBoss JIRA] Created: (EJBTHREE-1429) SFSB replication soak testing
by Brian Stansberry (JIRA)
SFSB replication soak testing
-----------------------------
Key: EJBTHREE-1429
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1429
Project: EJB 3.0
Issue Type: Task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 5.0.0.CR2
Long running tests of SFSB replication under heavy load.
Should include:
1) Letting a significant percentage of sessions passivate and later activate.
2) Letting a significant percentage of sessions expire due to time out.
3) Invalidating remaining sessions after a while (i.e. don't use any sessions for the life of test; all get used and replaced after a while).
4) Perhaps, a low (say 1/1000) probability of failover.
--
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
15 years, 3 months
[JBoss JIRA] Created: (SECURITY-344) Error decrypting datasource password with SecureIdentityLoginModule
by Marcus Moyses (JIRA)
Error decrypting datasource password with SecureIdentityLoginModule
-------------------------------------------------------------------
Key: SECURITY-344
URL: https://jira.jboss.org/jira/browse/SECURITY-344
Project: JBoss Security and Identity Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0.2.SP3
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Fix For: 2.0.2.SP5
During password decryption using SecureIdentityLoginModule there could be an error due to missing leading zeros for certain passwords.
This error might appear in the log:
[SecureIdentityLoginModule] Failed to decode password
javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
at javax.crypto.Cipher.doFinal(DashoA12275)
at org.jboss.resource.security.SecureIdentityLoginModule.decode(SecureIdentityLoginModule.java:173)
at org.jboss.resource.security.SecureIdentityLoginModule.commit(SecureIdentityLoginModule.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
--
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
15 years, 3 months
[JBoss JIRA] Created: (JBAS-4078) DeploymentManager.getAvailableModules() returns null
by Libor Kotouc (JIRA)
DeploymentManager.getAvailableModules() returns null
----------------------------------------------------
Key: JBAS-4078
URL: http://jira.jboss.com/jira/browse/JBAS-4078
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08
Reporter: Libor Kotouc
Assigned To: Dimitris Andreadis
Priority: Critical
This issue blocks an integration of JBoss AS 5 into NetBeans IDE.
Steps to reproduce the behavior:
1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server)
2. start JBoss server (./run.sh)
3. run the following code from a J2SE application (I added JBoss jars to the classpath):
public class Main {
public static void main(String[] args) {
try {
javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl();
javax.enterprise.deploy.spi.DeploymentManager dm;
dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null);
javax.enterprise.deploy.spi.Target[] targets = dm.getTargets();
javax.enterprise.deploy.spi.TargetModuleID[] modules;
modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets);
System.out.println(targets.length + " " + targets[0]);
System.out.println(modules);
} catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) {
} catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) {
}
}
}
The output of System.out.println statements is:
1 org.jboss.deployment.spi.JMXTarget@161d36b
null
I expect the module representing the web application, but null is returned.
--
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
15 years, 3 months