[JBoss JIRA] Created: (AS7-1931) Unable to configure more than one pooled-connection-factory in the messaging subsystem
by Vincent MATHON (JIRA)
Unable to configure more than one pooled-connection-factory in the messaging subsystem
--------------------------------------------------------------------------------------
Key: AS7-1931
URL: https://issues.jboss.org/browse/AS7-1931
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.2.Final, 7.0.1.Final, 7.0.0.Final
Environment: Windows7, sun jdk 1.6_25
Reporter: Vincent MATHON
Adding another pooled connection factory in the standalone-preview.xml file provided by any of the 7.0.x.Final releases as follow
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
</pooled-connection-factory>
<pooled-connection-factory name="hornetq-ra-nonxa">
<transaction mode="local"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsNonXA"/>
</entries>
</pooled-connection-factory>
leads to the following exception:
12:44:31,621 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: org.jboss.msc.service.StartException in service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: failed to create resource adapter
at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:174)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.raactivator is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:232)
at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:172)
... 5 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-2267) The Console logs the DMR commands
by Rich Raposa (Created) (JIRA)
The Console logs the DMR commands
---------------------------------
Key: AS7-2267
URL: https://issues.jboss.org/browse/AS7-2267
Project: Application Server 7
Issue Type: Feature Request
Reporter: Rich Raposa
It would be nice if changes made to the configuration file via the Console were logged in DMR format so that the commands could be executed as a CLI script.
A simpler option would be to provide a link next to a resource that shows the CLI command you would use to create that resource. For example, in the list of datasources on the Datasources Configuration tab, next to each datasource would be a link that would contain the CLI command for defining that datasource.
The use case is this: I can take advantage of the ease-of-use of the Console to define a resource, then copy-and-paste the CLI command to define a script so that the resource can be defined over and over again on all of my EAP deployments.
--
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, 6 months
[JBoss JIRA] Created: (AS7-1913) Add script to simplify creating the password hashes
by Darran Lofthouse (JIRA)
Add script to simplify creating the password hashes
---------------------------------------------------
Key: AS7-1913
URL: https://issues.jboss.org/browse/AS7-1913
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management, Security
Environment:
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
When enabling pre-digested passwords administrators will require a way to generate the hashes, generation is simple however we should also publish a script so they don't need to spend time setting up their own generation if they don't need to.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1838) Add support for pre-digested passwords to AS7 domain realms
by Darran Lofthouse (JIRA)
Add support for pre-digested passwords to AS7 domain realms
-----------------------------------------------------------
Key: AS7-1838
URL: https://issues.jboss.org/browse/AS7-1838
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
Storing plain text passwords means that should the file containing these passwords be compromised not only could the passwords be used to access the AS instance they were using the passwords could potentially be used for any systems secured with the same passwords.
The pre-digested passwords will be digested with the username, password and realm - this will mean that although they still need to be kept secure to prevent access to the AS instance they secure they will not be useful for gaining access to different systems secured with different realms.
(As backwards compatibility is to be retained AS 7.0.2 will have this feature switched off by default leaving the end user to choose to switch it on - for AS 7.1.0 this will be reversed making it the default for out of the box)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months