[JBoss JIRA] (AS7-3572) Changing a DS JNDI name leads to DS that cannot be enabled
by Heiko Braun (JIRA)
Heiko Braun created AS7-3572:
--------------------------------
Summary: Changing a DS JNDI name leads to DS that cannot be enabled
Key: AS7-3572
URL: https://issues.jboss.org/browse/AS7-3572
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.0.Final
This requires some clarification: I can change the jndi name of a datasource when it's disabled. However I cannot re-enable it afterwards:
{noformat}
{
"outcome" => "failed",
"result" => {"server-groups" => {"main-server-group" => {
"7" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "JBAS010454: Data-source service [MyDS] is not available",
"rolled-back" => true
}
},
"server-one" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "JBAS010454: Data-source service [MyDS] is not available",
"rolled-back" => true
}
}
}}},
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
{noformat}
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3559) The SSLIdentityService needs to use hasDefined instead of has when obtaining the protocol.
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-3559:
-------------------------------------
Summary: The SSLIdentityService needs to use hasDefined instead of has when obtaining the protocol.
Key: AS7-3559
URL: https://issues.jboss.org/browse/AS7-3559
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Final
The following may be the result of has returning true when a protocol is not actually defined: -
17:57:33,898 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.server.controller.management.security_realm.ManagementRealm.ssl: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.ManagementRealm.ssl: JBAS015229: Unable to start service
at org.jboss.as.domain.management.security.SSLIdentityService.start(SSLIdentityService.java:96)
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$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]
Caused by: java.security.NoSuchAlgorithmException: undefined SSLContext not available
at sun.security.jca.GetInstance.getInstance(GetInstance.java:142) [:1.6.0_30]
at javax.net.ssl.SSLContext.getInstance(SSLContext.java:125) [:1.6]
at org.jboss.as.domain.management.security.SSLIdentityService.start(SSLIdentityService.java:91)
... 5 more
--
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
14 years, 2 months