November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4562) Deprecate Infinispan container/cache start mode

by xiaodong xie (JIRA)

[ https://issues.jboss.org/browse/WFLY-4562?page=com.atlassian.jira.plugin.... ] xiaodong xie commented on WFLY-4562: ------------------------------------ No, unfortunately, it does not work. I encountered the same issue with Wildfly-9.0.2... Set Infinispan module version in standalone.xml to 2.0 and set start='EAGER' do not help, the underlying value is still 'LAZY'. The workaround is to add <resource-env-ref> element as described at https://developer.jboss.org/thread/259151 > Deprecate Infinispan container/cache start mode > ----------------------------------------------- > > Key: WFLY-4562 > URL: https://issues.jboss.org/browse/WFLY-4562 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > start="EAGER" was only added to the Infinispan subsystem for use by JDG - so that a given container or cache service would install as ACTIVE rather than ON_DEMAND. In the context of WildFly, we would never want this since the modules referenced by cache entries may not yet be loaded. Many users configure start="EAGER" and inevitably have issues during redeploy. Consequently, we should drop this from the subsystem XSD altogether and deprecate it from the model. > Effectively, only start="LAZY" will be supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1108) Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1108?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-1108: ------------------------------------------- Since I can't reproduce, using java.nio.file.Files to get better exceptions. > Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory > ---------------------------------------------------------------------------------------- > > Key: WFCORE-1108 > URL: https://issues.jboss.org/browse/WFCORE-1108 > Project: WildFly Core > Issue Type: Bug > Environment: Wildfly 9.0.1 Final > Reporter: George Leon > Assignee: ehsavoie Hugonnet > > Hi all, > First Wildlfly is the best Bravo from Greece . > > > We have wildfly 9.0.1 Final installed as root and all folders are owner root > we deployed our web app (war) via the Web UI administration everything works for several hours the next day we come to work and Wildlfly fails with error below any help is very welcome > > ls /opt/wildfly-9.0.1.Final/standalone/deployments > drwxr-xr-x. 3 root root 4096 Sep 16 14:24 configuration > drwxr-xr-x. 8 root root 4096 Sep 10 11:20 data > drwxr-xr-x. 2 root root 23 Jul 23 21:01 deployments > drwxr-xr-x. 3 root root 16 Jul 23 21:01 lib > drwxr-xr-x. 2 root root 4096 Sep 18 00:00 log > drwxr-xr-x. 7 root root 94 Sep 16 14:24 tmp > > > 2015-09-18 10:02:41,735 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0012: Scan of /opt/wildfly-9.0.1.Final/standalone/deployments threw Exception: java.lang.RuntimeException: WFLYDS0032: Failed to list files in directory /opt/wildfly-9.0.1.Final/standalone/deployments. Check that the contents of the directory are readable. > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.listDirectoryChildren(FileSystemDeploymentService.java:1170) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scanDirectory(FileSystemDeploymentService.java:664) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:474) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:393) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentScanRunnable.run(FileSystemDeploymentService.java:161) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > > > Thanks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1095) Remove dependency on bouncycastle

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1095?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1095: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 > Remove dependency on bouncycastle > --------------------------------- > > Key: WFCORE-1095 > URL: https://issues.jboss.org/browse/WFCORE-1095 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > Core has a dependency on bouncycastle that AFAICT is not used. It was brought into core when a class from full's testsuite/shared was ported, but the core usage of the class has no need for the bouncycastle-related logic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1112) ModuleSpecProcessor not necessary char allocation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1112?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1112: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 > ModuleSpecProcessor not necessary char allocation > ------------------------------------------------- > > Key: WFCORE-1112 > URL: https://issues.jboss.org/browse/WFCORE-1112 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Vladimir Gordiychuk > Assignee: Jason Greene > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > [org.jboss.as.server.deployment.module.ModuleSpecProcessor|https://github....] concatenate string for debug logging without check that log level debug available or not, as result we allocate annesesary char[] during start server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5647) SingletonServiceTestCase fails intermittently

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5647: ---------------------------------- Summary: SingletonServiceTestCase fails intermittently Key: WFLY-5647 URL: https://issues.jboss.org/browse/WFLY-5647 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5646) SingletonServiceTestCase fails intermittently

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5646: ---------------------------------- Summary: SingletonServiceTestCase fails intermittently Key: WFLY-5646 URL: https://issues.jboss.org/browse/WFLY-5646 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-851) Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-851?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-851: ------------------------------------------------ Spolti <fspolti(a)redhat.com> changed the Status of [bug 1248156|https://bugzilla.redhat.com/show_bug.cgi?id=1248156] from CLOSED to NEW > Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-851 > URL: https://issues.jboss.org/browse/WFCORE-851 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Brad Maxwell > Assignee: David Lloyd > > Description of problem: > EJB CLient was configured with DNS FQDN to configure access to a remote EJB. If run a simple test adding an entry in /etc/hosts file pointing that FQDN to localhost for tests everything works. However, after finish the tests and remove the entry, the client still connects to localhost instead of resolve the new IP address. Even adding networkaddress.cache.ttl=30 inside security settings didn't work too. > How reproducible: > Everytime you use DNS names to connect to a remote EJB. > Steps to Reproduce: > 1. Configure a simple client that connects to a remote EJB using dns name > 2. add an entry in /etc/hosts mapping the dns name to localhost > 3. run the client code > 4. remove the entry in /etc/hosts > 5. run the client code again > Actual results: > EJB remote is still reached from localhost > Expected results: > After changing DNS record EJB will be reached in this new address -- 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 Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5642?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5642: --------------------------------- Labels: clean_undeploy (was: ) > 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 > > 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] (LOGMGR-125) Log rotation fails on Windows if target already exists

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-125?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-125: --------------------------------- Fix Version/s: 1.5.5.Final > Log rotation fails on Windows if target already exists > ------------------------------------------------------ > > Key: LOGMGR-125 > URL: https://issues.jboss.org/browse/LOGMGR-125 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Livingston > Assignee: James Perkins > Fix For: 1.5.5.Final, 2.0.4.Final, 2.1.0.Beta1 > > > PeriodicRotatingFileHandler (and others) use File.renameTo() to rename the file. That method is documented as having many implementation-defined aspects, see http://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo%28jav... > One that can be a problem is that on Windows, it will fail if the target file already exists. If you use a ".dd" suffix, this will occur when it rolls over to a new month. It has rarely been a problem, since most people use the year month and day so they are unique. Files.move() can replace existing files, so may be better, and some of the costs of that are likely not to be a problem with how it is using here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5074) MDB should not permit transaction attributes other than REQUIRED and NOT_SUPPORTED

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5074?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-5074: ----------------------------------- [~ochaloup] Do you have a test case highlighting the issue? > MDB should not permit transaction attributes other than REQUIRED and NOT_SUPPORTED > ----------------------------------------------------------------------------------- > > Key: WFLY-5074 > URL: https://issues.jboss.org/browse/WFLY-5074 > Project: WildFly > Issue Type: Bug > Components: EJB, JMS > Reporter: Ondřej Chaloupka > Assignee: Jeff Mesnil > > Message driven bean should be used only with transaction attributes REQUIRED an NOT_SUPPORTED. > The ejb specification says > {quote} > 13.6.3 Container-Managed Transaction Demarcation for Message-Driven Beans > Only the NOT_SUPPORTED and REQUIRED transaction attributes may be used for message-driven bean message listener methods. The use of the other transaction attributes is not meaningful for message-driven bean message listener methods because there is no pre-existing client transaction context (REQUIRES_NEW, SUPPORTS) and no client to handle exceptions (MANDATORY, NEVER). > {quote} > EAP 7 permits usage of other transaction attributes as well. In my testcase strangely attribute REQUIRED behaves differently than REQUIRES_NEW. > I do have mdb receiving message from remote message broker of ActiveMQ and closing connection during the commit (during prepare phase of XA 2PC). It happens to me that if used REQUIRED then all works fine. If used REQUIRES_NEW message seems to be read from the inbound queue but returned there instead of being left in in-doubt state (as expected when txn failed to prepare all participants). -- 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