JCA cached-connection-manager options do not persist between restarts - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

Configure the profile, server groups, server in the customized manner via CLI in the standalone.xml or the domain.xml file.
Configure the JCA Subsystem via CLI
The default domain.xml configuration consists of a <cached-connection-manager/> tag and hence can then be further configured to enable the debug logging. For the same changes are seen in the domain.xml when it is configured via the CLI.
Constructing JCA Subsystem manually does not reflect to changes in the domain.xml file and neither the <cached-connection-manager/> get appended.

Environment

JBoss Enterprise Application Platform (EAP)
- 6.0.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)