[
https://issues.jboss.org/browse/JBAS-9252?page=com.atlassian.jira.plugin....
]
Andrig Miller commented on JBAS-9252:
-------------------------------------
When the properties disappear, then of course, after you restart, you don't have them.
That's all I'm pointing out. I was able to work around this, but putting the
properties on the connection URL.
So, as long as the properties stay in the file, they are properly being set on the
connections.
So, I think you are done, and if you get this into the Beta 3, I'll test again.
Connection properties disappear in the standalone.xml after running.
--------------------------------------------------------------------
Key: JBAS-9252
URL:
https://issues.jboss.org/browse/JBAS-9252
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: 7.0.0.Beta2
Reporter: Andrig Miller
Assignee: Stefano Maestri
Priority: Critical
Fix For: 7.0.0.Beta3
In Beta 2, I wanted to test that connection properties were now properly handled, so I
set the following two connection properties for my MySQL data source:
<connection-property
name="rewriteBatchStatements">true</connection-property>
<connection-property
name="maintainTimeStats">false</connection-property>
After starting up the server, and running a test, I noticed that my test results
weren't what I was expecting, performance wise, but the error I was getting because of
the value of the connection property being quoted, was not in the log. So the other issue
was fixed, but this go around, I saw that both connection properties just disappeared from
the standalone.xml.
No warning or error in the log either.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira