[JBoss JIRA] (WFLY-847) Strange hangup during stopping of server - must be killed by SIGKILL
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-847?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry resolved WFLY-847.
-----------------------------------
Resolution: Out of Date
Given the discussion on [bug 899797|https://bugzilla.redhat.com/show_bug.cgi?id=899797] it is likely the original reported issue was fixed long ago. Please reopen if you can reproduce this with WildFly 10.
> Strange hangup during stopping of server - must be killed by SIGKILL
> --------------------------------------------------------------------
>
> Key: WFLY-847
> URL: https://issues.jboss.org/browse/WFLY-847
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Pavel Janousek
> Priority: Critical
>
> During investigation another JIRA (AS7-3607) I've affected by another issue too.
> Let say - you have machine after successful reboot. You should prepare network environment as described in AS7-3607, the only one difference is you must disable loopback interface too (ip link set dev lo down).
> Now, when you try to start AS7, everything is OK, more precisely is the same as in other issue (AS7-3607).
> BUT - when you hit Ctrl-C now - you try to stop server - it hang-up and report only:
> {code}
> 17:05:23,502 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 14012ms - Started 158 of 228 services (68 services are passive or on-demand)
> ^C17:05:50,274 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/queue/test
> 17:05:50,279 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011921: Stopping OSGi Framework
> 17:05:50,279 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
> 17:05:50,282 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
> 17:05:50,341 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
> 17:05:50,350 INFO [jacorb.poa] POA IRPOA destroyed
> 17:05:50,381 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [3fe9aa6a-4d86-11e1-b2c6-000000000001] stopped
> 17:05:50,411 INFO [jacorb.poa] POA Naming destroyed
> 17:05:50,434 INFO [jacorb.poa] POA RootPOA destroyed
> 17:05:50,440 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
> 17:05:50,442 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
> 17:05:50,441 INFO [jacorb.orb] prepare ORB for shutdown...
> 17:05:50,442 INFO [jacorb.orb] ORB going down...
> 17:05:50,446 INFO [jacorb.orb.iiop] Listener exited
> 17:05:50,447 INFO [jacorb.orb] ORB shutdown complete
> 17:05:50,447 INFO [jacorb.orb] ORB run, exit
> ^Z
> [1]+ Stopped ./standalone.sh
> [pjanouse@fedora15-vrt1 bin]$ kill -9 %1
> [1]+ Killed ./standalone.sh
> [pjanouse@fedora15-vrt1 bin]$
> {code}
> As you can see, it can be killed only by SIGKILL signal.
> More strange is when you now enable loopback interface again (ip link set dev lo up), start/stop sequence works fine (as expected).
> And the strangest is when you disable loopback again, it works fine as in previous step - everything works as you can expect. I think it is related to some network issue, but I can't be more precise now, I can't find any other aspect why it is occurred after reboot only.
> I try also several attempts (loopback interface disabled) during let say 10 minutes (due to attempt to eliminate resolver/DNS timeouts etc.), but until I did up/down sequence in lo interface, behavior was the same - only SIGKILL stops it.
> I try it several times, after several reboot my instance inside VirtualBox and behavior is the same - so it isn't accind situation. So I hope it isn't related to only network stack implementation/virtualization inside VirtualBox and is reproducible in another linux box too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[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:
------------------------------------------------
Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1248156|https://bugzilla.redhat.com/show_bug.cgi?id=1248156] from ASSIGNED to POST
> 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, 7 months
[JBoss JIRA] (WFCORE-1175) CLI prints unexpected ANSI characters to output with "echo" command
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1175?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-1175:
----------------------------------
Fix Version/s: 2.0.5.Final
(was: 2.0.4.Final)
> CLI prints unexpected ANSI characters to output with "echo" command
> -------------------------------------------------------------------
>
> Key: WFCORE-1175
> URL: https://issues.jboss.org/browse/WFCORE-1175
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.3.Final
> Reporter: Marek Kopecký
> Assignee: Ståle Pedersen
> Priority: Blocker
> Fix For: 2.0.5.Final
>
>
> *Description of problem:*
> CLI prints unexpected ANSI character to output with "echo" command.
> * This is regression against EAP 7.0.0.DR13
> * This is blocker for GA release.
> * This is not beta blocker.
> * This is probably AESH issue, so I assign [~stalep], but it is also CLI issue, so [~aloubyansky] may be assigned to this
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./standalone.sh
> # ./jboss-cli.sh --connect controller=127.0.0.1 command="echo test-echo" > out.txt
> # vim out.txt
> #* "cat out.txt" can't be used for reproducing, because console hide unexpected ANSI characters
> *Actual results:*
> {noformat}
> ^[[0G^[[2Ktest-echo
> {noformat}
> *Expected results:*
> {noformat}
> test-echo
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1128) Improve the subsystem test schema test coverage
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1128?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-1128:
----------------------------------
Fix Version/s: 2.0.5.Final
(was: 2.0.4.Final)
> Improve the subsystem test schema test coverage
> -----------------------------------------------
>
> Key: WFCORE-1128
> URL: https://issues.jboss.org/browse/WFCORE-1128
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.1.Final
> Reporter: Kabir Khan
> Assignee: Kabir Khan
> Fix For: 2.0.5.Final
>
>
> Currently the way to enable the AbstractSubsystemBaseTest testSchema() and testSchemaOfSubsystemTemplates() tests is to override getSubsystemXsdPath() and getSubsystemTemplatePaths().
> Rather than making it explicit to turn on, it should be explicit to turn off.
> Also the current way of doing this uses Assume.assumeTrue() to check if a test has provided a schema file, which provides a lot of ignored test noise in the test output. If the xsd should not be tested, methods should instead override testSchema() or testSchemaOfSubsystemTemplates() and provide an empty implementation with a comment saying why it is not important.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5770) Lock TimeoutException on CacheRegistry.close()
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5770?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-5770:
-------------------------------
Summary: Lock TimeoutException on CacheRegistry.close() (was: TimeoutException on CacheRegistry.close())
> Lock TimeoutException on CacheRegistry.close()
> ----------------------------------------------
>
> Key: WFLY-5770
> URL: https://issues.jboss.org/browse/WFLY-5770
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 10.0.0.CR4
> Reporter: Radoslav Husar
> Assignee: Richard Achmatowicz
>
> Just happened on node shutdown when testing locally.
> {noformat}
> 19:22:21,114 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0004: Undertow 1.3.7.Final stopping
> 19:22:21,114 ERROR [stderr] (ServerService Thread Pool -- 82) Exception in thread "ServerService Thread Pool -- 82" org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on node2 in behalf of transaction GlobalTransaction:<node2>:4223:local. Current owner GlobalTransaction:<node2>:4217:local.
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.util.concurrent.locks.impl.DefaultPendingLockManager.timeout(DefaultPendingLockManager.java:224)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.util.concurrent.locks.impl.DefaultPendingLockManager.checkForPendingLock(DefaultPendingLockManager.java:196)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.util.concurrent.locks.impl.DefaultPendingLockManager.awaitPendingTransactionsForKey(DefaultPendingLockManager.java:115)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockKey(AbstractTxLockingInterceptor.java:190)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockOrRegisterBackupLock(AbstractTxLockingInterceptor.java:115)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitDataWriteCommand(PessimisticLockingInterceptor.java:121)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitRemoveCommand(AbstractLockingInterceptor.java:71)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:48)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,115 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:366)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:48)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.handleTxWriteCommand(StateTransferInterceptor.java:304)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.handleWriteCommand(StateTransferInterceptor.java:286)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.visitRemoveCommand(StateTransferInterceptor.java:123)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:102)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:71)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:48)
> 19:22:21,116 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1634)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.removeInternal(CacheImpl.java:558)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.remove(CacheImpl.java:549)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.DecoratedCache.remove(DecoratedCache.java:452)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.AbstractDelegatingCache.remove(AbstractDelegatingCache.java:296)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.CacheRegistry.lambda$close$0(CacheRegistry.java:101)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.service.concurrent.StampedLockServiceExecutor.close(StampedLockServiceExecutor.java:55)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.CacheRegistry.close(CacheRegistry.java:96)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.CacheRegistryFactory$1.close(CacheRegistryFactory.java:56)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.RegistryBuilder.stop(RegistryBuilder.java:88)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.service.AsynchronousServiceBuilder$2.run(AsynchronousServiceBuilder.java:130)
> 19:22:21,117 ERROR [stderr] (ServerService Thread Pool -- 82) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at java.lang.Thread.run(Thread.java:745)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) Suppressed: org.infinispan.commons.CacheException: javax.transaction.RollbackException: Transaction marked as rollback only.
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.ee.infinispan.ActiveTransactionBatch.close(ActiveTransactionBatch.java:50)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.CacheRegistry.lambda$close$0(CacheRegistry.java:102)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) ... 9 more
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) Caused by: javax.transaction.RollbackException: Transaction marked as rollback only.
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.transaction.tm.DummyTransaction.setRollbackOnly(DummyTransaction.java:146)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:374)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.TxInterceptor.visitRemoveCommand(TxInterceptor.java:230)
> 19:22:21,118 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:48)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.handleTxWriteCommand(StateTransferInterceptor.java:304)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.handleWriteCommand(StateTransferInterceptor.java:286)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.statetransfer.StateTransferInterceptor.visitRemoveCommand(StateTransferInterceptor.java:123)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:102)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:71)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:48)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:59)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1634)
> 19:22:21,119 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.removeInternal(CacheImpl.java:558)
> 19:22:21,120 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.CacheImpl.remove(CacheImpl.java:549)
> 19:22:21,120 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.DecoratedCache.remove(DecoratedCache.java:452)
> 19:22:21,120 ERROR [stderr] (ServerService Thread Pool -- 82) at org.infinispan.cache.impl.AbstractDelegatingCache.remove(AbstractDelegatingCache.java:296)
> 19:22:21,120 ERROR [stderr] (ServerService Thread Pool -- 82) at org.wildfly.clustering.server.registry.CacheRegistry.lambda$close$0(CacheRegistry.java:101)
> 19:22:21,120 ERROR [stderr] (ServerService Thread Pool -- 82) ... 9 more
> 19:22:31,124 WARN [org.infinispan.transaction.impl.TransactionTable] (ServerService Thread Pool -- 88) ISPN000100: Stopping, but there are 1 local transactions and 0 remote transactions that did not finish in time.
> 19:22:31,125 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0003: Stopped routing cache from web container
> 19:22:31,128 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel web
> 19:22:31,128 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel web
> 19:22:31,141 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: WildFly Full 10.0.0.CR5-SNAPSHOT (WildFly Core 2.0.3.Final) stopped in 25086ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1175) CLI prints unexpected ANSI characters to output with "echo" command
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1175?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1175:
-------------------------------------
Fix Version/s: 2.0.4.Final
I'm scheduling this for 2.0.4 even though I know it won't get done for that (release is in progress.) I just want it to automatically get rescheduled to 2.0.5 once that is created so it stays visible for the pending release.
> CLI prints unexpected ANSI characters to output with "echo" command
> -------------------------------------------------------------------
>
> Key: WFCORE-1175
> URL: https://issues.jboss.org/browse/WFCORE-1175
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.3.Final
> Reporter: Marek Kopecký
> Assignee: Ståle Pedersen
> Priority: Blocker
> Fix For: 2.0.4.Final
>
>
> *Description of problem:*
> CLI prints unexpected ANSI character to output with "echo" command.
> * This is regression against EAP 7.0.0.DR13
> * This is blocker for GA release.
> * This is not beta blocker.
> * This is probably AESH issue, so I assign [~stalep], but it is also CLI issue, so [~aloubyansky] may be assigned to this
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./standalone.sh
> # ./jboss-cli.sh --connect controller=127.0.0.1 command="echo test-echo" > out.txt
> # vim out.txt
> #* "cat out.txt" can't be used for reproducing, because console hide unexpected ANSI characters
> *Actual results:*
> {noformat}
> ^[[0G^[[2Ktest-echo
> {noformat}
> *Expected results:*
> {noformat}
> test-echo
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1185) "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1185?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1185:
-------------------------------------
Fix Version/s: 2.0.4.Final
> "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-1185
> URL: https://issues.jboss.org/browse/WFCORE-1185
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.3.Final
> Reporter: Marek Kopecký
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 2.0.4.Final
>
>
> *Description of problem:*
> "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
> *How reproducible:*
> always
> *Steps to Reproduce:*
> # /core-service=server-environment:read-resource-description(operations=false)
> *Actual results:*
> ...
> "initial-running-mode" => \{
> "type" => STRING,
> "description" => "The *current* running mode of the server. Either *LIVE (normal operations)* or ADMIN_ONLY. An ADMIN_ONLY server will start any configured management interfaces and accept management requests, but will not start services used for handling end user requests.",
> ...
> \},
> ...
> *Expected results:*
> The *initial* running mode of the server. Either *NORMAL* or ADMIN_ONLY. An ADMIN_ONLY server will start any configured management interfaces and accept management requests, but will not start services used for handling end user requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5789) NPE when forming jgroups cluster
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-5789:
----------------------------------
Summary: NPE when forming jgroups cluster
Key: WFLY-5789
URL: https://issues.jboss.org/browse/WFLY-5789
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 9.0.1.Final, 10.0.0.CR4
Reporter: Paul Ferraro
Assignee: Paul Ferraro
I just got this NPE when deploying a new application on my Wildfly 10 CR4 domain cluster.
JGRP000027: failed passing message up: java.lang.RuntimeException: java.lang.NullPointerException
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:689)
at org.jgroups.JChannel.up(JChannel.java:738)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1029)
at org.jgroups.protocols.FORK.up(FORK.java:133)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:394)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:735)
at org.jgroups.protocols.pbcast.ParticipantGmsImpl.handleViewChange(ParticipantGmsImpl.java:140)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:925)
at org.jgroups.stack.Protocol.up(Protocol.java:412)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294)
at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:474)
at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:982)
at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:912)
at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:846)
at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:618)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155)
at org.jgroups.protocols.FD.up(FD.java:260)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:310)
at org.jgroups.protocols.MERGE3.up(MERGE3.java:285)
at org.jgroups.protocols.Discovery.up(Discovery.java:295)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1577)
at org.jgroups.protocols.TP$MyHandler.run(TP.java:1796)
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.lang.NullPointerException
at org.wildfly.clustering.server.group.ChannelNodeFactory.createNode(ChannelNodeFactory.java:55)
at org.wildfly.clustering.server.group.ChannelNodeFactory.createNode(ChannelNodeFactory.java:40)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.getNodes(ChannelCommandDispatcherFactory.java:207)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.getNodes(ChannelCommandDispatcherFactory.java:201)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.viewAccepted(ChannelCommandDispatcherFactory.java:216)
at org.jgroups.blocks.MessageDispatcher.handleUpEvent(MessageDispatcher.java:605)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:686)
... 25 more
I have already stumbled upon this issue in Wildfly 9: https://developer.jboss.org/thread/265607
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1185) "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1185?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-2190 to WFCORE-1185:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1185 (was: JBEAP-2190)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Domain Management
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.3.Final
(was: 7.0.0.ER2 (Beta))
> "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-1185
> URL: https://issues.jboss.org/browse/WFCORE-1185
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.3.Final
> Reporter: Marek Kopecký
> Assignee: Brian Stansberry
> Priority: Minor
>
> *Description of problem:*
> "initial-running-mode" attribute from "/core-service=server-environment" has wrong description
> *How reproducible:*
> always
> *Steps to Reproduce:*
> # /core-service=server-environment:read-resource-description(operations=false)
> *Actual results:*
> ...
> "initial-running-mode" => \{
> "type" => STRING,
> "description" => "The *current* running mode of the server. Either *LIVE (normal operations)* or ADMIN_ONLY. An ADMIN_ONLY server will start any configured management interfaces and accept management requests, but will not start services used for handling end user requests.",
> ...
> \},
> ...
> *Expected results:*
> The *initial* running mode of the server. Either *NORMAL* or ADMIN_ONLY. An ADMIN_ONLY server will start any configured management interfaces and accept management requests, but will not start services used for handling end user requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months