[JBoss JIRA] Created: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
9:41 a.m.
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: Jesper Pedersen
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
9:47 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
[
https://issues.jboss.org/browse/JBAS-9252?page=com.atlassian.jira.plugin....
]
Jesper Pedersen updated JBAS-9252:
----------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
Priority: Critical (was: Major)
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
3:15 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
[
https://issues.jboss.org/browse/JBAS-9252?page=com.atlassian.jira.plugin....
]
Stefano Maestri commented on JBAS-9252:
---------------------------------------
well it seems 2 different issues:
connection properties disappeared because we have missed these TAG write back code.
It's already fixed on my local branch. But it's not the main issue you are
pointing us. You are saying that property list are totally ignored from the underlying
connection. Could you provide us a complete example? Have you got a chance to try the same
example on IronJacamar?
thanks in advance
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
7:59 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
[
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
10:08 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
[
https://issues.jboss.org/browse/JBAS-9252?page=com.atlassian.jira.plugin....
]
Stefano Maestri commented on JBAS-9252:
---------------------------------------
fixed here https://github.com/maeste/jboss-as/tree/JBAS-9252
pull request sent. I'll close the issue as soon as it is pushed on master
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
3:51 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-9252) Connection properties disappear in the standalone.xml after running.
[
https://issues.jboss.org/browse/JBAS-9252?page=com.atlassian.jira.plugin....
]
Stefano Maestri resolved JBAS-9252.
-----------------------------------
Resolution: Done
Merged into master
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
4922
days inactive
4930
days old
5 comments
3 participants
participants (3)
-
Andrig Miller (JIRA) -
Jesper Pedersen (JIRA)
-
Stefano Maestri (JIRA)