]
Jay Kumar SenSharma updated WFLY-4615:
--------------------------------------
Workaround Description:
*NOTE*- If we manually edit the "standalone.xml" file DataSource configuration
which is generated via console andset
<max-pool-size>20</max-pool-size> greater than 0
Example:
{code}
<pool>
<min-pool-size>0</min-pool-size>
<initial-pool-size>0</initial-pool-size>
<max-pool-size>20</max-pool-size>
<allow-multiple-users>false</allow-multiple-users>
</pool>
{code}
was:
*NOTE*- If we manually edit the "standalone.xml" file DataSource configuration
which is generated via console and remove the following part from the Generated DataSource
section then it works perfectly fine:
{code}
<pool>
<min-pool-size>0</min-pool-size>
<initial-pool-size>0</initial-pool-size>
<max-pool-size>0</max-pool-size>
<allow-multiple-users>false</allow-multiple-users>
</pool>
{code}
DataSource created via console fails when test connection is done in
WildFly 9
------------------------------------------------------------------------------
Key: WFLY-4615
URL:
https://issues.jboss.org/browse/WFLY-4615
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 9.0.0.CR1
Environment: All
Reporter: Jay Kumar SenSharma
Assignee: Heiko Braun
- When a datasource is created via Console (WildFly 9 CR1) then it always fails when test
connection is done on MySQL datasource created via consle.
Following error is thrown :
{code}
Unexpected HTTP response: 500
Request
{
"address" => [
("subsystem" => "datasources"),
("data-source" => "MySqlDS")
],
"operation" => "test-connection-in-pool"
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation:
WFLYJCA0042: failed to match pool. Check JndiName: java:/MySqlDS",
"rolled-back" => true,
"response-headers" => {"process-state" =>
"reload-required"}
}
{code}
- Even after reloading the whole standalone server the test always fails.