April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2492) Analysis right panel doesn't close after exiting guided decision table asset view

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2492?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2492: ----------------------------------- Tester: Jozef Marko > Analysis right panel doesn't close after exiting guided decision table asset view > --------------------------------------------------------------------------------- > > Key: DROOLS-2492 > URL: https://issues.jboss.org/browse/DROOLS-2492 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Sree Hitha Gudimella > Assignee: Toni Rikkola > Attachments: Screen Shot 2018-04-23 at 10.35.20 AM.png, Screen Shot 2018-04-23 at 10.35.34 AM.png > > > Analysis panel that appears on the right while editing a guided decision table asset doesn't close by default after navigating to assets list view. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2492) Analysis right panel doesn't close after exiting guided decision table asset view

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2492?page=com.atlassian.jira.plugi... ] Michael Anstis moved AF-1170 to DROOLS-2492: -------------------------------------------- Project: Drools (was: AppFormer) Key: DROOLS-2492 (was: AF-1170) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: appformer) > Analysis right panel doesn't close after exiting guided decision table asset view > --------------------------------------------------------------------------------- > > Key: DROOLS-2492 > URL: https://issues.jboss.org/browse/DROOLS-2492 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Sree Hitha Gudimella > Assignee: Toni Rikkola > Attachments: Screen Shot 2018-04-23 at 10.35.20 AM.png, Screen Shot 2018-04-23 at 10.35.34 AM.png > > > Analysis panel that appears on the right while editing a guided decision table asset doesn't close by default after navigating to assets list view. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2263) GRAVE: JGRP000225: failed unmarshalling buffer into return value

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2263?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2263: -------------------------------- Then make it implement {{Streamable}} and implement {{writeTo()}} and {{readFrom()}}. > GRAVE: JGRP000225: failed unmarshalling buffer into return value > ---------------------------------------------------------------- > > Key: JGRP-2263 > URL: https://issues.jboss.org/browse/JGRP-2263 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.11 > Environment: jdk1.8.0_66.jdk > osx 10.10 & ubuntu 17.10 > Reporter: rama rama > Assignee: Bela Ban > Attachments: SimpleChat.java > > > trying to send a class that previous work with 3.x return > "failed unmarshalling buffer into return value" > jgroups instance it's configured with the default settings > i create a test case to reproduce it, executing this class on my 2 boxes return > ---- > GRAVE: JGRP000225: failed unmarshalling buffer into return value > java.lang.InstantiationException: com.eg.util.comm.SimpleChat$EError > at java.lang.Class.newInstance(Class.java:427) > at org.jgroups.util.Util.readException(Util.java:899) > at org.jgroups.util.Util.exceptionFromStream(Util.java:843) > at org.jgroups.util.Util.exceptionFromStream(Util.java:831) > at org.jgroups.util.Util.objectFromStream(Util.java:782) > at org.jgroups.util.Util.objectFromStream(Util.java:742) > at org.jgroups.blocks.RequestCorrelator.replyFromBuffer(RequestCorrelator.java:463) > at org.jgroups.blocks.RequestCorrelator.handleResponse(RequestCorrelator.java:408) > at org.jgroups.blocks.RequestCorrelator.dispatch(RequestCorrelator.java:363) > at org.jgroups.blocks.RequestCorrelator.receiveMessageBatch(RequestCorrelator.java:326) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:589) > at org.jgroups.JChannel.up(JChannel.java:837) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:896) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.RSVP.up(RSVP.java:233) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:196) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:416) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:293) > at org.jgroups.protocols.UNICAST3.deliverBatch(UNICAST3.java:1024) > at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:833) > at org.jgroups.protocols.UNICAST3.handleBatchFromSelf(UNICAST3.java:520) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:435) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:697) > at org.jgroups.protocols.BARRIER.up(BARRIER.java:195) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:212) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.stack.Protocol.up(Protocol.java:372) > at org.jgroups.protocols.TP.passBatchUp(TP.java:1274) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.passBatchUp(MaxOneThreadPerSender.java:284) > at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.run(MaxOneThreadPerSender.java:273) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoSuchMethodException: com.eg.util.comm.SimpleChat$EError.<init>() > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.newInstance(Class.java:412) > ... 37 more > ----- -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) TravisCI job for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-85?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-85: ------------------------------ Summary: TravisCI job for building and pushing test-mesh to public Docker Repo (was: Travis job for building and pushing test-mesh to public Docker Repo) > TravisCI job for building and pushing test-mesh to public Docker Repo > --------------------------------------------------------------------- > > Key: SWSQE-85 > URL: https://issues.jboss.org/browse/SWSQE-85 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) TravisCI for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-85?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-85: ------------------------------ Summary: TravisCI for building and pushing test-mesh to public Docker Repo (was: TravisCI job for building and pushing test-mesh to public Docker Repo) > TravisCI for building and pushing test-mesh to public Docker Repo > ----------------------------------------------------------------- > > Key: SWSQE-85 > URL: https://issues.jboss.org/browse/SWSQE-85 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) Jenkins job for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-85?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-85: ------------------------------ Team: Infrastructure > Jenkins job for building and pushing test-mesh to public Docker Repo > -------------------------------------------------------------------- > > Key: SWSQE-85 > URL: https://issues.jboss.org/browse/SWSQE-85 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) Travis job for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-85?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-85: ------------------------------ Summary: Travis job for building and pushing test-mesh to public Docker Repo (was: Jenkins job for building and pushing test-mesh to public Docker Repo) > Travis job for building and pushing test-mesh to public Docker Repo > ------------------------------------------------------------------- > > Key: SWSQE-85 > URL: https://issues.jboss.org/browse/SWSQE-85 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) Jenkins job for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-85?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-85: ------------------------------ Sprint: Kiali QE Sprint 4 > Jenkins job for building and pushing test-mesh to public Docker Repo > -------------------------------------------------------------------- > > Key: SWSQE-85 > URL: https://issues.jboss.org/browse/SWSQE-85 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1374) add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1374?page=com.atlassian.jira.plugin... ] Scott Marlow commented on JBJCA-1374: ------------------------------------- Or reference [http://www.ironjacamar.org/doc/userguide/1.2/en-US/html/ch04.html#configu...] > add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1374 > URL: https://issues.jboss.org/browse/JBJCA-1374 > Project: IronJacamar > Issue Type: Enhancement > Components: Core > Reporter: Scott Marlow > > In my internal testing with Hibernate, I hit a problem with IronJacamar throwing "javax.resource.ResourceException: IJ000459: Transaction is not active" error when called to get a database connection from pool from a thread that has an active transaction marked for rollback only. > The Hibernate jira is [https://hibernate.atlassian.net/browse/HHH-12472], which we are talking about changing. As well as WildFly jira [https://issues.jboss.org/browse/WFLY-10229] for a related bug. > Independent of the HHH-12472 + WFLY-10229 issues, I think it would be useful if there was a data source deployment option (in WildFly standalone*.xml) or system property, for disabling the IJ000459 check for rollback only transactions, as the IJ000459 check is not always expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1374) add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1374?page=com.atlassian.jira.plugin... ] Scott Marlow closed JBJCA-1374. ------------------------------- Resolution: Rejected never mind, just reading the IJ 1.2 doc and we should already have: {quote} " 4.1.2. Allow obtaining connections during MARKED_FOR_ROLLBACK IronJacamar doesn't allow to obtain a new connection once a transaction is in MARKED_FOR_ROLLBACK mode. This allows the container to fail eagerly, since any work after that point is wasted anyway. However, certain applications depends on getting a connection to perform work. IronJacamar has a system property called ironjacamar.allow_marked_for_rollback which can be set to true to enable this scenario. Note, that an existing enlisted connection is allowed to be obtained. This can be disallowed by setting the system property ironjacamar.allow_marked_for_rollback_fast_fail to true {quote} > add option for disabling transaction_marked_rollback_only_fail_fast check that throws "javax.resource.ResourceException: IJ000459: Transaction is not active" error > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1374 > URL: https://issues.jboss.org/browse/JBJCA-1374 > Project: IronJacamar > Issue Type: Enhancement > Components: Core > Reporter: Scott Marlow > > In my internal testing with Hibernate, I hit a problem with IronJacamar throwing "javax.resource.ResourceException: IJ000459: Transaction is not active" error when called to get a database connection from pool from a thread that has an active transaction marked for rollback only. > The Hibernate jira is [https://hibernate.atlassian.net/browse/HHH-12472], which we are talking about changing. As well as WildFly jira [https://issues.jboss.org/browse/WFLY-10229] for a related bug. > Independent of the HHH-12472 + WFLY-10229 issues, I think it would be useful if there was a data source deployment option (in WildFly standalone*.xml) or system property, for disabling the IJ000459 check for rollback only transactions, as the IJ000459 check is not always expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018