August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1200) CachedConnectionManager should only lock if needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1200?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1200: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1130385|https://bugzilla.redhat.com/show_bug.cgi?id=1130385] from NEW to POST > CachedConnectionManager should only lock if needed > -------------------------------------------------- > > Key: JBJCA-1200 > URL: https://issues.jboss.org/browse/JBJCA-1200 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta3 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3704) WebSocket Sessions must be manually closed

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3704?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3704: -------------------------------------- I think it may already be fixed upstream as part of WFLY-3490, I have just not got around to verifying it yet. > WebSocket Sessions must be manually closed > ------------------------------------------ > > Key: WFLY-3704 > URL: https://issues.jboss.org/browse/WFLY-3704 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Cody Lerum > Assignee: Stuart Douglas > Labels: websockets > > Currently if a WebSocket session goes inactive due to the browser shutting down or the user closing a tab the browser does not send a close event to the server. This behavior seems the same with Chrome and IE. > The underlying TCP socket is however inactive and can be confirmed by calling a Session#isOpen which returns false. This will cause a build up of sessions unless the user does something like > {code} > for (Session session : sessions) { > if (!session.isOpen()) { > session.close(); > } > } > {code} > This would need to be done periodically by the application. Shouldn't the server automatically close these sessions when the underlying socket goes inactive? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3704) WebSocket Sessions must be manually closed

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3704?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-3704: ---------------------------------- Might be related to WFLY-3490 > WebSocket Sessions must be manually closed > ------------------------------------------ > > Key: WFLY-3704 > URL: https://issues.jboss.org/browse/WFLY-3704 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Cody Lerum > Assignee: Stuart Douglas > Labels: websockets > > Currently if a WebSocket session goes inactive due to the browser shutting down or the user closing a tab the browser does not send a close event to the server. This behavior seems the same with Chrome and IE. > The underlying TCP socket is however inactive and can be confirmed by calling a Session#isOpen which returns false. This will cause a build up of sessions unless the user does something like > {code} > for (Session session : sessions) { > if (!session.isOpen()) { > session.close(); > } > } > {code} > This would need to be done periodically by the application. Shouldn't the server automatically close these sessions when the underlying socket goes inactive? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3704) WebSocket Sessions must be manually closed

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3704?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-3704: ---------------------------------- [~swd847] Were you able to find anything on this, or did you need more detail? > WebSocket Sessions must be manually closed > ------------------------------------------ > > Key: WFLY-3704 > URL: https://issues.jboss.org/browse/WFLY-3704 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Cody Lerum > Assignee: Stuart Douglas > Labels: websockets > > Currently if a WebSocket session goes inactive due to the browser shutting down or the user closing a tab the browser does not send a close event to the server. This behavior seems the same with Chrome and IE. > The underlying TCP socket is however inactive and can be confirmed by calling a Session#isOpen which returns false. This will cause a build up of sessions unless the user does something like > {code} > for (Session session : sessions) { > if (!session.isOpen()) { > session.close(); > } > } > {code} > This would need to be done periodically by the application. Shouldn't the server automatically close these sessions when the underlying socket goes inactive? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3735) Update JSF based on Mojarra 2.2.8

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3735?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-3735: ---------------------------------- Also backport to 8.x > Update JSF based on Mojarra 2.2.8 > --------------------------------- > > Key: WFLY-3735 > URL: https://issues.jboss.org/browse/WFLY-3735 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JSF > Reporter: Cody Lerum > Assignee: Jason Greene > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > Please upgrade mojarra to the recently released 2.2.8. This has fixes for @ViewScoped which have been delaying it's usage. > https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16964 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3735) Update JSF based on Mojarra 2.2.8

by Cody Lerum (JIRA)

Cody Lerum created WFLY-3735: -------------------------------- Summary: Update JSF based on Mojarra 2.2.8 Key: WFLY-3735 URL: https://issues.jboss.org/browse/WFLY-3735 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Cody Lerum Assignee: Jason Greene Fix For: 8.2.0.CR1, 9.0.0.Beta1 Please upgrade mojarra to the recently released 2.2.8. This has fixes for @ViewScoped which have been delaying it's usage. https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16964 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3735) Update JSF based on Mojarra 2.2.8

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3735?page=com.atlassian.jira.plugin.... ] Cody Lerum updated WFLY-3735: ----------------------------- Component/s: JSF > Update JSF based on Mojarra 2.2.8 > --------------------------------- > > Key: WFLY-3735 > URL: https://issues.jboss.org/browse/WFLY-3735 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JSF > Reporter: Cody Lerum > Assignee: Jason Greene > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > > Please upgrade mojarra to the recently released 2.2.8. This has fixes for @ViewScoped which have been delaying it's usage. > https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16964 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1208) Eclipse plugin update for IronJacamar 1.2

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1208?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1208: --------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/220 > Eclipse plugin update for IronJacamar 1.2 > ----------------------------------------- > > Key: JBJCA-1208 > URL: https://issues.jboss.org/browse/JBJCA-1208 > Project: IronJacamar > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Eclipse > Reporter: Lin Gao > Assignee: Lin Gao > > Differences between resource_adapters_1_1.xsd and resource_adapters_1_2.xsd are: > * Boolean 'connectable' attribute added: "Defines if external components can obtain a connection through the IronJacamar SPI if supported by the resource adapter" > * Boolean 'tracking' attribute added: "Defines if IronJacamar should track connection handles across transaction boundaries" > * Boolean 'validate-on-match' element added: "indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[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 commented on WFLY-3468: ----------------------------------------------- James Livingston <jlivings(a)redhat.com> changed the Status of [bug 1106393|https://bugzilla.redhat.com/show_bug.cgi?id=1106393] from NEW to ASSIGNED > 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: Emanuel Muckenhuber > 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.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-854) Fallback to FORM authentication when an invalid kerberos token is used

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-854?page=com.atlassian.jira.plug... ] Derek Horton updated SECURITY-854: ---------------------------------- Steps to Reproduce: Get a token from a different KDC than what JBoss is configured to use. Hit a Negotiation protected endpoint. This will result in a 401. With the patch applied, it is possible to fallback to form authentication. Git Pull Request: https://github.com/wildfly-security/jboss-negotiation/pull/19 > Fallback to FORM authentication when an invalid kerberos token is used > ---------------------------------------------------------------------- > > Key: SECURITY-854 > URL: https://issues.jboss.org/browse/SECURITY-854 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Derek Horton > Assignee: Derek Horton > > Negotiation will not fallback to FORM authentication if the client has a kerberos token from a different KDC than what JBoss is configured to use. > This results in the user getting presented with a 401 error and no way to login. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 August 2014