April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2483) Kjars aren't recognized as projects using the executable model when installed directly into the KieRepository

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2483: ----------------------------------- Summary: Kjars aren't recognized as projects using the executable model when installed directly into the KieRepository Key: DROOLS-2483 URL: https://issues.jboss.org/browse/DROOLS-2483 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10229) org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on WFLY-10229: -------------------------------------- [~smarlow] why is ContextTransactionManager maintaining its own transaction status code - that is the role of the transaction manager to determine the transaction status. > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus() > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10229 > URL: https://issues.jboss.org/browse/WFLY-10229 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Scott Marlow > Assignee: David Lloyd > Fix For: 13.0.0.Beta1 > > > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() is currently using com.arjuna.ats.jta.TransactionManager, instead it should use org.wildfly.transaction.client.ContextTransactionManager.getStatus(). > I'm seeing a case in Hibernate ORM 5.3, where org.wildfly.transaction.client.ContextTransactionManager.getStatus() returns 4 but TransactionSynchronizationRegistryWrapper.getStatus() returns 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10229) org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on WFLY-10229: -------------------------------------- [~dmlloyd] if the transaction has been marked for rollback then Narayana won't call before completion: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... it will call afterCompletion with the outcome. > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus() > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10229 > URL: https://issues.jboss.org/browse/WFLY-10229 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Scott Marlow > Assignee: David Lloyd > Fix For: 13.0.0.Beta1 > > > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() is currently using com.arjuna.ats.jta.TransactionManager, instead it should use org.wildfly.transaction.client.ContextTransactionManager.getStatus(). > I'm seeing a case in Hibernate ORM 5.3, where org.wildfly.transaction.client.ContextTransactionManager.getStatus() returns 4 but TransactionSynchronizationRegistryWrapper.getStatus() returns 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBNAME-26) NumberFormatException when there is an extra space in jndi.properties for jnp.timeout

by Ondrej Medek (JIRA)

[ https://issues.jboss.org/browse/JBNAME-26?page=com.atlassian.jira.plugin.... ] Ondrej Medek commented on JBNAME-26: ------------------------------------ I had a similar problem while ago. I've provided a config.properties to my customer/users. To overcome this Java deficiency, I've made a wrapper/helper class trimming extra spaces for all properties. This bug is 8 years old, I do not use JBoss now. It's just up to you how user-friendly you want to be to your users. > NumberFormatException when there is an extra space in jndi.properties for jnp.timeout > ------------------------------------------------------------------------------------- > > Key: JBNAME-26 > URL: https://issues.jboss.org/browse/JBNAME-26 > Project: JBoss Naming > Issue Type: Bug > Components: jnp-client > Affects Versions: 5.0.1.GA > Reporter: Ondrej Medek > Assignee: Radovan Netuka > Priority: Minor > > Hi, > if there's an extra space after the value of the property "jnp.timeout" or "jnp.sotimeout", then the exception is thrown: > java.lang.NumberFormatException: For input string: "6000 " > I had in jndi.properties the line: "jnp.timeout = 6000 " > (Note one extra space after "6000"). > I think, something like String.trim() should solve this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10229) org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10229: ------------------------------------- [~tomjenkinson] {quote} I don't understand why ContextTransactionManager is reporting it is rolled back if Narayana thinks it is only marked rollback - but perhaps that was explained on the private thread? {quote} I don't have a full understanding of why ContextTransactionManager is reporting different values from TransactionManager.getStatus() than the Narayna TransactionSynchronizationRegistry.getStatus() but I suspect it is related to ContextTransactionManager maintaining its own transaction status code. > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus() > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10229 > URL: https://issues.jboss.org/browse/WFLY-10229 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Scott Marlow > Assignee: David Lloyd > Fix For: 13.0.0.Beta1 > > > org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() is currently using com.arjuna.ats.jta.TransactionManager, instead it should use org.wildfly.transaction.client.ContextTransactionManager.getStatus(). > I'm seeing a case in Hibernate ORM 5.3, where org.wildfly.transaction.client.ContextTransactionManager.getStatus() returns 4 but TransactionSynchronizationRegistryWrapper.getStatus() returns 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-113: ------------------------------------------ Sprint: Kiali QE Sprint 4 > Allocate OpenShift and Jenkins resources for testing Jaeger productized images > ------------------------------------------------------------------------------ > > Key: SWSQE-113 > URL: https://issues.jboss.org/browse/SWSQE-113 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > > I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet. > I can work with either of these two options > -- A project on an OpenShift Cluster where I can create my own Jenkins instance. > -- An external Jenkins which has an agent defined which can run on OpenShift. > I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution. > Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2317) FEEL Syntax error on function(bkm) containing `for` keyword

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2317?page=com.atlassian.jira.plugi... ] Fedor Gavrilov reassigned DROOLS-2317: -------------------------------------- Assignee: Fedor Gavrilov (was: Matteo Mortari) > FEEL Syntax error on function(bkm) containing `for` keyword > ----------------------------------------------------------- > > Key: DROOLS-2317 > URL: https://issues.jboss.org/browse/DROOLS-2317 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Fedor Gavrilov > Attachments: Dynamic composition.dmn > > > Attached model > {code:java} > Error compiling FEEL expression 'for item in Order.items return Federal Tax for Item( item )' for name 'Calculate Federal Taxes' on node 'Calculate Federal Taxes': syntax error near 'for' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-161) Create Jenkins Job To Push Out Latest Kiali - For Community Usage

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-161: ---------------------------------- Summary: Create Jenkins Job To Push Out Latest Kiali - For Community Usage Key: SWSQE-161 URL: https://issues.jboss.org/browse/SWSQE-161 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Michael Foley Note: Could be that we leverage the existing CD pipeline for this task. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBNAME-26) NumberFormatException when there is an extra space in jndi.properties for jnp.timeout

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBNAME-26?page=com.atlassian.jira.plugin.... ] Radovan Netuka resolved JBNAME-26. ---------------------------------- Resolution: Won't Fix > NumberFormatException when there is an extra space in jndi.properties for jnp.timeout > ------------------------------------------------------------------------------------- > > Key: JBNAME-26 > URL: https://issues.jboss.org/browse/JBNAME-26 > Project: JBoss Naming > Issue Type: Bug > Components: jnp-client > Affects Versions: 5.0.1.GA > Reporter: Ondrej Medek > Assignee: Radovan Netuka > Priority: Minor > > Hi, > if there's an extra space after the value of the property "jnp.timeout" or "jnp.sotimeout", then the exception is thrown: > java.lang.NumberFormatException: For input string: "6000 " > I had in jndi.properties the line: "jnp.timeout = 6000 " > (Note one extra space after "6000"). > I think, something like String.trim() should solve this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBNAME-26) NumberFormatException when there is an extra space in jndi.properties for jnp.timeout

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBNAME-26?page=com.atlassian.jira.plugin.... ] Radovan Netuka commented on JBNAME-26: -------------------------------------- This is how Java properties works. Leading whitespace are trimmed, trailing are not. The property from your example is read with trailing whitespace character as "6000 " and this couldn't be parsed into a number. Closing this as it is not a bug. If you insist on this feature, you should re-create it as feature request. > NumberFormatException when there is an extra space in jndi.properties for jnp.timeout > ------------------------------------------------------------------------------------- > > Key: JBNAME-26 > URL: https://issues.jboss.org/browse/JBNAME-26 > Project: JBoss Naming > Issue Type: Bug > Components: jnp-client > Affects Versions: 5.0.1.GA > Reporter: Ondrej Medek > Assignee: Radovan Netuka > Priority: Minor > > Hi, > if there's an extra space after the value of the property "jnp.timeout" or "jnp.sotimeout", then the exception is thrown: > java.lang.NumberFormatException: For input string: "6000 " > I had in jndi.properties the line: "jnp.timeout = 6000 " > (Note one extra space after "6000"). > I think, something like String.trim() should solve this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 April 2018