July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12281) Upgrade jboss-ejb-client from 4.0.20 to 4.0.21

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12281?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12281: ------------------------------ Affects Version/s: 17.0.1.Final > Upgrade jboss-ejb-client from 4.0.20 to 4.0.21 > ---------------------------------------------- > > Key: WFLY-12281 > URL: https://issues.jboss.org/browse/WFLY-12281 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12281) Upgrade jboss-ejb-client from 4.0.20 to 4.0.21

by Cheng Fang (Jira)

Cheng Fang created WFLY-12281: --------------------------------- Summary: Upgrade jboss-ejb-client from 4.0.20 to 4.0.21 Key: WFLY-12281 URL: https://issues.jboss.org/browse/WFLY-12281 Project: WildFly Issue Type: Component Upgrade Reporter: Cheng Fang Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12281) Upgrade jboss-ejb-client from 4.0.20 to 4.0.21

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12281?page=com.atlassian.jira.plugin... ] Cheng Fang reassigned WFLY-12281: --------------------------------- Assignee: Cheng Fang (was: Brian Stansberry) > Upgrade jboss-ejb-client from 4.0.20 to 4.0.21 > ---------------------------------------------- > > Key: WFLY-12281 > URL: https://issues.jboss.org/browse/WFLY-12281 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12258) Upgrade wildfly-transaction-client from 1.1.4.Final to 1.1.5.Final

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12258?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12258: ------------------------------ Description: compare 1.1.4.Final vs 1.1.5.Final: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.4.Final... > Upgrade wildfly-transaction-client from 1.1.4.Final to 1.1.5.Final > ------------------------------------------------------------------ > > Key: WFLY-12258 > URL: https://issues.jboss.org/browse/WFLY-12258 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB, Transactions > Affects Versions: 17.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > compare 1.1.4.Final vs 1.1.5.Final: > https://github.com/wildfly/wildfly-transaction-client/compare/1.1.4.Final... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12280) DatabaseTimerPersistence does not detect mssql driver type

by David Ward (Jira)

[ https://issues.jboss.org/browse/WFLY-12280?page=com.atlassian.jira.plugin... ] David Ward updated WFLY-12280: ------------------------------ Description: The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] I _think_ the fix would be as simple as changing this line: {code:java} }else if (name.toLowerCase().contains("microsoft")) { {code} to this: {code:java} }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { {code} [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... was: The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] I _believe_ fix would be as simple as changing this line: {code:java} }else if (name.toLowerCase().contains("microsoft")) { {code} to this: {code:java} }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { {code} [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... > DatabaseTimerPersistence does not detect mssql driver type > ---------------------------------------------------------- > > Key: WFLY-12280 > URL: https://issues.jboss.org/browse/WFLY-12280 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: David Ward > Assignee: Filippe Spolti > Priority: Major > > The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". > The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. > The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] > We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] > I _think_ the fix would be as simple as changing this line: > {code:java} > }else if (name.toLowerCase().contains("microsoft")) { > {code} > to this: > {code:java} > }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { > {code} > [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... > [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... > [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12280) DatabaseTimerPersistence does not detect mssql driver type

by Filippe Spolti (Jira)

[ https://issues.jboss.org/browse/WFLY-12280?page=com.atlassian.jira.plugin... ] Filippe Spolti reassigned WFLY-12280: ------------------------------------- Assignee: Filippe Spolti (was: Cheng Fang) > DatabaseTimerPersistence does not detect mssql driver type > ---------------------------------------------------------- > > Key: WFLY-12280 > URL: https://issues.jboss.org/browse/WFLY-12280 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: David Ward > Assignee: Filippe Spolti > Priority: Major > > The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". > The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. > The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] > We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] > I _believe_ fix would be as simple as changing this line: > {code:java} > }else if (name.toLowerCase().contains("microsoft")) { > {code} > to this: > {code:java} > }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { > {code} > [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... > [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... > [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12280) DatabaseTimerPersistence does not detect mssql driver type

by David Ward (Jira)

[ https://issues.jboss.org/browse/WFLY-12280?page=com.atlassian.jira.plugin... ] David Ward updated WFLY-12280: ------------------------------ Description: The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] I _believe_ fix would be as simple as changing this line: {code:java} }else if (name.toLowerCase().contains("microsoft")) { {code} to this: {code:java} }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { {code} [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... was: The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] We rean into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] I _believe_ fix would be as simple as changing this line: {code:java} }else if (name.toLowerCase().contains("microsoft")) { {code} to this: {code:java} }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { {code} [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... > DatabaseTimerPersistence does not detect mssql driver type > ---------------------------------------------------------- > > Key: WFLY-12280 > URL: https://issues.jboss.org/browse/WFLY-12280 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: David Ward > Assignee: Cheng Fang > Priority: Major > > The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". > The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. > The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] > We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] > I _believe_ fix would be as simple as changing this line: > {code:java} > }else if (name.toLowerCase().contains("microsoft")) { > {code} > to this: > {code:java} > }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { > {code} > [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... > [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... > [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12280) DatabaseTimerPersistence does not detect mssql driver type

by David Ward (Jira)

David Ward created WFLY-12280: --------------------------------- Summary: DatabaseTimerPersistence does not detect mssql driver type Key: WFLY-12280 URL: https://issues.jboss.org/browse/WFLY-12280 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 17.0.1.Final Reporter: David Ward Assignee: Cheng Fang The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] We rean into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] I _believe_ fix would be as simple as changing this line: {code:java} }else if (name.toLowerCase().contains("microsoft")) { {code} to this: {code:java} }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { {code} [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4564) ${maven.repository.url} in repository url is not evaluated when org.jboss:jboss-parent is missing

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4564?page=com.atlassian.jira.plugi... ] James Perkins resolved WFCORE-4564. ----------------------------------- Resolution: Won't Fix > ${maven.repository.url} in repository url is not evaluated when org.jboss:jboss-parent is missing > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-4564 > URL: https://issues.jboss.org/browse/WFCORE-4564 > Project: WildFly Core > Issue Type: Bug > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency > > When EAP 7.2.3.CR1 is built in a clean environment without cached maven dependencies it fails with the following error: > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=140499&buildTy... > This is caused by maven not evaluating properties in time which means that internal repo *download.devel.redhat.com* is never tried for dependencies download - https://github.com/jbossas/jboss-eap7/commit/fc7dfde0a5309173dd4deca18f79... > This is a know maven issue: https://issues.apache.org/jira/browse/MNG-5611 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4276) Rules with accumulate cannot be compiled natively

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4276?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4276. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/kogito-runtimes/commit/402bff4974d5c60c065a4e... > Rules with accumulate cannot be compiled natively > ------------------------------------------------- > > Key: DROOLS-4276 > URL: https://issues.jboss.org/browse/DROOLS-4276 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Executable model generated for rules with accumulates uses reflection and then cannot be compiled natively. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019