June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3468) Managed server shutdown unexpectedly when timeout during connection request to HC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3468?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3468: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1106393 > Managed server shutdown unexpectedly when timeout during connection request to HC > --------------------------------------------------------------------------------- > > Key: WFLY-3468 > URL: https://issues.jboss.org/browse/WFLY-3468 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.Final > Reporter: Takayoshi Kimura > Assignee: Brian Stansberry > Priority: Minor > > Sometimes managed server shutdown unexpectedly when managed server tries to connect to the HC and got lengthly Full GC. > {quote} > java.io.IOException: JBAS012175: Channel closed > at org.jboss.as.server.mgmt.domain.HostControllerConnection.getChannel(HostControllerConnection.java:101) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:100) > at org.jboss.as.server.mgmt.domain.HostControllerConnection.reConnect(HostControllerConnection.java:171) > at org.jboss.as.server.mgmt.domain.HostControllerClient.reconnect(HostControllerClient.java:98) > at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:138) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:292) > at org.jboss.modules.Main.main(Main.java:455) > {quote} > The current DomainServerMain exits on the connetion error. > The scenario is: > # server tries to connect to the HC > # server Full GC > # HC is waiting a request from server, read timeout, closes the sock > # server resumed from GC, failed to send the req to the HC and exit -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3468) Managed server shutdown unexpectedly when timeout during connection request to HC

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created WFLY-3468: -------------------------------------- Summary: Managed server shutdown unexpectedly when timeout during connection request to HC Key: WFLY-3468 URL: https://issues.jboss.org/browse/WFLY-3468 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.1.0.Final Reporter: Takayoshi Kimura Assignee: Brian Stansberry Priority: Minor Sometimes managed server shutdown unexpectedly when managed server tries to connect to the HC and got lengthly Full GC. {quote} java.io.IOException: JBAS012175: Channel closed at org.jboss.as.server.mgmt.domain.HostControllerConnection.getChannel(HostControllerConnection.java:101) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:100) at org.jboss.as.server.mgmt.domain.HostControllerConnection.reConnect(HostControllerConnection.java:171) at org.jboss.as.server.mgmt.domain.HostControllerClient.reconnect(HostControllerClient.java:98) at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.modules.Module.run(Module.java:292) at org.jboss.modules.Main.main(Main.java:455) {quote} The current DomainServerMain exits on the connetion error. The scenario is: # server tries to connect to the HC # server Full GC # HC is waiting a request from server, read timeout, closes the sock # server resumed from GC, failed to send the req to the HC and exit -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-224) MethodParameters attribute support

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-224?page=com.atlassian.jira.plugi... ] Shigeru Chiba updated JASSIST-224: ---------------------------------- Description: An attribute recording the formal parameter names of a method. > MethodParameters attribute support > ---------------------------------- > > Key: JASSIST-224 > URL: https://issues.jboss.org/browse/JASSIST-224 > Project: Javassist > Issue Type: Feature Request > Affects Versions: 3.18.2-GA > Reporter: Shigeru Chiba > Assignee: Shigeru Chiba > > An attribute recording the formal parameter names of a method. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-224) MethodParameters attribute support

by Shigeru Chiba (JIRA)

Shigeru Chiba created JASSIST-224: ------------------------------------- Summary: MethodParameters attribute support Key: JASSIST-224 URL: https://issues.jboss.org/browse/JASSIST-224 Project: Javassist Issue Type: Feature Request Affects Versions: 3.18.2-GA Reporter: Shigeru Chiba Assignee: Shigeru Chiba -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3453) Caused by: java.lang.IllegalArgumentException: Cookie name "path" is a reserved token

by shaik masthan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3453?page=com.atlassian.jira.plugin.... ] shaik masthan commented on WFLY-3453: ------------------------------------- hi, could you provide the workaround > Caused by: java.lang.IllegalArgumentException: Cookie name "path" is a reserved token > ------------------------------------------------------------------------------------- > > Key: WFLY-3453 > URL: https://issues.jboss.org/browse/WFLY-3453 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final, 8.1.0.Final > Environment: windows 2003,flex with java(servlets) > Reporter: shaik masthan > Assignee: Stuart Douglas > Fix For: 8.0.0.Final, 8.1.0.Final > > > i am getting the below error when trying to access or open the UI page (developed using flex) .it was properly working in tomcat version. recently migrated from tomcat to wildfly 8.0.0 Final. > Caused by: java.lang.IllegalArgumentException: Cookie name "path" is a reserved token > at javax.servlet.http.Cookie.<init>(Cookie.java:192) > at io.undertow.servlet.spec.HttpServletRequestImpl.getCookies(HttpServletRequestImpl.java:145) > at com.ap.ca.mm.util.SessionUtils.getSessionManagerPrincipal(SessionUtils.java:128) > at com.ap.ca.mm.util.SessionUtils.getRmpPrincipalFromSessionManagerBean(SessionUtils.java:166) > at com.ap.ca.mm.util.SessionUtils.getRmpPrincipal(SessionUtils.java:96) > at com.ap.ca.mm.ro.dao.csdb.EntityDAO.<init>(EntityDAO.java:149) > ... 42 more -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3460) Async servlet: HttpServletResponse.sendError() throws UT000048 if error page set

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3460?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3460: -------------------------------------- Fixed in Undertow, should be in WF soon > Async servlet: HttpServletResponse.sendError() throws UT000048 if error page set > -------------------------------------------------------------------------------- > > Key: WFLY-3460 > URL: https://issues.jboss.org/browse/WFLY-3460 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Windows 7 Professional, Java 7u55 > Reporter: Darren Jones > Assignee: Stuart Douglas > Attachments: AsyncTest.war, AsyncTestSrc.zip > > > If an async servlet calls sendError(...) when an <error-page> is added to the web.xml, the exception below occurs. If the <error-page> is removed (not possible for me), the servlet works just fine. > Exception in thread "default task-29" java.lang.IllegalStateException: UT000048: No request is currently active > at io.undertow.servlet.handlers.ServletRequestContext.requireCurrent(ServletRequestContext.java:63) > at io.undertow.servlet.spec.SecurityActions.requireCurrentServletRequestContext(SecurityActions.java:86) > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:324) > at io.undertow.servlet.spec.RequestDispatcherImpl.error(RequestDispatcherImpl.java:311) > at io.undertow.servlet.spec.HttpServletResponseImpl.sendError(HttpServletResponseImpl.java:128) > at TestAsyncServlet$1.run(TestAsyncServlet.java:25) > at io.undertow.servlet.spec.AsyncContextImpl$4.run(AsyncContextImpl.java:309) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3466) No error reported when remote handshake fails

by Paul Benedict (JIRA)

[ https://issues.jboss.org/browse/WFLY-3466?page=com.atlassian.jira.plugin.... ] Paul Benedict commented on WFLY-3466: ------------------------------------- Both containers are WildFly 8.0.1.CR2 containers. I followed the instructions here: https://docs.jboss.org/author/display/WFLY8/EJB+invocations+from+a+remote... I did link to my message board post that described this issue in more detail. I did everything to a T -- no deviations from the wiki instructions. > No error reported when remote handshake fails > --------------------------------------------- > > Key: WFLY-3466 > URL: https://issues.jboss.org/browse/WFLY-3466 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Remoting > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Paul Benedict > Assignee: David Lloyd > > When the destination server fails to respond and thus the remote handshake cannot be made, nothing gets reported in the client's log -- even when put on TRACE. I spent many days trying to get to the bottom of this. This abnormal condition is too important for it to go unreported. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3466) No error reported when remote handshake fails

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3466?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3466: ----------------------------------- Okay then, so what configurations are you using on the client and the server? Is the client a WildFly container, or is it a standalone program? > No error reported when remote handshake fails > --------------------------------------------- > > Key: WFLY-3466 > URL: https://issues.jboss.org/browse/WFLY-3466 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Remoting > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Paul Benedict > Assignee: David Lloyd > > When the destination server fails to respond and thus the remote handshake cannot be made, nothing gets reported in the client's log -- even when put on TRACE. I spent many days trying to get to the bottom of this. This abnormal condition is too important for it to go unreported. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-519) Accumulate CollectList does not preserve the insertion order

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-519?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-519: --------------------------------------- (This report is intended to address future inquiries on the topic) > Accumulate CollectList does not preserve the insertion order > ------------------------------------------------------------ > > Key: DROOLS-519 > URL: https://issues.jboss.org/browse/DROOLS-519 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta4 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > > In 5.x, acc / collectList preserves the order of insertion. > That is, if A1, A2 and A3 are inserted, a collectList will return 1,2,3 > In 6.x, the order is reversed. That is, in the same scenario, a list > with 3,2,1 is generated. > While arguably a minor issue, collectList returns a list, that is an ordered > collection. The reversal of the order breaks the compatibility of preexising > applications (such as drools-mas) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-519) Accumulate CollectList does not preserve the insertion order

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-519?page=com.atlassian.jira.plugin... ] Davide Sottara closed DROOLS-519. --------------------------------- Assignee: Davide Sottara (was: Mark Proctor) Resolution: Won't Fix The ordering crtieria was never part of the original contract, so applications should not rely on it. More specific behaviors should be implemented as different acc functions (which are pluggable) and committed > Accumulate CollectList does not preserve the insertion order > ------------------------------------------------------------ > > Key: DROOLS-519 > URL: https://issues.jboss.org/browse/DROOLS-519 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta4 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > > In 5.x, acc / collectList preserves the order of insertion. > That is, if A1, A2 and A3 are inserted, a collectList will return 1,2,3 > In 6.x, the order is reversed. That is, in the same scenario, a list > with 3,2,1 is generated. > While arguably a minor issue, collectList returns a list, that is an ordered > collection. The reversal of the order breaks the compatibility of preexising > applications (such as drools-mas) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 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 2014