June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2194) Function for UNICAST3 to remove connections in CLOSING state

by Bela Ban (JIRA)

Bela Ban created JGRP-2194: ------------------------------ Summary: Function for UNICAST3 to remove connections in CLOSING state Key: JGRP-2194 URL: https://issues.jboss.org/browse/JGRP-2194 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Optional Fix For: 4.0.4 When a connection is closed in UNICAST3, it is not actually destroyed and removed, but transitioned into the CLOSING state. Only after {{conn_close_timeout}} ms is the connection really destroyed and removed. This means that if a connection to P has state, e.g. seqno=25, is subsequently closed but we send another message to P before the connection is destroyed, seqno=26 will be sent. If the connection was destroyed before, then a new connection with seqno=1 would be used. If an application wanted to destroy a connection to a peer, then this proposed function would do this. The implementation will probably be a managed operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2925) Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2925: ---------------------------------------- Summary: Separate heap settings in standalone.conf and domain.conf from rest of JAVA_OPTS Key: WFCORE-2925 URL: https://issues.jboss.org/browse/WFCORE-2925 Project: WildFly Core Issue Type: Enhancement Components: Scripts Reporter: Brian Stansberry Assignee: Tomaz Cerar Let's do this: {code} if [ "x$JBOSS_JAVA_SIZING" = "x" ]; then JBOSS_JAVA_SIZING="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m" fi if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="$JBOSS_JAVA_SIZING -Djava.net.preferIPv4Stack=true" JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" else echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS" fi {code} That will allow users to easily control memory sizing by setting that specific env var externally while still relying on our defaults for all the other fussy stuff in JAVA_OPTS. The JBOSS_JAVA_SIZING name was 20 secs of thought on my part. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1091) CS tool, Summary output must reflect chosen option, now there is always CLI command for add new credential store.

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1091?page=com.atlassian.jira.plugin.s... ] Yeray Borges updated ELY-1091: ------------------------------ Git Pull Request: https://github.com/wildfly-security/wildfly-elytron-tool/pull/39, https://github.com/wildfly-security/wildfly-elytron-tool/pull/64, https://github.com/wildfly-security/wildfly-elytron-tool/pull/78 (was: https://github.com/wildfly-security/wildfly-elytron-tool/pull/39, https://github.com/wildfly-security/wildfly-elytron-tool/pull/64) > CS tool, Summary output must reflect chosen option, now there is always CLI command for add new credential store. > ----------------------------------------------------------------------------------------------------------------- > > Key: ELY-1091 > URL: https://issues.jboss.org/browse/ELY-1091 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Yeray Borges > Priority: Critical > > Summary output must reflect chosen option. When I run wildfly-elytron-tool with --remove and --summary I always get "add command for CLI" > There is expected command for remove entry from credential store. > Same problem is there for --aliases, --exists > {code} > java -jar wildfly-elytron-tool.jar credential-store --remove secret_alias --password pass123 --uri "cr-store://test1.jceks?modifiable=true;create=true;keyStoreType=JCEKS" -l test1.jceks --summary > Alias "secret_alias" has been successfully removed > Credential store command summary: > -------------------------------------- > /subsystem=elytron/credential-store=test:add(uri="cr-store://test1.jceks?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="pass123"}) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Elis Edlund (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Elis Edlund commented on JASSIST-267: ------------------------------------- Looks like a follow up issue to https://issues.jboss.org/browse/JASSIST-244 The workaround suggested workaround in this case is not really applicable for me as I would *not* be able to "change the parent to public" > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1608) Move classes that are only used by jBPM from Drools to jBPM

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1608: ----------------------------------- Summary: Move classes that are only used by jBPM from Drools to jBPM Key: DROOLS-1608 URL: https://issues.jboss.org/browse/DROOLS-1608 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2160: ------------------------------------------------- Ivo Hradek <ihradek(a)redhat.com> changed the Status of [bug 1410924|https://bugzilla.redhat.com/show_bug.cgi?id=1410924] from ON_QA to ASSIGNED > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > Fix For: 3.0.0.Alpha23 > > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1607) Internal refactor removing KnowledgeBase in preparation for DROOLS-1583

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1607?page=com.atlassian.jira.plugi... ] Matteo Mortari resolved DROOLS-1607. ------------------------------------ Resolution: Done Done with: * http://github.com/kiegroup/droolsjbpm-knowledge/commit/2d6f52e45 * http://github.com/kiegroup/drools/commit/ffa6f44a1 * http://github.com/kiegroup/jbpm/commit/1feb6a036 * http://github.com/kiegroup/droolsjbpm-integration/commit/d93bf50fe > Internal refactor removing KnowledgeBase in preparation for DROOLS-1583 > ----------------------------------------------------------------------- > > Key: DROOLS-1607 > URL: https://issues.jboss.org/browse/DROOLS-1607 > Project: Drools > Issue Type: Sub-task > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1232) Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing

by Josef Cacek (JIRA)

Josef Cacek created ELY-1232: -------------------------------- Summary: Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing Key: ELY-1232 URL: https://issues.jboss.org/browse/ELY-1232 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Blocker I'm not able to get SCRAM PLUS SASL mechanisms (i.e. the ones with channel binding) working. It seems there is a missing piece of integration. The mechanisms are required by EAP7-530. I don't see the wrapper SASL factories, which are responsible for handling {{ChannelBindingCallback}}, used in the application server. (e.g. the {{TLSServerEndPointChannelBindingSaslClientFactory}}). This issue is blocking test development. There is still a chance the problem is in my test configuration, but the documentation of this topic is still a little bit sparse. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2193) View: use View.getCoord() to determine coordinator

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2193?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2193. ---------------------------- Resolution: Done > View: use View.getCoord() to determine coordinator > -------------------------------------------------- > > Key: JGRP-2193 > URL: https://issues.jboss.org/browse/JGRP-2193 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.4 > > > Often the coord is determined by getting a view's members and grabbing the first member of the view. If the list is empty, this fails with an NPE. > Instead, use {{View.getCoord()}} and handle the potential null value. > {noformat} > ViewId vid = new ViewId(new JGAddress(), 0); > List<Address> members = new ArrayList<>(); > View jgv = new View(vid, members); > this.myChannel.down(new Event(Event.VIEW_CHANGE, jgv)); > java.lang.ArrayIndexOutOfBoundsException: 0 > at java.util.Arrays$ArrayList.get(Arrays.java:3841) > at java.util.Collections$UnmodifiableList.get(Collections.java:1309) > at org.jgroups.protocols.pbcast.STABLE.handleViewChange(STABLE.java:365) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:328) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:347) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:347) > at org.jgroups.protocols.FRAG2.down(FRAG2.java:136) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1039) > at org.jgroups.JChannel.down(JChannel.java:790) > at org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:310) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8904) Fix AuthenticationTestCase for Elytron and unignore it

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8904?page=com.atlassian.jira.plugin.... ] Michal Jurc updated WFLY-8904: ------------------------------ Description: {{org.jboss.as.test.integration.ejb.security.AuthenticationTestCase}} currently fails in {{elytron}} profile due to different exception than expected (old PB one) being produced by Elytron: {code}Results : Failed tests: AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:257 null {code} When this is fixed, the test should be unignored for the {{elytron}} profile. was: {{org.jboss.as.test.integration.ejb.security.AuthenticationTestCase}} currently fails in {{elytron}} profile due to different exception than expected being produced by Elytron: {code}Results : Failed tests: AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:257 null {code} When this is fixed, the test should be unignored for the {{elytron}} profile. > Fix AuthenticationTestCase for Elytron and unignore it > ------------------------------------------------------ > > Key: WFLY-8904 > URL: https://issues.jboss.org/browse/WFLY-8904 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Michal Jurc > Assignee: Michal Jurc > > {{org.jboss.as.test.integration.ejb.security.AuthenticationTestCase}} currently fails in {{elytron}} profile due to different exception than expected (old PB one) being produced by Elytron: > {code}Results : > Failed tests: > AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:257 null > {code} > When this is fixed, the test should be unignored for the {{elytron}} profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017