October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-150) Undefining suffix on size-rotating-file-handler sets invalid value on suffix

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-150?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-3946 to WFCORE-150: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-150 (was: WFLY-3946) Component/s: Logging (was: Logging) > Undefining suffix on size-rotating-file-handler sets invalid value on suffix > ---------------------------------------------------------------------------- > > Key: WFCORE-150 > URL: https://issues.jboss.org/browse/WFCORE-150 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When the suffix is undefined ({{undefine-attribute(name=suffix)}}) on a {{size-rotating-file-handler}} the value {{undefined}} gets written to the suffix which is invalid. The value needs to be set to null if undefined. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-1470: ------------------------------------ Another: server/src/main/java/org/jboss/as/server/deployment/module/MountHandle.java This looks ok (but might stall the finalizer thread) controller-client/src/main/java/org/jboss/as/controller/client/impl/RemotingModelControllerClient.java > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3946) Undefining suffix on size-rotating-file-handler sets invalid value on suffix

by James Perkins (JIRA)

James Perkins created WFLY-3946: ----------------------------------- Summary: Undefining suffix on size-rotating-file-handler sets invalid value on suffix Key: WFLY-3946 URL: https://issues.jboss.org/browse/WFLY-3946 Project: WildFly Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins When the suffix is undefined ({{undefine-attribute(name=suffix)}}) on a {{size-rotating-file-handler}} the value {{undefined}} gets written to the suffix which is invalid. The value needs to be set to null if undefined. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-141) Update file based keystore services to use the registered PathManagerService

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-141?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved WFCORE-141. ------------------------------------- Resolution: Done > Update file based keystore services to use the registered PathManagerService > ---------------------------------------------------------------------------- > > Key: WFCORE-141 > URL: https://issues.jboss.org/browse/WFCORE-141 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-1470: ------------------------------------ Another: jacorb/src/main/java/org/jboss/as/jacorb/naming/jndi/CNBindingEnumeration.java > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1470: ------------------------------- Summary: Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) (was: Usage of finalize() needs extra guards due to a flaw in the language features (mostly affects IBM)) > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language features (mostly affects IBM)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1470: ------------------------------- Summary: Usage of finalize() needs extra guards due to a flaw in the language features (mostly affects IBM) (was: Usage of finalize() needs extra guards on IBM JDK) > Usage of finalize() needs extra guards due to a flaw in the language features (mostly affects IBM) > -------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards on IBM JDK

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-1470: ------------------------------------ A patch has been sent in for remote-naming. Another occurrence of the problem is here: jacorb/src/main/java/org/jboss/as/jacorb/naming/jndi/CNCtx.java > Usage of finalize() needs extra guards on IBM JDK > ------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1149) Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1149?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-1149: ------------------------------------ The complete and correct fix, which can affect non-IBM JVMS has been submitted as a PR. > Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1149 > URL: https://issues.jboss.org/browse/WFLY-1149 > Project: WildFly > Issue Type: Bug > Components: Naming, Test Suite > Environment: IBM JDK 6 (build 20110203_074623) > IBM JDK 7 (build 20120809_118929) > Reporter: Ivo Studensky > Attachments: endpoint_is_not_open_2012-11-26.xml, failed_with_status_cancelled_2012-11-26.xml, test_output_with_trace_logging_in_EndpointCache.xml > > > RemoteNamingTestCase intermittently fails when running on IBM JDK. According to logs the remoting channel had been closed before the endpoint tried to connect to it. Unfortunately, when I was trying to debug this issue the tests always nicely passed. > test.log snippet: > {noformat} > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" read-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@345642e1 > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" write-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@1dc68cf2 > 13:16:31,121 DEBUG [org.jboss.naming.remote.client.InitialContextFactory] (main) jboss.naming.client.connect.options. has the following options {org.xnio.Options.SASL_POLICY_NOPLAINTEXT=>false} > 13:16:31,191 ERROR [org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1] (Remoting "config-based-naming-client-endpoint" task-1) Channel end notification received, closing channel Channel ID d1f17196 (outbound) of Remoting connection fd3dcedc to /127.0.0.1:4447 > 13:16:31,204 DEBUG [org.jboss.naming.remote.client.HaRemoteNamingStore] (main) Failed to connect to server remote://127.0.0.1:4447: org.jboss.remoting3.NotOpenException: Endpoint is not open > at org.jboss.remoting3.EndpointImpl.resourceUntick(EndpointImpl.java:182) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:261) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105) > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:179) > at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:117) > at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:223) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83) > at javax.naming.InitialContext.lookup(InitialContext.java:422) > at org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase.testRemoteLookup(RemoteNamingTestCase.java:74) > {noformat} > server.log snippet: > {noformat} > 13:16:31,025 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "test.jar" > 13:16:31,163 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-3) Channel Opened - Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 > 13:16:31,176 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-4) Chosen version 0x01 > 13:16:31,189 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" read-1) Channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 closed. > 13:16:31,193 INFO [org.jboss.as.naming] (Remoting "thinkpax" task-1) JBAS011806: Channel end notification received, closing channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to null > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1149) Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1149?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1149: ------------------------------- Git Pull Request: https://github.com/jbossas/jboss-remote-naming/pull/21, https://github.com/wildfly/wildfly/pull/6786 (was: https://github.com/jbossas/jboss-as/pull/3481, https://github.com/jbossas/jboss-as/pull/3482) > Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1149 > URL: https://issues.jboss.org/browse/WFLY-1149 > Project: WildFly > Issue Type: Bug > Components: Naming, Test Suite > Environment: IBM JDK 6 (build 20110203_074623) > IBM JDK 7 (build 20120809_118929) > Reporter: Ivo Studensky > Attachments: endpoint_is_not_open_2012-11-26.xml, failed_with_status_cancelled_2012-11-26.xml, test_output_with_trace_logging_in_EndpointCache.xml > > > RemoteNamingTestCase intermittently fails when running on IBM JDK. According to logs the remoting channel had been closed before the endpoint tried to connect to it. Unfortunately, when I was trying to debug this issue the tests always nicely passed. > test.log snippet: > {noformat} > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" read-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@345642e1 > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" write-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@1dc68cf2 > 13:16:31,121 DEBUG [org.jboss.naming.remote.client.InitialContextFactory] (main) jboss.naming.client.connect.options. has the following options {org.xnio.Options.SASL_POLICY_NOPLAINTEXT=>false} > 13:16:31,191 ERROR [org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1] (Remoting "config-based-naming-client-endpoint" task-1) Channel end notification received, closing channel Channel ID d1f17196 (outbound) of Remoting connection fd3dcedc to /127.0.0.1:4447 > 13:16:31,204 DEBUG [org.jboss.naming.remote.client.HaRemoteNamingStore] (main) Failed to connect to server remote://127.0.0.1:4447: org.jboss.remoting3.NotOpenException: Endpoint is not open > at org.jboss.remoting3.EndpointImpl.resourceUntick(EndpointImpl.java:182) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:261) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105) > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:179) > at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:117) > at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:223) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83) > at javax.naming.InitialContext.lookup(InitialContext.java:422) > at org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase.testRemoteLookup(RemoteNamingTestCase.java:74) > {noformat} > server.log snippet: > {noformat} > 13:16:31,025 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "test.jar" > 13:16:31,163 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-3) Channel Opened - Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 > 13:16:31,176 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-4) Chosen version 0x01 > 13:16:31,189 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" read-1) Channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 closed. > 13:16:31,193 INFO [org.jboss.as.naming] (Remoting "thinkpax" task-1) JBAS011806: Channel end notification received, closing channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to null > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 October 2014