[JBoss JIRA] (AS7-5501) AS7 allows use of weak ciphers for management console https
by R Stokoe (JIRA)
R Stokoe created AS7-5501:
-----------------------------
Summary: AS7 allows use of weak ciphers for management console https
Key: AS7-5501
URL: https://issues.jboss.org/browse/AS7-5501
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: R Stokoe
Assignee: Anil Saldhana
This is a security vulnerability.
Default accepted ciphers should be stronger or method should be provided to specify allowed ciphers as with the web subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5934) RAR inside EAR: deployment issues
by Marcel Šebek (JIRA)
Marcel Šebek created AS7-5934:
---------------------------------
Summary: RAR inside EAR: deployment issues
Key: AS7-5934
URL: https://issues.jboss.org/browse/AS7-5934
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.4.Final (EAP)
Reporter: Marcel Šebek
Assignee: Jesper Pedersen
I'm having troubles with deploying inbound RARs inside EARs. For example, the test ear attached to AS7-5471 is sometimes deployed successfully and sometimes not, it seems that the probability does not depend on the fact whether it is the first deployment or redeployment. The exception is:
[org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "test-rar-2.0.0-SNAPSHOT.rar" of deployment "test-ear.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:182)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:351)
at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:332)
at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:139)
... 6 more
A bigger project with MDB and @ResourceAdapter annotation sometimes fails (and sometimes not) with the following exception:
[org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."adapter-snmp-ear.ear"."adapter-snmp-ejb.jar".component.InboundMDB.CREATE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."adapter-snmp-ear.ear"."adapter-snmp-ejb.jar".component.InboundMDB.CREATE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: java.lang.IllegalStateException: JBAS014331: No resource adapter registered with resource adapter name adapter-snmp-ear.ear#adapter-snmp-rar
at org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:83)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:89)
at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:91)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.start(MessageDrivenComponentCreateService.java:76)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBRULES-3693) Pull Request to update smooks to 1.5.1
by George Varsamis (JIRA)
George Varsamis created JBRULES-3693:
----------------------------------------
Summary: Pull Request to update smooks to 1.5.1
Key: JBRULES-3693
URL: https://issues.jboss.org/browse/JBRULES-3693
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Alpha1
Reporter: George Varsamis
Assignee: Mark Proctor
Switchyard requires Smooks v 1.5.1 . I have updated drools parent to use smooks 1.5.1 and also updated the source code in droolsjbpm-integration/drools-pipeline to reflect this. The change is trivial. I have run the tests and the change had no adverse effect on the codebase.
I will attach the pull requests to this ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JGRP-1410) globalThreadGroup not destroyed creates a classloader memory leak
by Jean-Philippe Gariepy (Created) (JIRA)
globalThreadGroup not destroyed creates a classloader memory leak
-----------------------------------------------------------------
Key: JGRP-1410
URL: https://issues.jboss.org/browse/JGRP-1410
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.1
Environment: linux w/ java 1.6
Reporter: Jean-Philippe Gariepy
Assignee: Bela Ban
When all channels are closed, the globalThreadGroup is not destroyed. For a normal (i.e. non-web) application, this is not a problem since the process will exit anyway. However, for a Java Enterprise web application, this causes a classloader memory leak since the ThreadGroup object has strong references to JGroups instances having strong references to their class object having strong reference to their class loader. Since the class loader is pointed by strong references, the it cannot be garbage collected and hence a leak is created each time the web application is stopped.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5974) Persistent @Schedule timers are not removed if the persistent attribute change
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-5974:
-------------------------------------
Summary: Persistent @Schedule timers are not removed if the persistent attribute change
Key: AS7-5974
URL: https://issues.jboss.org/browse/AS7-5974
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.2.0.Alpha1
Reporter: Wolf-Dieter Fink
Assignee: jaikiran pai
If a EJB (Stateless) is deployed with a @Schedule annotation which is persistent the timer will not be removed if it is redeployed and the only change is the persistent flag.
If the time schedule is changed in the same deploment the timer will be removed from the store.
There is no difference for managed or unmanaged deployments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5655) Cannot restart ejb3 bundle after activation failure
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5655:
-----------------------------------
Summary: Cannot restart ejb3 bundle after activation failure
Key: AS7-5655
URL: https://issues.jboss.org/browse/AS7-5655
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
{code}
Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence
at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225)
at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117)
at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month