[Red Hat JIRA] (WFCORE-5229) Utilize JBoss Modules version 1.9 in module descriptors
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5229?page=com.atlassian.jira.plug... ]
Brian Stansberry reassigned WFCORE-5229:
----------------------------------------
Fix Version/s: 14.0.0.Beta5
Assignee: Boris Unckel (was: Richard Opalka)
Resolution: Done
> Utilize JBoss Modules version 1.9 in module descriptors
> -------------------------------------------------------
>
> Key: WFCORE-5229
> URL: https://issues.redhat.com/browse/WFCORE-5229
> Project: WildFly Core
> Issue Type: Task
> Components: Modules
> Affects Versions: 14.0.0.Beta4
> Reporter: Boris Unckel
> Assignee: Boris Unckel
> Priority: Major
> Fix For: 14.0.0.Beta5
>
> Attachments: 2020-12-12_wfcorejdep_14.0.0.Beta5-SNAPSHOT.7z
>
>
> There are still modules which use 1.6 or 1.7 and do not need that. The idea is to run jdeps on each artifact of a modul, add the relevant java.* modules to the dependencies of the module and upgrade to version 1.8. In a first only none-jdk modules and none which depend on system dependency.
> Full list:
> ./system/layers/base/sun/scripting/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.scripting">
> ./system/layers/base/sun/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.jdk">
> ./system/layers/base/ibm/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="ibm.jdk">
> ./system/layers/base/io/undertow/core/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="io.undertow.core">
> ./system/layers/base/org/apache/log4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.log4j">
> ./system/layers/base/org/apache/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.commons.logging">
> ./system/layers/base/org/fusesource/jansi/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.fusesource.jansi">
> ./system/layers/base/org/slf4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j">
> ./system/layers/base/org/slf4j/impl/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j.impl">
> ./system/layers/base/org/jboss/stdio/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.stdio">
> ./system/layers/base/org/jboss/jandex/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.jandex">
> ./system/layers/base/org/jboss/vfs/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.vfs">
> ./system/layers/base/org/jboss/staxmapper/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.staxmapper">
> ./system/layers/base/org/jboss/as/domain-http-error-context/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-http-error-context">
> ./system/layers/base/org/jboss/as/core-security-api/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.core-security-api">
> ./system/layers/base/org/jboss/as/version/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.version">
> ./system/layers/base/org/jboss/as/domain-add-user/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-add-user">
> ./system/layers/base/org/jboss/as/management-client-content/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.management-client-content">
> ./system/layers/base/org/jboss/as/deployment-repository/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.deployment-repository">
> ./system/layers/base/org/jboss/as/threads/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.threads">
> ./system/layers/base/org/jboss/as/patching/cli/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.patching.cli">
> ./system/layers/base/org/jboss/as/controller-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.controller-client">
> ./system/layers/base/org/jboss/as/standalone/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.standalone">
> ./system/layers/base/org/jboss/logging/jul-to-slf4j-stub/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging.jul-to-slf4j-stub">
> ./system/layers/base/org/jboss/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging">
> ./system/layers/base/org/jboss/invocation/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.invocation">
> ./system/layers/base/org/jboss/dmr/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.dmr">
> ./system/layers/base/org/wildfly/embedded/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.embedded">
> ./system/layers/base/org/wildfly/extension/core-management-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.extension.core-management-client">
> ./system/layers/base/org/wildfly/security/manager/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.manager">
> ./system/layers/base/org/wildfly/security/elytron/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.elytron">
> ./system/layers/base/org/jboss/logging/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.7" name="org.jboss.logging.commons.logging">
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 9 months
[Red Hat JIRA] (WFLY-12263) Not able to use admin console on HTTPS in wildfly 17
by Mahantesh Padache (Jira)
[ https://issues.redhat.com/browse/WFLY-12263?page=com.atlassian.jira.plugi... ]
Mahantesh Padache commented on WFLY-12263:
------------------------------------------
Hi,
I have the same issue and working on it from 2 days.
The xml file is same.
If anybody have solution on how to use WildFly Admin console, Please lets us know here.
I will update if i got a solution to it.
> Not able to use admin console on HTTPS in wildfly 17
> ----------------------------------------------------
>
> Key: WFLY-12263
> URL: https://issues.redhat.com/browse/WFLY-12263
> Project: WildFly
> Issue Type: Bug
> Components: Management
> Affects Versions: 17.0.0.Final
> Reporter: Abhishek Goyal
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: standalone.xml
>
>
> Hi Floks
> I am facing one issue when i am trying to use Management Interfaces for HTTPS , wildfly not able to deploy the wars and its stopped but when i changed to http its working fine.
> you can refer the configuration which i did in standalone.xml file.
> Below tag i added in the management .
> {code:xml}
> <management-interfaces>
> <http-interface security-realm="ManagementRealmHTTPS">
> <http-upgrade enabled="true"/>
> <socket-binding https="management-https"/>
> </http-interface>
> </management-interfaces>
> {code}
> I added the security realm under security-realms.
> {code:xml}
> <security-realm name="ManagementRealmHTTPS">
> <server-identities>
> <ssl>
> <keystore path="keystore" relative-to="jboss.server.config.dir" keystore-password="Ivr@123"/>
> </ssl>
> </server-identities>
> <authentication>
> <properties path="https-mgmt-users.properties" relative-to="jboss.server.config.dir"/>
> </authentication>
> </security-realm>
> {code}
> and below is the socket-binding group config.
> {code:xml}
> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
> <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
> <socket-binding name="http" port="${jboss.http.port:8080}"/>
> <socket-binding name="https" port="${jboss.https.port:8443}"/>
> <socket-binding name="txn-recovery-environment" port="4712"/>
> <socket-binding name="txn-status-manager" port="4713"/>
> <outbound-socket-binding name="mail-smtp">
> <remote-destination host="localhost" port="25"/>
> </outbound-socket-binding>
> </socket-binding-group>
> {code}
> After doing all this config server is not coming up.
> Its giving the below logs.
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/wildfly-17.0.0.Final
> JAVA: /opt/jdk1.8.0_181/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 08:15:17,354 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 08:15:17,869 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.7.Final
> 08:15:17,899 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 08:15:18,075 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) starting
> 08:15:19,291 INFO [org.wildfly.security] (ServerService Thread Pool -- 21) ELY00001: WildFly Elytron version 1.9.1.Final
> 08:15:20,013 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 08:15:20,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 6) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 08:15:20,160 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0040: Creating http management service using secure-socket-binding (management-https)
> 08:15:20,190 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.7.2.Final
> 08:15:20,205 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.7.2.Final
> 08:15:20,272 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem.
> 08:15:20,308 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.7.0.Final
> 08:15:20,319 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
> 08:15:20,337 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 08:15:20,339 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.16.Final)
> 08:15:20,350 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
> 08:15:20,367 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
> 08:15:20,375 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
> 08:15:20,395 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem
> 08:15:20,395 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
> 08:15:20,442 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
> 08:15:20,455 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
> 08:15:20,469 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 08:15:20,440 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
> 08:15:20,475 INFO [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem
> 08:15:20,521 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
> 08:15:20,532 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 08:15:20,544 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.21.Final starting
> 08:15:20,555 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.3.Final
> 08:15:20,619 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.12.Final
> 08:15:20,663 INFO [io.smallrye.metrics] (MSC service thread 1-6) Converted [2] config entries and added [4] replacements
> 08:15:20,840 INFO [io.smallrye.metrics] (MSC service thread 1-6) Converted [3] config entries and added [14] replacements
> 08:15:20,920 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path '/tmp/wildfly-17.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 08:15:20,945 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
> 08:15:20,949 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
> 08:15:21,096 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
> 08:15:21,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
> 08:15:21,271 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
> 08:15:21,516 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 08:15:21,526 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
> 08:15:21,661 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 08:15:21,747 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 08:15:21,854 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2)
> 08:15:21,945 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTPS listener https suspending
> 08:15:21,946 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
> 08:15:21,963 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 08:15:21,967 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
> 08:15:21,968 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP listener default suspending
> 08:15:21,971 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 08:15:21,989 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 08:15:22,006 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 2.0.21.Final stopping
> 08:15:22,008 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 08:15:22,051 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 08:15:22,078 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) stopped in 20ms
> {noformat}
> Can anyone help me on that.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 9 months
[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set
by Davy Koravand (Jira)
[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ]
Davy Koravand commented on WFCORE-5216:
---------------------------------------
I would like to add that using eval instead of exec helps us as well, as we experienced some problems with spaces in JAVA_OPTS on Unix machines. I think it's worth patching jboss-cli.sh with eval.
> EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-5216
> URL: https://issues.redhat.com/browse/WFCORE-5216
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Priority: Major
>
> Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages:
> {noformat}
> INFO Duration: 347 milliseconds
> ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script.
> org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297)
> at org.jboss.modules.Main.main(Main.java:371)
> {noformat}
> This issue does not occur on JBoss EAP 7.2 container.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 9 months
[Red Hat JIRA] (JGRP-2503) Extend DataInput & DataOutput to avoid copy of byte[]
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2503?page=com.atlassian.jira.plugin... ]
Bela Ban closed JGRP-2503.
--------------------------
Resolution: Rejected
> Extend DataInput & DataOutput to avoid copy of byte[]
> -----------------------------------------------------
>
> Key: JGRP-2503
> URL: https://issues.redhat.com/browse/JGRP-2503
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.4
> Reporter: Jingqi Xu
> Assignee: Bela Ban
> Priority: Optional
> Fix For: 5.1.3
>
>
> "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
(v8.13.1#813001)
4 years, 9 months
[Red Hat JIRA] (JGRP-2503) Extend DataInput & DataOutput to avoid copy of byte[]
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2503?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2503:
--------------------------------
Doesn't work, see my comments in the PR. Closing for now...
> Extend DataInput & DataOutput to avoid copy of byte[]
> -----------------------------------------------------
>
> Key: JGRP-2503
> URL: https://issues.redhat.com/browse/JGRP-2503
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.4
> Reporter: Jingqi Xu
> Assignee: Bela Ban
> Priority: Optional
> Fix For: 5.1.3
>
>
> "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
(v8.13.1#813001)
4 years, 9 months
[Red Hat JIRA] (JGRP-2503) Extend DataInput & DataOutput to avoid copy of byte[]
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2503?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2503:
---------------------------
Fix Version/s: 5.1.3
(was: 5.1)
Issue Type: Enhancement (was: Feature Request)
> Extend DataInput & DataOutput to avoid copy of byte[]
> -----------------------------------------------------
>
> Key: JGRP-2503
> URL: https://issues.redhat.com/browse/JGRP-2503
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.4
> Reporter: Jingqi Xu
> Assignee: Bela Ban
> Priority: Optional
> Fix For: 5.1.3
>
>
> "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
(v8.13.1#813001)
4 years, 9 months