[JBoss JIRA] (ELY-1243) Content of wildfly.config.url is parsed incorrectly for non-absolute URI
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1243?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1243:
------------------------------
Attachment: parse-authn-client-config-dep.war
> Content of wildfly.config.url is parsed incorrectly for non-absolute URI
> ------------------------------------------------------------------------
>
> Key: ELY-1243
> URL: https://issues.jboss.org/browse/ELY-1243
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Attachments: parse-authn-client-config-dep.war
>
>
> When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
> It seems this issue is probably caused by fix of issue [1] in PR [2].
> Thrown exception:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
> at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
> at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
> ... 41 more
> Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at java.io.FileInputStream.<init>(FileInputStream.java:93)
> at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
> ... 43 more
> {code}
> [1] https://issues.jboss.org/browse/JBEAP-10954
> [2] https://github.com/wildfly/wildfly-client-config/pull/7/files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1243) Content of wildfly.config.url is parsed incorrectly for non-absolute URI
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1243?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1243:
------------------------------
Description:
When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
It seems this issue is probably caused by fix of issue [1] in PR [2].
Thrown exception:
{code}
org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
... 41 more
Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileInputStream.<init>(FileInputStream.java:93)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
... 43 more
{code}
[1] https://issues.jboss.org/browse/JBEAP-10954
[2] https://github.com/wildfly/wildfly-client-config/pull/7/files
was:
When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
This issue is regression between EAP 7.1.0.ER1 and EAP 7.1.0.DR19 (and EAP 7.1.0.Alpha). We request blocker since it breaks feature in RFE EAP7-567 Client Side Security (Elytron Client).
It seems this issue is probably caused by fix of issue [1] in PR [2].
Thrown exception:
{code}
org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
... 41 more
Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileInputStream.<init>(FileInputStream.java:93)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
... 43 more
{code}
[1] https://issues.jboss.org/browse/JBEAP-10954
[2] https://github.com/wildfly/wildfly-client-config/pull/7/files
> Content of wildfly.config.url is parsed incorrectly for non-absolute URI
> ------------------------------------------------------------------------
>
> Key: ELY-1243
> URL: https://issues.jboss.org/browse/ELY-1243
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
> It seems this issue is probably caused by fix of issue [1] in PR [2].
> Thrown exception:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
> at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
> at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
> ... 41 more
> Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at java.io.FileInputStream.<init>(FileInputStream.java:93)
> at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
> ... 43 more
> {code}
> [1] https://issues.jboss.org/browse/JBEAP-10954
> [2] https://github.com/wildfly/wildfly-client-config/pull/7/files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1243) Content of wildfly.config.url is parsed incorrectly for non-absolute URI
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1243?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1243:
------------------------------
Affects Version/s: 1.1.0.Beta52
> Content of wildfly.config.url is parsed incorrectly for non-absolute URI
> ------------------------------------------------------------------------
>
> Key: ELY-1243
> URL: https://issues.jboss.org/browse/ELY-1243
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
> This issue is regression between EAP 7.1.0.ER1 and EAP 7.1.0.DR19 (and EAP 7.1.0.Alpha). We request blocker since it breaks feature in RFE EAP7-567 Client Side Security (Elytron Client).
> It seems this issue is probably caused by fix of issue [1] in PR [2].
> Thrown exception:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
> at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
> at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
> ... 41 more
> Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at java.io.FileInputStream.<init>(FileInputStream.java:93)
> at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
> at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
> ... 43 more
> {code}
> [1] https://issues.jboss.org/browse/JBEAP-10954
> [2] https://github.com/wildfly/wildfly-client-config/pull/7/files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1243) Content of wildfly.config.url is parsed incorrectly for non-absolute URI
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-1243:
---------------------------------
Summary: Content of wildfly.config.url is parsed incorrectly for non-absolute URI
Key: ELY-1243
URL: https://issues.jboss.org/browse/ELY-1243
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
When Elytron client tries to obtain {{ClientConfiguration}} through {{ClientConfiguration.getInstance()}} method and {{wildfly.config.url}} system property includes non-absolute URI then URI for obtaining Elytron Client configuration file is created incorrectly. It is created as {{value_of_user.dir_system_property}}+{{content_of_wildfly.config.url_system_property}}. It means that Elytron Client configuration file cannot be found and hence its content is not used by Elytron Client.
This issue is regression between EAP 7.1.0.ER1 and EAP 7.1.0.DR19 (and EAP 7.1.0.Alpha). We request blocker since it breaks feature in RFE EAP7-567 Client Side Security (Elytron Client).
It seems this issue is probably caused by fix of issue [1] in PR [2].
Thrown exception:
{code}
org.wildfly.client.config.ConfigXMLParseException: CONF0012: Failed to read from input source
at file:///home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:135)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:144)
at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
... 41 more
Caused by: java.io.FileNotFoundException: /home/user/temp/jboss-eap-7.1/bin/home/user/temp/wildfly-config.xml (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileInputStream.<init>(FileInputStream.java:93)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at org.wildfly.client.config.ClientConfiguration.streamOpener(ClientConfiguration.java:71)
at org.wildfly.client.config.ClientConfiguration.readConfiguration(ClientConfiguration.java:131)
... 43 more
{code}
[1] https://issues.jboss.org/browse/JBEAP-10954
[2] https://github.com/wildfly/wildfly-client-config/pull/7/files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8929) Race condition if timers overlap due to long running execution and short schedules if database persistence is used
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/WFLY-8929?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink reassigned WFLY-8929:
--------------------------------------
Assignee: Wolf-Dieter Fink (was: Stuart Douglas)
> Race condition if timers overlap due to long running execution and short schedules if database persistence is used
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8929
> URL: https://issues.jboss.org/browse/WFLY-8929
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Environment: Configure DB persistence for timers as file-persistence will not have a persistence check for shouldRun to lock the timer execution.
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Attachments: server-extract.log, server1.log
>
>
> If timers (here calendar timer) are running longer than scheduled, or the schedule/processing get stuck do to thread or cpu bottleneck, it is possible that the updates for persistence overlap.
> The issue seems that the task(1) try to finish the timer and task(2) is about to start but see the concurrency.
> The DB is updated with the 'old' next timeout, but the internal Timer instance will be updated with the next possible schedule due to a race condition between the two threads updating the object.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JGRP-2172) Non-blocking flow control
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2172:
---------------------------
Description:
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded). The max queue size is given in bytes, so we can estimate what the memory penalty for reaching that size would be (if bounded).
The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
Non-blocking flow control can be used by both external and internal threads.
If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
was:
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)
The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
Non-blocking flow control can be used by both external and internal threads.
If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
> Non-blocking flow control
> -------------------------
>
> Key: JGRP-2172
> URL: https://issues.jboss.org/browse/JGRP-2172
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.4
>
>
> Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
> Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded). The max queue size is given in bytes, so we can estimate what the memory penalty for reaching that size would be (if bounded).
> The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
> Non-blocking flow control can be used by both external and internal threads.
> If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JGRP-2172) Non-blocking flow control
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2172:
---------------------------
Description:
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)
The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
Non-blocking flow control can be used by both external and internal threads.
If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
was:
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)
The queued messages are sent when credits arrive.
Non-blocking flow control can be used by both external and internal threads.
If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
> Non-blocking flow control
> -------------------------
>
> Key: JGRP-2172
> URL: https://issues.jboss.org/browse/JGRP-2172
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.4
>
>
> Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
> Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)
> The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
> Non-blocking flow control can be used by both external and internal threads.
> If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[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:
-------------------------------------------------
Slavcho <sstavrev(a)redhat.com> changed the Status of [bug 1410924|https://bugzilla.redhat.com/show_bug.cgi?id=1410924] from NEW 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)
8 years, 11 months
[JBoss JIRA] (WFLY-4790) Getting DirectBuffer OOM when sending fragmented binary message to websocket endpoint
by cosmin cosmin (JIRA)
[ https://issues.jboss.org/browse/WFLY-4790?page=com.atlassian.jira.plugin.... ]
cosmin cosmin commented on WFLY-4790:
-------------------------------------
I updated undertow to version 1.3.Final on a wildfly 9.0.1 and got this exception :
[here|https://pastebin.com/tP56xTmT]
> Getting DirectBuffer OOM when sending fragmented binary message to websocket endpoint
> -------------------------------------------------------------------------------------
>
> Key: WFLY-4790
> URL: https://issues.jboss.org/browse/WFLY-4790
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Alpha3
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 10.0.0.Alpha6
>
>
> When sending fragmented binary message (message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64). The server throws {{java.lang.OutOfMemoryError: Direct buffer memory}} [1]
> The memory for direct buffer by default depends on the size set by -Xmx, which is in EAP 7.0.0.DR4 by default set to -Xmx512m. Increasing it just increases the time before the limit is hit (it is enough to send those messages multiple times to hit the limit again).
> I believe the issue is similar to the one for EAP 6.4: [https://bugzilla.redhat.com/show_bug.cgi?id=1223708]
> [1]
> {noformat}
> 15:10:55,463 ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: Direct buffer memory
> at java.nio.Bits.reserveMemory(Bits.java:658)
> at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57)
> at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55)
> at org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:143)
> at io.undertow.websockets.core.BufferedBinaryMessage$1.handleEvent(BufferedBinaryMessage.java:106)
> at io.undertow.websockets.core.BufferedBinaryMessage$1.handleEvent(BufferedBinaryMessage.java:97)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at io.undertow.server.protocol.framed.AbstractFramedStreamSourceChannel$1.run(AbstractFramedStreamSourceChannel.java:264)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:560)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:462)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months