[JBoss JIRA] Created: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
3:48 a.m.
sql-message-filter optional attribute "insert-timestamp-column" actually not
optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP4
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2212:
-------------------------------------
The code you are talking about has not changed since January 2008 and is unlikely to be a
regression. It does not look like this has ever worked.
Can you attach the testcase which you believe has regressed? I would like to take a look
at it.
Thanks
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP4
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Lukas Petrovicky commented on JBESB-2212:
-----------------------------------------
I investigated SVN history of the test in question and found out that previous version
(that was run on SOA 4.2.0 CP02) did specify the insert-timestamp-column. This bug is ergo
not a regression, my apologies.
If you still need to take a look at the test, you can find the QS here:
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP4
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Lukas Petrovicky commented on JBESB-2212:
-----------------------------------------
Here:
https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/notifiers
And the test for it here:
https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/tests/src...
Should you need help running our test suite, contact me on IRC.
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP4
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2212:
-------------------------------------
No, your explanation is enough. I just could not understand, given the current code and
its age, how this could ever have worked.
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP4
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2212:
--------------------------------
Fix Version/s: 4.2.1 CP5
(was: 4.2.1 CP4)
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Priority: Blocker
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2212:
--------------------------------
Priority: Major (was: Blocker)
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Mark Little reassigned JBESB-2212:
----------------------------------
Assignee: Mark Little
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Assignee: Mark Little
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Work on JBESB-2212 started by Mark Little.
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Assignee: Mark Little
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:37 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Mark Little commented on JBESB-2212:
------------------------------------
Pulled across trunk fix from a while ago and verified fix. Waiting for CP04 release before
checking in.
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Assignee: Mark Little
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2212) sql-message-filter optional attribute "insert-timestamp-column" actually not optional
[
https://jira.jboss.org/jira/browse/JBESB-2212?page=com.atlassian.jira.plu...
]
Mark Little closed JBESB-2212.
------------------------------
Resolution: Done
sql-message-filter optional attribute
"insert-timestamp-column" actually not optional
-------------------------------------------------------------------------------------
Key: JBESB-2212
URL: https://jira.jboss.org/jira/browse/JBESB-2212
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2.1 CP4
Reporter: Lukas Petrovicky
Assignee: Mark Little
Fix For: 4.2.1 CP5
XSD for jboss-esb.xml clearly states that the parameter
"insert-timestamp-column" for sql-message-filter is optional. However, when you
don't supply it, following queries are executed, which causes the whole SQL provider
not to work correctly (notice the missing column name):
update NOTIFICATIONS_TABLE set STATUS_COL = 'W' , = 'Tue Dec 02 10:17:23 CET
2008' where STATUS_COL = 'P' and UNIQUE_ID = 1234
This is what I have in the jboss-esb.xml:
<sql-message-filter tablename="NOTIFICATIONS_TABLE"
status-column="STATUS_COL"
message-id-column="UNIQUE_ID"
message-column="MESSAGECONTENTS" />
This was discovered on SOA-P 4.2.0 CP03 by one of our regression tests - it is clearly a
regression as it worked fine on SOA-P 4.2.0 CP02.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5783
days inactive
5840
days old
10 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Lukas Petrovicky (JIRA)
-
Mark Little (JIRA)