August 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3173) Check that the LRA quickstarts work with the latest MP-LRA snapshot

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3173: -------------------------------------- Summary: Check that the LRA quickstarts work with the latest MP-LRA snapshot Key: JBTM-3173 URL: https://issues.jboss.org/browse/JBTM-3173 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator, LRA Affects Versions: 5.9.6.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The LRA quickstarts in the rts/lra-examples need updating to work on the latest MP-LRA snapshot release -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3170) BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3170?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3170: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3170 > URL: https://issues.jboss.org/browse/JBTM-3170 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Simon Dallaway > Assignee: Ondrej Chaloupka > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3172) Failing CI tests on Windows - Catelyn JDK8

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3172?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka reassigned JBTM-3172: -------------------------------------- Assignee: Ondrej Chaloupka > Failing CI tests on Windows - Catelyn JDK8 > ------------------------------------------ > > Key: JBTM-3172 > URL: https://issues.jboss.org/browse/JBTM-3172 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: catelyn-build55-archive.zip, catelyn-build55-consoleText.txt > > > The Narayana CI for Windows fails with compilation failure on Catelyn. This failure occurs consistently but only on JDK8, not on JDK11. The failure is (see whole log console in attachment) > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0-jboss-2:compile (default-compile) on project jta: Compilation failure: Compilation failure: > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,1] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,3] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,5] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,13] > expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,3] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,5] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,7] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,4] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,7] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,9] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,14] <identifier> expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,15] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,19] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,31] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,50] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,63] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,77] <identifier> expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,13] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,14] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,132] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,157] ';' expected > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jta > {code} > When I run the compilation manually on Catelyn with JDK {{:\Progra~1\java\jdk1.8.0_20\bin\java.exe}} I have hit no issue either with compilation or with the testing. Maybe I run wrong JDK version or there is some another issue in involvement of Jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3172) Failing CI tests on Windows - Catelyn JDK8

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3172: -------------------------------------- Summary: Failing CI tests on Windows - Catelyn JDK8 Key: JBTM-3172 URL: https://issues.jboss.org/browse/JBTM-3172 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Ondrej Chaloupka Attachments: catelyn-build55-archive.zip, catelyn-build55-consoleText.txt The Narayana CI for Windows fails with compilation failure on Catelyn. This failure occurs consistently but only on JDK8, not on JDK11. The failure is (see whole log console in attachment) {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0-jboss-2:compile (default-compile) on project jta: Compilation failure: Compilation failure: [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,1] illegal start of type [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,3] = expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,5] ';' expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,13] > expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,3] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,5] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,7] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,4] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,7] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,9] illegal start of expression [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,14] <identifier> expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,15] ';' expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,19] illegal start of type [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,31] = expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,50] = expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,63] = expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,77] <identifier> expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,13] = expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,14] ';' expected [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,132] illegal start of type [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,157] ';' expected [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jta {code} When I run the compilation manually on Catelyn with JDK {{:\Progra~1\java\jdk1.8.0_20\bin\java.exe}} I have hit no issue either with compilation or with the testing. Maybe I run wrong JDK version or there is some another issue in involvement of Jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3169) Update MP-LRA implementation for recent status code changes

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3169?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3169: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update MP-LRA implementation for recent status code changes > ----------------------------------------------------------- > > Key: JBTM-3169 > URL: https://issues.jboss.org/browse/JBTM-3169 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > MP-LRA issue 195 (see https://github.com/eclipse/microprofile-lra/issues) introduced some changes to response codes that relate to how unknown LRA id's are handled by implementations. The associated tests for the issue also uncovered a bug in how recovery handles in progress LRA's. The new TCK tests are in pull request 205. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3171) Validate that the LRA recovery header is set on LRA completion notifications

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3171: -------------------------------------- Summary: Validate that the LRA recovery header is set on LRA completion notifications Key: JBTM-3171 URL: https://issues.jboss.org/browse/JBTM-3171 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.9.6.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next LRA includes the capability to receive JAX-RS notifications when an LRA is finished but the implementation does not set the "recovery header". This requirement was added in MP-LRA issue eclipse/microprofile-lra#209 when new tests were created to verify that the recovery header is set correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3170) BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3170?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on JBTM-3170: ---------------------------------------- [~simon.dallaway] From what I can see you are absolutely right about the issue. I created the PR for that. Please, feel free to contact us at the forum at https://community.jboss.org/en/jbosstm to discuss your issues. And you are more than welcome to propose your PR for the bug you find. Just create the PR at https://github.com/jbosstm/narayana. Thank you for your bug report and the contribution to the Narayana project! > BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3170 > URL: https://issues.jboss.org/browse/JBTM-3170 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Simon Dallaway > Assignee: Ondrej Chaloupka > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3170) BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3170?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3170: ----------------------------------- Description: The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included The current code is fileName = parameter.substring(0, breakPosition - 1); The correct code should be fileName = parameter.substring(0, breakPosition); was: The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included The current code is fileName = parameter.substring(0, breakPosition - 1); The correct code should be fileName = parameter.substring(0, breakPosition); Git Pull Request: https://github.com/jbosstm/narayana/pull/1480 Steps to Reproduce: Include a number of connections in the com.arjuna.ats.jta.recovery.XAResourceRecovery1 property value e.g. -Dcom.arjuna.ats.jta.recovery.XAResourceRecovery1=com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery;abs://%CATALINA_HOME%/conf/xa-recovery-properties.xml;1 was: Include a number of connections in the com.arjuna.ats.jta.recovery.XAResourceRecovery1 property value e.g. -Dcom.arjuna.ats.jta.recovery.XAResourceRecovery1=com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery;abs://%CATALINA_HOME%/conf/xa-recovery-properties.xml;1 > BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3170 > URL: https://issues.jboss.org/browse/JBTM-3170 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Simon Dallaway > Assignee: Ondrej Chaloupka > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3170) BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3170?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondrej Chaloupka created pull request #1480 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3170 > URL: https://issues.jboss.org/browse/JBTM-3170 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Simon Dallaway > Assignee: Ondrej Chaloupka > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3170) BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3170?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka reassigned JBTM-3170: -------------------------------------- Assignee: Ondrej Chaloupka > BasicXARecovery class calculates the name of the XA recovery properties file incorrectly if a number of connections is included > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3170 > URL: https://issues.jboss.org/browse/JBTM-3170 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Simon Dallaway > Assignee: Ondrej Chaloupka > Priority: Trivial > > The procedure initialise of BasicXARecovery incorrectly calculates the name of the XA recovery properties file if a number of connections is included > The current code is > fileName = parameter.substring(0, breakPosition - 1); > The correct code should be > fileName = parameter.substring(0, breakPosition); -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2019