September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2503) Extend DataInput & DataOutput to avoid copy of byte[]

by Jingqi Xu (Jira)

[ https://issues.redhat.com/browse/JGRP-2503?page=com.atlassian.jira.plugin... ] Jingqi Xu updated JGRP-2503: ---------------------------- Description: "DataInput's void readFully(byte b[])" will cause an extra copy when reading bytes from DataInput. Sometimes business logic needs to read bytes from DataInput first, then process them conditionally(or will not process at all) , is it possible to support ByteBuffer api like: public interface XDataInput extends DataInput { ByteBuffer readBuffer(int n); } public interface XDataOutput extends DataOutput { void writeBuffer(ByteBuffer value); } ByteArrayDataInputStream.java @Override public ByteBuffer readBuffer(int n) { ByteBuffer r = wrap(this.buf, this.pos, n); this.pos += n; return r; } public interface Streamable { void writeTo(XDataOutput out) throws IOException; void readFrom(XDataInput in) throws IOException, ClassNotFoundException; } was: "DataInput's void readFully(byte b[])" will cause an extra copy when reading bytes from DataInput. Sometimes business logic needs to read bytes from DataInput first, then process them conditionally(or will not process at all) , is it possible to support ByteBuffer api like: public interface XDataInput extends DataInput { ByteBuffer readBuffer(int n); } public interface XDataOutput extends DataOutput { void writeBuffer(ByteBuffer value); } ByteArrayDataInputStream.java @Override public XByteBuffer readBuffer(int n) { ByteBuffer r = wrap(this.buf, this.pos, n); this.pos += n; return r; } public interface Streamable { void writeTo(XDataOutput out) throws IOException; void readFrom(XDataInput in) throws IOException, ClassNotFoundException; } > Extend DataInput & DataOutput to avoid copy of byte[] > ----------------------------------------------------- > > Key: JGRP-2503 > URL: https://issues.redhat.com/browse/JGRP-2503 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 5.0.4 > Reporter: Jingqi Xu > Assignee: Bela Ban > Priority: Optional > > "DataInput's void readFully(byte b[])" will cause an extra copy when reading bytes from DataInput. Sometimes business logic needs to read bytes from DataInput first, then process them conditionally(or will not process at all) , is it possible to support ByteBuffer api like: > public interface XDataInput extends DataInput { > ByteBuffer readBuffer(int n); > } > public interface XDataOutput extends DataOutput { > void writeBuffer(ByteBuffer value); > } > ByteArrayDataInputStream.java > @Override > public ByteBuffer readBuffer(int n) { > ByteBuffer r = wrap(this.buf, this.pos, n); this.pos += n; return r; > } > public interface Streamable { > void writeTo(XDataOutput out) throws IOException; > void readFrom(XDataInput in) throws IOException, ClassNotFoundException; > } -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2503) Extend DataInput & DataOutput to avoid copy of byte[]

by Jingqi Xu (Jira)

Jingqi Xu created JGRP-2503: ------------------------------- Summary: Extend DataInput & DataOutput to avoid copy of byte[] Key: JGRP-2503 URL: https://issues.redhat.com/browse/JGRP-2503 Project: JGroups Issue Type: Feature Request Affects Versions: 5.0.4 Reporter: Jingqi Xu Assignee: Bela Ban "DataInput's void readFully(byte b[])" will cause an extra copy when reading bytes from DataInput. Sometimes business logic needs to read bytes from DataInput first, then process them conditionally(or will not process at all) , is it possible to support ByteBuffer api like: public interface XDataInput extends DataInput { ByteBuffer readBuffer(int n); } public interface XDataOutput extends DataOutput { void writeBuffer(ByteBuffer value); } ByteArrayDataInputStream.java @Override public XByteBuffer readBuffer(int n) { ByteBuffer r = wrap(this.buf, this.pos, n); this.pos += n; return r; } public interface Streamable { void writeTo(XDataOutput out) throws IOException; void readFrom(XDataInput in) throws IOException, ClassNotFoundException; } -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13884) JdrReportManagmentTestCase.generateStandaloneJdrReport fails on my ee9 branch

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13884?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFLY-13884 at 9/21/20 9:19 PM: ------------------------------------------------------------------ It's failing in a number of other jobs as well, so perhaps the test is expecting certain environmental conditions that don't always exist? https://ci.wildfly.org/viewLog.html?buildId=223170&tab=buildResultsDiv&bu... https://ci.wildfly.org/viewLog.html?buildId=222944&buildTypeId=WF_MasterL... Another possibility is there are issues with JDR in these environments and the increased checking you added to this test has revealed that. was (Author: brian.stansberry): It's failing in a number of other jobs as well, so perhaps the test is expecting certain environmental conditions that don't always exist? https://ci.wildfly.org/viewLog.html?buildId=223170&tab=buildResultsDiv&bu... https://ci.wildfly.org/viewLog.html?buildId=222944&buildTypeId=WF_MasterL... > JdrReportManagmentTestCase.generateStandaloneJdrReport fails on my ee9 branch > ----------------------------------------------------------------------------- > > Key: WFLY-13884 > URL: https://issues.redhat.com/browse/WFLY-13884 > Project: WildFly > Issue Type: Bug > Components: JDR > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > > On my ee9 branch JdrReportManagmentTestCase.generateStandaloneJdrReport fails when -Dts.ee9 us used. I'll disable it but we need to figure out why. > As part of whatever the fix is I'd like the sos_logs/skips.log to get special handling. Check it before checking the other files, and instead of just failing if not empty, capture the file contents and put them in the failure message. If there are future failures that will provide better info, even if the file is empty and the check passes, which would rule out a category of problems. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-13793: ---------------------------------- sure, the fix version was set when the attribute validation problem was resolved for 21.0.0.Beta1 before reopened, I have unset the fix version now. > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Feature Request > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13888) Move JWTEJBTestCase to testsuite/integration/microprofile

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13888: --------------------------------------- Summary: Move JWTEJBTestCase to testsuite/integration/microprofile Key: WFLY-13888 URL: https://issues.redhat.com/browse/WFLY-13888 Project: WildFly Issue Type: Task Components: MP JWT Reporter: Brian Stansberry Assignee: Darran Lofthouse Part of our overall testing strategy is wanting to be able to run testsuite/integration/basic using the output of the ee-build maven module or provisioning using the wildfly-ee feature pack. Having a JWT test in that testsuite breaks that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13884) JdrReportManagmentTestCase.generateStandaloneJdrReport fails on my ee9 branch

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13884?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13884: ----------------------------------------- It's failing in a number of other jobs as well, so perhaps the test is expecting certain environmental conditions that don't always exist? https://ci.wildfly.org/viewLog.html?buildId=223170&tab=buildResultsDiv&bu... https://ci.wildfly.org/viewLog.html?buildId=222944&buildTypeId=WF_MasterL... > JdrReportManagmentTestCase.generateStandaloneJdrReport fails on my ee9 branch > ----------------------------------------------------------------------------- > > Key: WFLY-13884 > URL: https://issues.redhat.com/browse/WFLY-13884 > Project: WildFly > Issue Type: Bug > Components: JDR > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > > On my ee9 branch JdrReportManagmentTestCase.generateStandaloneJdrReport fails when -Dts.ee9 us used. I'll disable it but we need to figure out why. > As part of whatever the fix is I'd like the sos_logs/skips.log to get special handling. Check it before checking the other files, and instead of just failing if not empty, capture the file contents and put them in the failure message. If there are future failures that will provide better info, even if the file is empty and the check passes, which would rule out a category of problems. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang updated WFLY-13793: ----------------------------- Issue Type: Feature Request (was: Bug) > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Feature Request > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang updated WFLY-13793: ----------------------------- Fix Version/s: (was: 21.0.0.Final) > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13793: ----------------------------------------- [~soul2zimate] [~ehugonnet] If this is a Feature Request or Enhancement please change the issue type. For Feature Request for sure the Fix Version should be unset, and for Enhancement I'd say it's about 98% sure that it should be unset. We're wrapping up work on WF 21. > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Final > > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5138) Upgrade JBoss Remoting to 5.0.19.Final

by Flavia Rainone (Jira)

Flavia Rainone created WFCORE-5138: -------------------------------------- Summary: Upgrade JBoss Remoting to 5.0.19.Final Key: WFCORE-5138 URL: https://issues.redhat.com/browse/WFCORE-5138 Project: WildFly Core Issue Type: Component Upgrade Reporter: Flavia Rainone Assignee: Flavia Rainone Upgrade JBoss Remoting to 5.0.19.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

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 September 2020