Bug 1467697 - Unable to deploy xa-datasource (postgres driver) over ssl
Unable to deploy xa-datasource (postgres driver) over ssl
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: jbossas (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: jboss-set
Peter Mackay
Depends On:
  Show dependency treegraph
Reported: 2017-07-04 12:18 EDT by Abhi
Modified: 2017-07-04 12:18 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.8 Build Name: 8740, Administration and Configuration Guide-6-3 Build Date: 05-04-2013 09:18:51
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Abhi 2017-07-04 12:18:27 EDT
Title: SSL on PostgreSQL XA Datasource

Describe the issue:

Following configuration was used:

 <xa-datasource jndi-name="java:jboss/datasources/jbpmDS" pool-name="JBPMDS" enabled="true" use-ccm="false">
                    <xa-datasource-property name="databaseName">
                    <xa-datasource-property name="serverName">
                    <xa-datasource-property name="portNumber">
                    <xa-datasource-property name="Ssl">
                    <xa-datasource-property name="trustServerCertificate">
                    <xa-datasource-property name="trustStore">
                        <check-valid-connection-sql>select 1</check-valid-connection-sql>

Suggestions for improvement:

Additional information:
Please advise.
Setup not working.

Following is the error:

Internal Server Error
    "outcome" => "failed",
    "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName: java:jboss/datasources/jbpmDS",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}

Note You need to log in before you can comment on or make changes to this bug.