May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1553) data.dir not cleaned up correctly

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1553?page=com.atlassian.jira.plugi... ] Heiko Braun moved SWARM-459 to WFCORE-1553: ------------------------------------------- Project: WildFly Core (was: WildFly Swarm) Key: WFCORE-1553 (was: SWARM-459) Component/s: Server (was: core) > data.dir not cleaned up correctly > --------------------------------- > > Key: WFCORE-1553 > URL: https://issues.jboss.org/browse/WFCORE-1553 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Heiko Braun > > When running the examples and shutting down the server, certain files remain in the tmp.dir. > Steps to reproduce: > 1) cd examples; mvn install > 2) java -Djava.io.tmpdir=servlet/servlet-cdi/target/test-tmp -jar servlet/servlet-cdi/target/example-servlet-cdi-swarm.jar > 3) du -ch servlet/servlet-cdi/target/test-tmp > This leaves us with: > {noformat} > hbraun:~/dev/prj/wfs/wildfly-swarm-examples (1.0.0.Beta8)$ du -ch servlet/servlet-cdi/target/test-tmp > 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/kernel > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore/defaultStore > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store > 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d > 4.0K servlet/servlet-cdi/target/test-tmp > 4.0K total > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1553) data.dir not cleaned up correctly

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1553?page=com.atlassian.jira.plugi... ] Heiko Braun commented on WFCORE-1553: ------------------------------------- [~brian.stansberry] is core the right place for this? > data.dir not cleaned up correctly > --------------------------------- > > Key: WFCORE-1553 > URL: https://issues.jboss.org/browse/WFCORE-1553 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Heiko Braun > > When running the examples and shutting down the server, certain files remain in the tmp.dir. > Steps to reproduce: > 1) cd examples; mvn install > 2) java -Djava.io.tmpdir=servlet/servlet-cdi/target/test-tmp -jar servlet/servlet-cdi/target/example-servlet-cdi-swarm.jar > 3) du -ch servlet/servlet-cdi/target/test-tmp > This leaves us with: > {noformat} > hbraun:~/dev/prj/wfs/wildfly-swarm-examples (1.0.0.Beta8)$ du -ch servlet/servlet-cdi/target/test-tmp > 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/kernel > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore/defaultStore > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store/ShadowNoFileLockStore > 0B servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d/tx-object-store > 4.0K servlet/servlet-cdi/target/test-tmp/wildfly-self-contained7234196008976901496.d > 4.0K servlet/servlet-cdi/target/test-tmp > 4.0K total > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6524) Upgrade Netty to 4.0.33.Final

by Radim Chlad (JIRA)

[ https://issues.jboss.org/browse/WFLY-6524?page=com.atlassian.jira.plugin.... ] Radim Chlad commented on WFLY-6524: ----------------------------------- netty 4 is already at 4.0.36 - isn't it worth upgrading up-to-date? [http://netty.io/news/2016/04/04/4-0-36-Final.html] > Upgrade Netty to 4.0.33.Final > ----------------------------- > > Key: WFLY-6524 > URL: https://issues.jboss.org/browse/WFLY-6524 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.1.0.Final > > > Upgrading Netty to 4.0.33 should resolve https://issues.jboss.org/browse/JBEAP-4220 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6599) JDBC_PING can't use a JNDI database connection because it is closed on shutdown

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6599?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6599: -------------------------------------- See JGRP-2063 for changes that need to be done in JGroups directly. > JDBC_PING can't use a JNDI database connection because it is closed on shutdown > ------------------------------------------------------------------------------- > > Key: WFLY-6599 > URL: https://issues.jboss.org/browse/WFLY-6599 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Matthew Casperson > Assignee: Radoslav Husar > > If you configure the JDBC_PING protocol in JGroups to use a datasource provided by WildFly via the *datasource_jndi_name* setting, you'll get the following exception when WildFly is shutdown: > {code} > [Server:main-server] 2016-05-10 11:05:45+1000 ERROR [[org.jgroups.protocols.JDBC_PING]] [[MSC service thread 1-4]] Could not open connection to database: java.sql.SQLException: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups > [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146) > [Server:main-server] at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66) > [Server:main-server] at org.jgroups.protocols.JDBC_PING.getConnection(JDBC_PING.java:348) > [Server:main-server] at org.jgroups.protocols.JDBC_PING.delete(JDBC_PING.java:379) > [Server:main-server] at org.jgroups.protocols.JDBC_PING.deleteSelf(JDBC_PING.java:395) > [Server:main-server] at org.jgroups.protocols.JDBC_PING.stop(JDBC_PING.java:144) > [Server:main-server] at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:1015) > [Server:main-server] at org.jgroups.JChannel.stopStack(JChannel.java:1002) > [Server:main-server] at org.jgroups.JChannel.disconnect(JChannel.java:373) > [Server:main-server] at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.stop(ChannelConnectorBuilder.java:103) > [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > [Server:main-server] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:main-server] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:main-server] at java.lang.Thread.run(Thread.java:745) > [Server:main-server] Caused by: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups > [Server:main-server] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:735) > [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138) > [Server:main-server] ... 14 more > {code} > The solution is to configure the database connection directly, but then it seems that you loose the ability to use features like database connection validation, reconnection and the other settings provided by a WildFly datasource the improve the reliability of a database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3532) RemoteFailoverTestCase still fails intermittently

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3532?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-3532: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > RemoteFailoverTestCase still fails intermittently > -------------------------------------------------- > > Key: WFLY-3532 > URL: https://issues.jboss.org/browse/WFLY-3532 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: clean_undeploy > Fix For: 10.1.0.Final > > > Fail rate is at 1.5% atm. > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF&testNameI... > (making affected version alpha, but indeed its master) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2063: --------------------------------- Summary: JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) (was: JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook)) > JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) > ------------------------------------------------------------------------------------ > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2063: --------------------------------- Affects Version/s: 3.6.9 > JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook) > ----------------------------------------------------------------------------- > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned JGRP-2063: ------------------------------------ Assignee: Radoslav Husar (was: Bela Ban) > JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook) > ----------------------------------------------------------------------------- > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook)

by Radoslav Husar (JIRA)

Radoslav Husar created JGRP-2063: ------------------------------------ Summary: JDBC_PING: allow providing dataSource directly (e.g. via after_creation_hook) Key: JGRP-2063 URL: https://issues.jboss.org/browse/JGRP-2063 Project: JGroups Issue Type: Feature Request Reporter: Radoslav Husar Assignee: Bela Ban See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1481) list-add operation doesn't work on login-modules attribute

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1481?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1481: ------------------------------------------ I closed the PR I mentioned in my last comment. I get what the test is doing and it's not contrived and not mistaken. It's just validating that a normal Storage.CONFIGURATION attribute with a handler that updates the runtime works properly, all the way through to updating the runtime. > list-add operation doesn't work on login-modules attribute > ---------------------------------------------------------- > > Key: WFCORE-1481 > URL: https://issues.jboss.org/browse/WFCORE-1481 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Tomas Hofman > > Executing list-add operation on login-modules results in the modules being replaced instead of appending new module. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016