June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4778) WebSocket connection failed because of Unexpected response code: 501

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4778?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-4778. ---------------------------------- Resolution: Cannot Reproduce Bug Tried out your example on both 9.x and upstream and websockets and the example work fine > WebSocket connection failed because of Unexpected response code: 501 > -------------------------------------------------------------------- > > Key: WFLY-4778 > URL: https://issues.jboss.org/browse/WFLY-4778 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Mike Mike > Assignee: Stuart Douglas > Attachments: push-test.zip > > > I am trying to use Wilfly 9 RC with Vaadins Server Push. The Push works but I get always following message in the java script log: > Vaadin push loaded > vaadinPush.js:21 WebSocket connection to 'ws://localhost:8080/abc-ui/PUSH/?v-uiId=0&v-csrfToken=9592bfe8-549f-4713-85b4-8ddae0163407&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.0.3.vaadin2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json;%20charset=UTF-8' failed: Error during WebSocket handshake: Unexpected response code: 501 > vaadinPush.js:21 Websocket failed. Downgrading to Comet and resending > The HTTP 501 (Not Implemented) is really irritating. Which side is implementing and who specifies? > I found this topic related here: http://atmosphere-framework.2306103.n4.nabble.com/Websocket-Connection-Fa... > Does anybody know here, if it is a bug in WildFly or atmosphere? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-818) Listeners declared in kmodule.xml are not registered in StatelessKieSession

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-818?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-818: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1233192, https://bugzilla.redhat.com/show_bug.cgi?id=1233197 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1233192) > Listeners declared in kmodule.xml are not registered in StatelessKieSession > --------------------------------------------------------------------------- > > Key: DROOLS-818 > URL: https://issues.jboss.org/browse/DROOLS-818 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.Beta2 > > > Listener declared in kmodule.xml as in the following snippet of XML works on stateful KieSession, but are not registered on stateless ones. > {code} > <ksession name="statelessKieSession1" type="stateless"> > <listeners> > <ruleRuntimeEventListener type="com.esrx.ref.testproject.TestRuleRuntimeEventListener"/> > </listeners> > </ksession> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-818) Listeners declared in kmodule.xml are not registered in StatelessKieSession

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-818?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-818: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1233192 > Listeners declared in kmodule.xml are not registered in StatelessKieSession > --------------------------------------------------------------------------- > > Key: DROOLS-818 > URL: https://issues.jboss.org/browse/DROOLS-818 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.Beta2 > > > Listener declared in kmodule.xml as in the following snippet of XML works on stateful KieSession, but are not registered on stateless ones. > {code} > <ksession name="statelessKieSession1" type="stateless"> > <listeners> > <ruleRuntimeEventListener type="com.esrx.ref.testproject.TestRuleRuntimeEventListener"/> > </listeners> > </ksession> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4790) Getting DirectBuffer OOM when sending fragmented binary message to websocket endpoint

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4790?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4790: -------------------------------------- This should be fixed in upstream undertow. > 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 > > 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 (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-751) Failed to initialize Aesh console while starting CLI on fresh Windows 2k8

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-751?page=com.atlassian.jira.plugin... ] Petr Kremensky updated WFCORE-751: ---------------------------------- Comment: was deleted (was: This issue affects also Installer jar C:\>java -jar e:\static_build_env\eap\7.0.0.DR4\jboss-eap-7.0.0.DR4-installer.jar auto.xml Checking for corresponding .variables file Variables file detected: C:\auto.xml.variables [ Starting automated installation ] Read pack list from xml definition. Try to add to selection [Name: Red Hat JBoss Enterprise Application Platform and Index: 0] Try to add to selection [Name: AppClient and Index: 1] Try to add to selection [Name: Bin and Index: 2] Try to add to selection [Name: Bundles and Index: 3] Try to add to selection [Name: XMLs and XSDs and Index: 4] Try to add to selection [Name: Domain and Index: 5] Try to add to selection [Name: Domain Batch Scripts and Index: 6] Try to add to selection [Name: Modules and Index: 7] Try to add to selection [Name: Standalone and Index: 8] Try to add to selection [Name: Standalone Batch Scripts and Index: 9] Try to add to selection [Name: Welcome Content and Index: 10] Try to remove from selection [Name: Quickstarts and Index: 11] Modify pack selection. Pack [Name: Quickstarts and Index: 11] removed from selection. Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no jansi in java.library.path, C:\Users\Adminis trator\AppData\Local\Temp\jansi-64.dll: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail] at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:184) at org.fusesource.hawtjni.runtime.Library.load(Library.java:142) at org.fusesource.jansi.internal.Kernel32.<clinit>(Kernel32.java:37) at org.fusesource.jansi.WindowsAnsiOutputStream.<clinit>(WindowsAnsiOutputStream.java:52) at org.jboss.aesh.terminal.WindowsTerminal.init(WindowsTerminal.java:53) at org.jboss.aesh.console.Console.setTerminal(Console.java:194) at org.jboss.aesh.console.Console.reset(Console.java:155) at org.jboss.aesh.console.Console.<init>(Console.java:106) at com.izforge.izpack.util.Shell.<init>(Shell.java:56) at com.izforge.izpack.util.Shell.getInstance(Shell.java:74) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getInputs(UserInputPanelAutomationHelper.java:324) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getAutoPromptVariable(UserInputPanelAutomationHelper.java:300) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getAutoPromptVariable(UserInputPanelAutomationHelper.java:246) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.runAutomated(UserInputPanelAutomationHelper.java:197) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:579) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:519) at com.izforge.izpack.installer.Installer.main(Installer.java:173) ) > Failed to initialize Aesh console while starting CLI on fresh Windows 2k8 > ------------------------------------------------------------------------- > > Key: WFCORE-751 > URL: https://issues.jboss.org/browse/WFCORE-751 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha4 > Environment: Windows Server 2008 64bit Service Pack 2 > Oracle JDK 8_40 & 8_45 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > > Initializing interactive CLI session via jboss-cli.bat script fails during initializing of Aesh console. Non-interactive commands work. > >jboss-cli.bat -c > fails > >jboss-cli.bat -c "echo test" > works > Installing Microsoft Visual C++ 2008 Redistributable Package solves the problem > We encountered a similar issue in the past with EAP installer jar:\\ > Bug 1190789 - Installer: Installation of EAP with installation script fails on Windows W2k8 servers -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-751) Failed to initialize Aesh console while starting CLI on fresh Windows 2k8

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-751?page=com.atlassian.jira.plugin... ] Petr Kremensky updated WFCORE-751: ---------------------------------- Priority: Major (was: Blocker) > Failed to initialize Aesh console while starting CLI on fresh Windows 2k8 > ------------------------------------------------------------------------- > > Key: WFCORE-751 > URL: https://issues.jboss.org/browse/WFCORE-751 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha4 > Environment: Windows Server 2008 64bit Service Pack 2 > Oracle JDK 8_40 & 8_45 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > > Initializing interactive CLI session via jboss-cli.bat script fails during initializing of Aesh console. Non-interactive commands work. > >jboss-cli.bat -c > fails > >jboss-cli.bat -c "echo test" > works > Installing Microsoft Visual C++ 2008 Redistributable Package solves the problem > We encountered a similar issue in the past with EAP installer jar:\\ > Bug 1190789 - Installer: Installation of EAP with installation script fails on Windows W2k8 servers -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-751) Failed to initialize Aesh console while starting CLI on fresh Windows 2k8

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-751?page=com.atlassian.jira.plugin... ] Petr Kremensky updated WFCORE-751: ---------------------------------- Priority: Blocker (was: Major) > Failed to initialize Aesh console while starting CLI on fresh Windows 2k8 > ------------------------------------------------------------------------- > > Key: WFCORE-751 > URL: https://issues.jboss.org/browse/WFCORE-751 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha4 > Environment: Windows Server 2008 64bit Service Pack 2 > Oracle JDK 8_40 & 8_45 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > Priority: Blocker > > Initializing interactive CLI session via jboss-cli.bat script fails during initializing of Aesh console. Non-interactive commands work. > >jboss-cli.bat -c > fails > >jboss-cli.bat -c "echo test" > works > Installing Microsoft Visual C++ 2008 Redistributable Package solves the problem > We encountered a similar issue in the past with EAP installer jar:\\ > Bug 1190789 - Installer: Installation of EAP with installation script fails on Windows W2k8 servers -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-751) Failed to initialize Aesh console while starting CLI on fresh Windows 2k8

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-751?page=com.atlassian.jira.plugin... ] Petr Kremensky commented on WFCORE-751: --------------------------------------- This issue affects also Installer jar C:\>java -jar e:\static_build_env\eap\7.0.0.DR4\jboss-eap-7.0.0.DR4-installer.jar auto.xml Checking for corresponding .variables file Variables file detected: C:\auto.xml.variables [ Starting automated installation ] Read pack list from xml definition. Try to add to selection [Name: Red Hat JBoss Enterprise Application Platform and Index: 0] Try to add to selection [Name: AppClient and Index: 1] Try to add to selection [Name: Bin and Index: 2] Try to add to selection [Name: Bundles and Index: 3] Try to add to selection [Name: XMLs and XSDs and Index: 4] Try to add to selection [Name: Domain and Index: 5] Try to add to selection [Name: Domain Batch Scripts and Index: 6] Try to add to selection [Name: Modules and Index: 7] Try to add to selection [Name: Standalone and Index: 8] Try to add to selection [Name: Standalone Batch Scripts and Index: 9] Try to add to selection [Name: Welcome Content and Index: 10] Try to remove from selection [Name: Quickstarts and Index: 11] Modify pack selection. Pack [Name: Quickstarts and Index: 11] removed from selection. Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no jansi in java.library.path, C:\Users\Adminis trator\AppData\Local\Temp\jansi-64.dll: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail] at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:184) at org.fusesource.hawtjni.runtime.Library.load(Library.java:142) at org.fusesource.jansi.internal.Kernel32.<clinit>(Kernel32.java:37) at org.fusesource.jansi.WindowsAnsiOutputStream.<clinit>(WindowsAnsiOutputStream.java:52) at org.jboss.aesh.terminal.WindowsTerminal.init(WindowsTerminal.java:53) at org.jboss.aesh.console.Console.setTerminal(Console.java:194) at org.jboss.aesh.console.Console.reset(Console.java:155) at org.jboss.aesh.console.Console.<init>(Console.java:106) at com.izforge.izpack.util.Shell.<init>(Shell.java:56) at com.izforge.izpack.util.Shell.getInstance(Shell.java:74) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getInputs(UserInputPanelAutomationHelper.java:324) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getAutoPromptVariable(UserInputPanelAutomationHelper.java:300) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.getAutoPromptVariable(UserInputPanelAutomationHelper.java:246) at com.izforge.izpack.panels.UserInputPanelAutomationHelper.runAutomated(UserInputPanelAutomationHelper.java:197) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:579) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:519) at com.izforge.izpack.installer.Installer.main(Installer.java:173) > Failed to initialize Aesh console while starting CLI on fresh Windows 2k8 > ------------------------------------------------------------------------- > > Key: WFCORE-751 > URL: https://issues.jboss.org/browse/WFCORE-751 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha4 > Environment: Windows Server 2008 64bit Service Pack 2 > Oracle JDK 8_40 & 8_45 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > Priority: Blocker > > Initializing interactive CLI session via jboss-cli.bat script fails during initializing of Aesh console. Non-interactive commands work. > >jboss-cli.bat -c > fails > >jboss-cli.bat -c "echo test" > works > Installing Microsoft Visual C++ 2008 Redistributable Package solves the problem > We encountered a similar issue in the past with EAP installer jar:\\ > Bug 1190789 - Installer: Installation of EAP with installation script fails on Windows W2k8 servers -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-769) Boot errors should hide the failure description if the failing operation is not accessible

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-769?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet updated WFCORE-769: ------------------------------------- Summary: Boot errors should hide the failure description if the failing operation is not accessible (was: Boot errors should hide the failure description if the failing operation address is not accessible) > Boot errors should hide the failure description if the failing operation is not accessible > ------------------------------------------------------------------------------------------ > > Key: WFCORE-769 > URL: https://issues.jboss.org/browse/WFCORE-769 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.Alpha4 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > The boot error collector reports whatever failure-description it was passed. Those can include pretty random info, and there's no good way to know what,so it could leak some sensitive information. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-773) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor

by Enrique González Martínez (JIRA)

Enrique González Martínez created WFCORE-773: ------------------------------------------------ Summary: ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor Key: WFCORE-773 URL: https://issues.jboss.org/browse/WFCORE-773 Project: WildFly Core Issue Type: Bug Reporter: Enrique González Martínez Assignee: Enrique González Martínez BoundedQueueThreadPool does not support zero length queue setup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 June 2015