February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9754) Global flag to supress transaction propagation for EJB clients inside of an server application

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-9754: -------------------------------------- Summary: Global flag to supress transaction propagation for EJB clients inside of an server application Key: WFLY-9754 URL: https://issues.jboss.org/browse/WFLY-9754 Project: WildFly Issue Type: Feature Request Components: EJB Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance Reporter: Wolf-Dieter Fink The remote interface can be marked with an annotation to control transaction propagation with org.jboss.ejb.client.annotation.ClientTransactionPolicy.* This can be useful if the application need to ensure a specific Tx behaviour for this combination. Remember the client does not know whether the server side is flagged to use Tx or not! But there are different issues - the Remote interface is polluted with WildFly specific annotations consider the interface could be used in an environment without WildFly - any call to the remote application should not propagate Tx context - any call to a remote server should not propagate a Tx context Consider former versions where able to control the Tx propagation by using JTA or JTS To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. possible solutions to disable the Tx propagation - add a flag in ejb-client.xml application descriptor (affect this application) - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9755) Global flag to supress transaction propagation for EJB clients inside of an server application

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-9755: -------------------------------------- Summary: Global flag to supress transaction propagation for EJB clients inside of an server application Key: WFLY-9755 URL: https://issues.jboss.org/browse/WFLY-9755 Project: WildFly Issue Type: Feature Request Components: EJB Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance Reporter: Wolf-Dieter Fink The remote interface can be marked with an annotation to control transaction propagation with org.jboss.ejb.client.annotation.ClientTransactionPolicy.* This can be useful if the application need to ensure a specific Tx behaviour for this combination. Remember the client does not know whether the server side is flagged to use Tx or not! But there are different issues - the Remote interface is polluted with WildFly specific annotations consider the interface could be used in an environment without WildFly - any call to the remote application should not propagate Tx context - any call to a remote server should not propagate a Tx context Consider former versions where able to control the Tx propagation by using JTA or JTS To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. possible solutions to disable the Tx propagation - add a flag in ejb-client.xml application descriptor (affect this application) - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9753) Promote best practice for PRs by using PR template

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9753?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-9753: ----------------------------------------- Co-author information can be tracked too: * https://help.github.com/articles/creating-a-commit-with-multiple-authors/ > Promote best practice for PRs by using PR template > -------------------------------------------------- > > Key: WFLY-9753 > URL: https://issues.jboss.org/browse/WFLY-9753 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > > Promote best practice for PRs by using PR template > Templates on GitHub: > * https://github.com/blog/2111-issue-and-pull-request-templates > * https://github.com/blog/2495-multiple-issue-and-pull-request-templates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9753) Promote best practice for PRs by using PR template

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9753?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-9753: ----------------------------------------- https://github.com/jboss-container-images/github-pr-template/blob/master/... is pretty nice > Promote best practice for PRs by using PR template > -------------------------------------------------- > > Key: WFLY-9753 > URL: https://issues.jboss.org/browse/WFLY-9753 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > > Promote best practice for PRs by using PR template > Templates on GitHub: > * https://github.com/blog/2111-issue-and-pull-request-templates > * https://github.com/blog/2495-multiple-issue-and-pull-request-templates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9753) Promote best practice for PRs by using PR template

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-9753: --------------------------------------- Summary: Promote best practice for PRs by using PR template Key: WFLY-9753 URL: https://issues.jboss.org/browse/WFLY-9753 Project: WildFly Issue Type: Task Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Promote best practice for PRs by using PR template Templates on GitHub: * https://github.com/blog/2111-issue-and-pull-request-templates * https://github.com/blog/2495-multiple-issue-and-pull-request-templates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2289) The response time jump add in stability test

by LIANG LIU (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2289?page=com.atlassian.jira.plugi... ] LIANG LIU commented on DROOLS-2289: ----------------------------------- I am so sorry. I cannot provide you a reproducer but I could provide code, test plan for your reference, then you could see the problem showed in screenshot in attachment. By the way,Jmeter and kie_server are in two machines.Hope it is helpful for you to figure out the problem and solution. Any questions please don't hesitate to let me know. Thanks! > The response time jump add in stability test > --------------------------------------------- > > Key: DROOLS-2289 > URL: https://issues.jboss.org/browse/DROOLS-2289 > Project: Drools > Issue Type: Quality Risk > Components: kie server > Affects Versions: 7.5.0.Final > Environment: tomcat version:8.5.24 jmeter version：jakarta-jmeter-2.5.1 Drools version：7.5.0.Final > cpu：2x6 x86_64， memory：32G， sysOS：CentOS release 6.3 > Reporter: LIANG LIU > Assignee: Maciej Swiderski > Attachments: InputFact.java, image-2018-02-02-14-51-31-166.png, screenshot-1.png, tomcat8_test.jmx > > > !image-2018-02-02-14-51-31-166.png|thumbnail! > Stability test the response time jump add! Figure ; En,there are 20 rules,like: > rule "1" > salience 9999 > when > $inputFact:InputFact(stateless_data["black_test"]== 1) > then > result.put(drools.getRule().getName(),1); > end > It's a problem I use or some parameters need to be set？ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2289) The response time jump add in stability test

by LIANG LIU (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2289?page=com.atlassian.jira.plugi... ] LIANG LIU updated DROOLS-2289: ------------------------------ Attachment: screenshot-1.png > The response time jump add in stability test > --------------------------------------------- > > Key: DROOLS-2289 > URL: https://issues.jboss.org/browse/DROOLS-2289 > Project: Drools > Issue Type: Quality Risk > Components: kie server > Affects Versions: 7.5.0.Final > Environment: tomcat version:8.5.24 jmeter version：jakarta-jmeter-2.5.1 Drools version：7.5.0.Final > cpu：2x6 x86_64， memory：32G， sysOS：CentOS release 6.3 > Reporter: LIANG LIU > Assignee: Maciej Swiderski > Attachments: InputFact.java, image-2018-02-02-14-51-31-166.png, screenshot-1.png, tomcat8_test.jmx > > > !image-2018-02-02-14-51-31-166.png|thumbnail! > Stability test the response time jump add! Figure ; En,there are 20 rules,like: > rule "1" > salience 9999 > when > $inputFact:InputFact(stateless_data["black_test"]== 1) > then > result.put(drools.getRule().getName(),1); > end > It's a problem I use or some parameters need to be set？ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3553) Improve message from CLI when writing into the directory without permission

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3553?page=com.atlassian.jira.plugi... ] Martin Stefanko resolved WFCORE-3553. ------------------------------------- Resolution: Done Current output: {code} [standalone@embedded /] echo aaa > ./dir/without/permission ./dir/without/permission (Permission denied) aaa > ./dir/without/permission {code} [~kanovotn] If you still don't think it is sufficient enough, reopen the issue please. > Improve message from CLI when writing into the directory without permission > --------------------------------------------------------------------------- > > Key: WFCORE-3553 > URL: https://issues.jboss.org/browse/WFCORE-3553 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha6 > Reporter: Katerina Novotna > Assignee: Martin Stefanko > Priority: Minor > > *Description of problem:* > Cli displays java exception name when trying to write into the file without permission. > *Actual results:* > [standalone@embedded /] echo aaa > /dir/without/permission > java.nio.file.AccessDeniedException: /dir/without/permission > *Expected results:* > [standalone@embedded /] echo aaa > /dir/without/permission > Couldn't write into the /dir/without/permission. Permission denied. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3553) Improve message from CLI when writing into the directory without permission

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3553?page=com.atlassian.jira.plugi... ] Martin Stefanko reassigned WFCORE-3553: --------------------------------------- Assignee: Martin Stefanko (was: Jean-Francois Denise) > Improve message from CLI when writing into the directory without permission > --------------------------------------------------------------------------- > > Key: WFCORE-3553 > URL: https://issues.jboss.org/browse/WFCORE-3553 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha6 > Reporter: Katerina Novotna > Assignee: Martin Stefanko > Priority: Minor > > *Description of problem:* > Cli displays java exception name when trying to write into the file without permission. > *Actual results:* > [standalone@embedded /] echo aaa > /dir/without/permission > java.nio.file.AccessDeniedException: /dir/without/permission > *Expected results:* > [standalone@embedded /] echo aaa > /dir/without/permission > Couldn't write into the /dir/without/permission. Permission denied. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2245) JGroup JDBC_PING is not clearing the crashed members

by Sibin Karnavar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2245?page=com.atlassian.jira.plugin.... ] Sibin Karnavar commented on JGRP-2245: -------------------------------------- Got it, Thank you. > JGroup JDBC_PING is not clearing the crashed members > ---------------------------------------------------- > > Key: JGRP-2245 > URL: https://issues.jboss.org/browse/JGRP-2245 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.8 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.10 > > > 1) In AWS cloud environments, IP address will be different when a node crashes and when a new cluster node gets recreated. > 2) In this situation, JGroup is not clearing logical_addr_cache and it gets confused, when we restart the cluster nodes. > 3)logical_addr_cache_max_size and the eviction did not work because, the cache is again getting updated from the ping and it never getting marked as removable. > I think the issue is > handleView method is always re writing the entire cache on view change to the db. So even if we clear the table with the help of above mentioned flags (remove_all_data_on_view_change && remove_old_coords_on_view_change) , its getting re written to the table. > {code:java} > // remove all files which are not from the current members > protected void handleView(View new_view, View old_view, boolean coord_changed) { > if(is_coord) { > if(coord_changed) { > if(remove_all_data_on_view_change) > removeAll(cluster_name); > else if(remove_old_coords_on_view_change) { > Address old_coord=old_view != null? old_view.getCreator() : null; > if(old_coord != null) > remove(cluster_name, old_coord); > } > } > if(coord_changed || View.diff(old_view, new_view)[1].length > 0) { > writeAll(); > if(remove_all_data_on_view_change || remove_old_coords_on_view_change) > startInfoWriter(); > } > } > else if(coord_changed) // I'm no longer the coordinator > remove(cluster_name, local_addr); > } > {code} > 4) Because of the crashed members (non existing ip address), we are getting lot of socket timeouts > sendToMembers of TP is trying to send messages to old crashed members and writing error logs while startup. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 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 February 2018