November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5641) Cleanup is not done properly after test have finished

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5641?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-5641: ---------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Cleanup is not done properly after test have finished > ----------------------------------------------------- > > Key: WFLY-5641 > URL: https://issues.jboss.org/browse/WFLY-5641 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Ivan Straka > Assignee: Radoslav Husar > Priority: Minor > > There are several tests failing because cleanup process was not done properly. > This can be caused by ibmjdk1.8 that do not run test in different order. Therefore problem is shown. > two exceptions: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... > whole run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5642) RejectedExecutionException when deploying in test org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase.testGracefulServeOnUndeploy

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5642?page=com.atlassian.jira.plugin.... ] Paul Ferraro resolved WFLY-5642. -------------------------------- Fix Version/s: 10.0.0.Final Resolution: Done > RejectedExecutionException when deploying in test org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase.testGracefulServeOnUndeploy > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5642 > URL: https://issues.jboss.org/browse/WFLY-5642 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Ivan Straka > Assignee: Paul Ferraro > Labels: clean_undeploy > Fix For: 10.0.0.Final > > > org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase is failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... && x86_64 && eap-sustaining/testReport/org.jboss.as.test.clustering.cluster.web/ClusteredWebSimpleTestCase(SYNC-tcp)/testGracefulServeOnUndeploy/ > WARN [org.wildfly.clustering.web.infinispan] (default task-18) WFLYCLWEBINF0006: Failed to schedule expiration/passivation of session PShvmFq6MDIrMz1wZP6MwVHydgu6_EMrtMyLm_x6 on primary owner.: java.util.concurrent.ExecutionException: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@24aaa062 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@2095202f[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] > at org.wildfly.clustering.server.dispatcher.SimpleCommandResponse.<init>(SimpleCommandResponse.java:43) > at org.wildfly.clustering.server.dispatcher.LocalCommandDispatcher.executeOnNode(LocalCommandDispatcher.java:82) > at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcher.executeOnNode(ChannelCommandDispatcher.java:146) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.lambda$executeOnPrimaryOwner$5(InfinispanSessionManager.java:195) > at org.wildfly.clustering.ee.infinispan.RetryingInvoker.invoke(RetryingInvoker.java:70) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.executeOnPrimaryOwner(InfinispanSessionManager.java:192) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.schedule(InfinispanSessionManager.java:185) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.close(InfinispanSessionManager.java:462) > at org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:75) > at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:767) > at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:554) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:331) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:198) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:788) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@24aaa062 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@2095202f[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) > at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326) > at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533) > at org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler.schedule(SessionExpirationScheduler.java:101) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$1.lambda$schedule$0(InfinispanSessionManager.java:138) > at java.util.ArrayList.forEach(ArrayList.java:1249) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$1.schedule(InfinispanSessionManager.java:138) > at org.wildfly.clustering.web.infinispan.session.ScheduleSchedulerCommand.execute(ScheduleSchedulerCommand.java:48) > at org.wildfly.clustering.web.infinispan.session.ScheduleSchedulerCommand.execute(ScheduleSchedulerCommand.java:35) > at org.wildfly.clustering.server.dispatcher.LocalCommandDispatcher.executeOnNode(LocalCommandDispatcher.java:80) > ... 18 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1294) caching the value of isTraceEnabled

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1294?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1294: ----------------------------------- Fix Version/s: 1.0.35.Final (was: 1.0.34.Final) > caching the value of isTraceEnabled > ----------------------------------- > > Key: JBJCA-1294 > URL: https://issues.jboss.org/browse/JBJCA-1294 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.2.6.Final > Reporter: Johnathon Lee > Assignee: Bartosz Baranowski > Fix For: WildFly/IronJacamar 1.3.2.Final, 1.0.35.Final > > > caching the value of isTraceEnabled does not allow for complete dynamic control of the logging level. This has ramifications in support scenarios where diagnostics are needed and the ability to reload an instance to enable TRACE level logging is prohibitive. > see examples of TRACE being cached: > grep 'log.isTraceEnabled();' -r * --include='*.java' > Replacement of all if (trace) with calls to log.tracef would be needed. > Note, that some "if (trace)" would have to be replaced by if (log.isTraceEnabled()) calls, as they guard multiple lines of code, and even synchronization blocks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1297) Verify if a SQLException is fatal in all methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1297?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1297: ------------------------------------------------ Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1271806|https://bugzilla.redhat.com/show_bug.cgi?id=1271806] from POST to MODIFIED > Verify if a SQLException is fatal in all methods > ------------------------------------------------ > > Key: JBJCA-1297 > URL: https://issues.jboss.org/browse/JBJCA-1297 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.1.Final, 1.2.6.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: WildFly/IronJacamar 1.3.2.Final, 1.2.7.Final > > > WrappedConnection: > * setTransactionIsolation > * commit > * rollback > * setClientInfo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1276) Prefill race condition in flush

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1276?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1276: ------------------------------------------------ Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1231658|https://bugzilla.redhat.com/show_bug.cgi?id=1231658] from ASSIGNED to MODIFIED > Prefill race condition in flush > ------------------------------- > > Key: JBJCA-1276 > URL: https://issues.jboss.org/browse/JBJCA-1276 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.31.Final, 1.1.9.Final > Reporter: Takayoshi Kimura > Assignee: Jesper Pedersen > Fix For: 1.0.33.Final > > Attachments: server.log > > > There is a race condition between AbstractPool and SemaphoreArrayListManagedConnectionPool. > https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.31.Final/... > https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.31.Final/... > AbstractPool flushes the mcp, mcp invokes PoolFiller which works in a separate thread. However AbstractPool is going to unregister the empty mcp and this mcp is no longer used. Then the dead mcp is prefilled in a separate thread by PoolFiller. > At next getConnection(), the mcp is re-initialized and prefilled. > I've attached logs, prefill enabled and min-size is 10. Boot server, invoke flush-all-connection-in-pool, getConnection() then killed. The prefill is done 3 times where it should be twice. > {noformat} > 16:26:04,254 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 1) ExampleDS: flush(true) > 16:26:04,255 TRACE [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 1) Destroying flushed connection org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1d298ed8[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@4ae26a1b connection handles=0 lastUse=1434353148384 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@56a43905 pool internal context=SemaphoreArrayListManagedConnectionPool@5cbd770e[pool=ExampleDS] xaResource=LocalXAResourceImpl@379ba3b3[connectionListener=1d298ed8 connectionManager=4b18594a warned=false currentXid=null productName=H2 productVersion=@PROJECT_VERSION@ (2012-07-13) jndiName=java:jboss/datasources/ExampleDS] txSync=null] > (repeat 10 times) > 16:02:20,666 TRACE [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 7) Shutdown - Pool: ExampleDS MCP: 2f5a2102 > 16:02:20,666 TRACE [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (JCA PoolFiller) Using properties: {user=sa, password=--hidden--} > 16:02:20,666 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (management-handler-thread - 7) Unregister pool: SemaphoreArrayListManagedConnectionPool@2f5a2102[pool=ExampleDS] > 16:26:04,259 TRACE [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) Filling pool cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@34f0bb27[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@288f1898 connection handles=0 lastUse=1434353164259 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@56a43905 pool internal context=SemaphoreArrayListManagedConnectionPool@5cbd770e[pool=ExampleDS] xaResource=LocalXAResourceImpl@4a97b7f5[connectionListener=34f0bb27 connectionManager=4b18594a warned=false currentXid=null productName=H2 productVersion=@PROJECT_VERSION@ (2012-07-13) jndiName=java:jboss/datasources/ExampleDS] txSync=null] > (repeat 10 times) > 16:26:11,342 TRACE [org.jboss.jca.core.connectionmanager.TxConnectionManager] (http-/127.0.0.1:8080-1) getManagedConnection interleaving=false , tx=null > 16:26:11,343 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (http-/127.0.0.1:8080-1) Register pool: SemaphoreArrayListManagedConnectionPool@1d4ae61f[pool=ExampleDS] (interval=1800000) > 16:26:11,344 TRACE [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) Filling pool cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1c706b4d[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@18949ad1 connection handles=0 lastUse=1434353171343 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@56a43905 pool internal context=SemaphoreArrayListManagedConnectionPool@1d4ae61f[pool=ExampleDS] xaResource=LocalXAResourceImpl@44401bf2[connectionListener=1c706b4d connectionManager=4b18594a warned=false currentXid=null productName=H2 productVersion=@PROJECT_VERSION@ (2012-07-13) jndiName=java:jboss/datasources/ExampleDS] txSync=null] > (repeat 10 times) > {noformat} > In 1.0.31.Final: > > if (mcp.isEmpty()) > > clearMcpPools.add(mcp); > In 1.2 branch it looks like already fixed within commit 956af09c8494d4187db24a253e7e37b5ba5d9779 for JBJCA-1135: > > if (mcp.isEmpty() && !isPrefill() && size > 1) > > clearMcpPools.add(mcp); > We probably need to backport "!isPrefill()" to the 1.0/1.1 branch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5471) Expose Infinispan's replicationQueue thread pool configuration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5471?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5471. -------------------------------- Resolution: Won't Do The thread pool is scheduled to be deprecated and eventually go away. Will not do. > Expose Infinispan's replicationQueue thread pool configuration > -------------------------------------------------------------- > > Key: WFLY-5471 > URL: https://issues.jboss.org/browse/WFLY-5471 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Final > > > Still exposed and still not deprecated. We may need to support it and carry the burden of it around. > https://github.com/infinispan/infinispan/blob/8.0.x/core/src/main/java/or... > https://github.com/infinispan/infinispan/blob/8.0.x/core/src/main/java/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5650) Cancel button in JConsole do nothing

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-5650?page=com.atlassian.jira.plugin.... ] Marek Kopecký moved JBEAP-1802 to WFLY-5650: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5650 (was: JBEAP-1802) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: CLI Scripts (was: Scripts) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.DR13 (Alpha)) > Cancel button in JConsole do nothing > ------------------------------------ > > Key: WFLY-5650 > URL: https://issues.jboss.org/browse/WFLY-5650 > Project: WildFly > Issue Type: Bug > Components: CLI, Scripts > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Cancel button in JConsole do nothing. It should be removed from JConsole > *How reproducible:* > Always > *Steps to Reproduce:* > # cd EAP_HOME > # ./bin/standalone.sh & > # ./bin/jconsole.sh > # Click to CLI tab > # Click to "Cancel" button -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5649) Export JSON-P API packages

by Pavel Jelinek (JIRA)

[ https://issues.jboss.org/browse/WFLY-5649?page=com.atlassian.jira.plugin.... ] Pavel Jelinek moved JBEAP-1800 to WFLY-5649: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5649 (was: JBEAP-1800) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: (was: Modules) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.DR13 (Alpha)) > Export JSON-P API packages > -------------------------- > > Key: WFLY-5649 > URL: https://issues.jboss.org/browse/WFLY-5649 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR4 > Reporter: Pavel Jelinek > Assignee: James Perkins > > The javax.json.api module should be public, but rather than have it be > an alias, it should be an empty module which re-exports the public API > packages of the non-public org.glassfish.javax.json module. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1836) manual module SSLEJBRemoteClientTestCase keeps freezing

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1836?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-1836: --------------------------------- Assignee: Tomaz Cerar (was: JBoss SET) > manual module SSLEJBRemoteClientTestCase keeps freezing > ------------------------------------------------------- > > Key: WFLY-1836 > URL: https://issues.jboss.org/browse/WFLY-1836 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Bartosz Baranowski > Assignee: Tomaz Cerar > > CI job keeps freezing on this test. In local run, it does not fail however: > execution in batch: 102s+ > standalone : ~45s -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1297) Verify if a SQLException is fatal in all methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1297?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1297: ------------------------------------------------ Bartek Spyrko-Smietanko <bspyrkos(a)redhat.com> changed the Status of [bug 1271806|https://bugzilla.redhat.com/show_bug.cgi?id=1271806] from ASSIGNED to POST > Verify if a SQLException is fatal in all methods > ------------------------------------------------ > > Key: JBJCA-1297 > URL: https://issues.jboss.org/browse/JBJCA-1297 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.1.Final, 1.2.6.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: WildFly/IronJacamar 1.3.2.Final, 1.2.7.Final > > > WrappedConnection: > * setTransactionIsolation > * commit > * rollback > * setClientInfo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015