[jboss-jira] [JBoss JIRA] (AS7-2963) Provide extended datasource configuration options
Heiko Braun (Commented) (JIRA)
jira-events at lists.jboss.org
Fri Dec 9 02:36:41 EST 2011
[ https://issues.jboss.org/browse/AS7-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649520#comment-12649520 ]
Heiko Braun commented on AS7-2963:
----------------------------------
For XA Datasources:
Create
* XA properties
- Check minimum one entry before "Next" is enabled
* Connection
- New connection SQL
- Transaction isolation (drop-down)
* Pool
- Min-pool-size
- Max-pool-size
- Prefill: Yes/No (default: No)
- Enable is-same-rm-override => if yes => Value: True/False (default: True)
- Enable interleaving
- Pad Xid (default: No)
- Wrap XAResource (default: Yes)
* Security (excludes each other)
- Username / password
- Security domain
* Validation
- valid-connection-checker (drop-down that can be edited)
(values include built-in checkers)
- check-valid-connection-sql (excludes the one above)
- validate-on-match (excludes background*)
- background-validation (default: No)
- background-validation-millis
- stale-connection-checker (drop-down that can be edited)
(values include built-in checkers)
- exception-sorter (drop-down that can be edited)
(values include built-in sorters)
* Statement
- prepared-statement-cache-size
- share-prepared-statements (default: No)
* Recovery
- Enable (default: Yes)
Built-ins:
http://docs.jboss.org/ironjacamar/userguide/1.0/en-
US/html/deployment.html#deployingds_extensions
Overview:
- Is enabled ? => Enabled
- Use JTA ? => JTA
- Use CCM ? => CCM
- true => Yes
- false => No
- Use strict min => Strict minimum
- Use prefill => Prefill enabled
- We need the real pool values - we need to figure out where the issue is
- We need the pool statistics
- We need the JDBC statistics
the 3 last ones we will check with Stefano.
I think we can skip the other attributes / elements in the XSD for now.
> Provide extended datasource configuration options
> -------------------------------------------------
>
> Key: AS7-2963
> URL: https://issues.jboss.org/browse/AS7-2963
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 7.1.0.CR1
>
>
> Jesper:
> Create
> * Overall
> - JTA: Yes/No (default: Yes)
> * Connection
> - New connection SQL
> - Transaction isolation (if JTA) (drop-down)
> * Pool
> - Min-pool-size
> - Max-pool-size
> - Prefill: Yes/No (default: No)
> * Security (excludes each other)
> - Username / password
> - Security domain
> * Validation
> - valid-connection-checker (drop-down that can be edited)
> (values include built-in checkers)
> - check-valid-connection-sql (excludes the one above)
> - validate-on-match (excludes background*)
> - background-validation (default: No)
> - background-validation-millis
> - stale-connection-checker (drop-down that can be edited)
> (values include built-in checkers)
> - exception-sorter (drop-down that can be edited)
> (values include built-in sorters)
> * Statement
> - prepared-statement-cache-size
> - share-prepared-statements (default: No)
> Built-ins:
> http://docs.jboss.org/ironjacamar/userguide/1.0/en-
> US/html/deployment.html#deployingds_extensions
> Overview:
> - Is enabled ? => Enabled
> - Use JTA ? => JTA
> - Use CCM ? => CCM
> - true => Yes
> - false => No
> - Use strict min => Strict minimum
> - Use prefill => Prefill enabled
> - We need the real pool values - we need to figure out where the issue is
> - We need the pool statistics
> - We need the JDBC statistics
> the 3 last ones we will check with Stefano.
> I think we can skip the other attributes / elements in the XSD for now.
--
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
More information about the jboss-jira
mailing list