[JBoss JIRA] Created: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
1:39 a.m.
Resource adapter deployment fails when an authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:43 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
[
https://issues.jboss.org/browse/JBAS-8894?page=com.atlassian.jira.plugin....
]
Shelly McGowan updated JBAS-8894:
---------------------------------
Attachment: jbosstestadapter.rar
Resource adapter deployment fails when an
authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Shelly McGowan
Attachments: jbosstestadapter.rar
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:47 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
[
https://issues.jboss.org/browse/JBAS-8894?page=com.atlassian.jira.plugin....
]
Shelly McGowan updated JBAS-8894:
---------------------------------
Affects Version/s: 7.0.0.Alpha2
Resource adapter deployment fails when an
authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Alpha2
Reporter: Shelly McGowan
Attachments: jbosstestadapter.rar
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:38 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
[
https://issues.jboss.org/browse/JBAS-8894?page=com.atlassian.jira.plugin....
]
Jesper Pedersen closed JBAS-8894.
---------------------------------
Assignee: Jesper Pedersen
Resolution: Won't Fix
credential-interface is incorrect. The exception shows you the options available.
Resource adapter deployment fails when an
authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Alpha2
Reporter: Shelly McGowan
Assignee: Jesper Pedersen
Attachments: jbosstestadapter.rar
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:35 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
[
https://issues.jboss.org/browse/JBAS-8894?page=com.atlassian.jira.plugin....
]
Shelly McGowan commented on JBAS-8894:
--------------------------------------
This .rar is used with many of the org/jboss/test/jca tests in the AS 6 integration test
suite so must have been incorrect for a while:
http://svn.jboss.org/repos/jbossas/trunk/testsuite/src/resources/jca/adap...
Resource adapter deployment fails when an
authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Alpha2
Reporter: Shelly McGowan
Assignee: Jesper Pedersen
Attachments: jbosstestadapter.rar
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
[
https://issues.jboss.org/browse/JBAS-8894?page=com.atlassian.jira.plugin....
]
Jesper Pedersen commented on JBAS-8894:
---------------------------------------
There are validation errors too - even if the ra.xml is fixed:
Severity: WARNING
Section: 20.7
Description: Invalid config-property-type for ManagedConnectionFactory.
Code: Class: org.jboss.test.jca.adapter.TestManagedConnectionFactory Property: failJoin
Type: boolean
Severity: WARNING
Section: 20.7
Description: Invalid config-property-type for ManagedConnectionFactory.
Code: Class: org.jboss.test.jca.adapter.TestManagedConnectionFactory Property: UrlProperty
Type: java.net.URL
Severity: ERROR
Section: 17.5.1.1
Description: A ConnectionFactory must have a default constructor
Severity: WARNING
Section: 20.7
Description: Invalid config-property-type for ManagedConnectionFactory.
Code: Class: org.jboss.test.jca.adapter.TestManagedConnectionFactory Property: sleepInEnd
Type: long
Severity: WARNING
Section: 20.7
Description: Invalid config-property-type for ManagedConnectionFactory.
Code: Class: org.jboss.test.jca.adapter.TestManagedConnectionFactory Property:
sleepInStart Type: long
Archives from the IronJacamar distribution comply with the spec.
Resource adapter deployment fails when an
authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Alpha2
Reporter: Shelly McGowan
Assignee: Jesper Pedersen
Attachments: jbosstestadapter.rar
The the authentication-mechanism element of the ra.xml is used to specify the
authentication mechanism supported by the resource adapter. If the
authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service
jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of
deployment "jbosstestadapter.rar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to
parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of
javax.resource.spi.security.PasswordCredential;
org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at
org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at
org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at
org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4870
days inactive
4870
days old
5 comments
2 participants
participants (2)
-
Jesper Pedersen (JIRA) -
Shelly McGowan (JIRA)