[JBoss JIRA] (JGRP-1794) OOBTest method testNonBlockingUnicastOOBMessage fails to correctly receive all OOB mssages
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1794?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JGRP-1794:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=910773
> OOBTest method testNonBlockingUnicastOOBMessage fails to correctly receive all OOB mssages
> -------------------------------------------------------------------------------------------
>
> Key: JGRP-1794
> URL: https://issues.jboss.org/browse/JGRP-1794
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: Solaris, RHEL, Windows, HPUX
> tcp stack only
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test fails regularly on multiple platforms. It doesn't fail all the time, but perhaps on 5/10 platform executions.
> The test consists of a sender and a receiver. The receiver B will receive OOB messages but blocks on a latch for 25 seconds when it receives a non-OOB message. After 25 seconds, it unblocks and continues receiving
> The test does this:
> - send 1 regular message from A -> B
> - send 9 OOB meesages from A -> B
> - wait 20 seconds for messages to arrive
> - check that all 9 OOB messages have arrived
> - unblock the latch
> - check that all 10 message have arrived
> The test failures all involve the first 9 OOB messages not arriving completely. For example, sample lists of received messages before the first 20 second interval are:
> [3,2,6,8,9,10,4]
> [2,3,4,8,9,5]
> [2,3,4,8,7,9]
> [2,3,5,4,6]
> So, it appears that either the messages are slow to arrive or not arriving at all.
> A correct result looks like this:
> {noformat}
> list = [2, 4, 3, 7, 8, 9, 10, 5, 6]
> [main]: releasing latch
> list = [2, 4, 3, 7, 8, 9, 10, 5, 6, 1]
> {noformat}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1806) UnicastLoopbackTest fails to receive all messages in the allotted time
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1806?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JGRP-1806:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=927921
> UnicastLoopbackTest fails to receive all messages in the allotted time
> ----------------------------------------------------------------------
>
> Key: JGRP-1806
> URL: https://issues.jboss.org/browse/JGRP-1806
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL, Windows, Solaris
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> UnicastLoopbackTest.testUnicastMessagesWithLoopback() is failing with the following error:
> {noformat}
> Error Message
> Test timed out before all messages were received
> Stacktrace
> java.lang.AssertionError
> at org.testng.Assert.fail(Assert.java:94)
> at org.jgroups.tests.UnicastLoopbackTest.testUnicastMsgsWithLoopback(UnicastLoopbackTest.java:78)
> {noformat}
> The test does the following:
> - creates one channel with loopback enabled in the transport
> - the channel is assigned a receiver which collects the messages received and sets a Boolean valued Promise when all messages have been received
> - the channel sends 1000 messages to itself in a burst
> - waits 20 seconds for the promise to be set to true
> The test fails because the messages do not arrive within the allotted 20 seconds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1806) UnicastLoopbackTest fails to receive all messages in the allotted time
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1806?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated JGRP-1806:
--------------------------------------
Bugzilla Update: (was: Perform)
> UnicastLoopbackTest fails to receive all messages in the allotted time
> ----------------------------------------------------------------------
>
> Key: JGRP-1806
> URL: https://issues.jboss.org/browse/JGRP-1806
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL, Windows, Solaris
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> UnicastLoopbackTest.testUnicastMessagesWithLoopback() is failing with the following error:
> {noformat}
> Error Message
> Test timed out before all messages were received
> Stacktrace
> java.lang.AssertionError
> at org.testng.Assert.fail(Assert.java:94)
> at org.jgroups.tests.UnicastLoopbackTest.testUnicastMsgsWithLoopback(UnicastLoopbackTest.java:78)
> {noformat}
> The test does the following:
> - creates one channel with loopback enabled in the transport
> - the channel is assigned a receiver which collects the messages received and sets a Boolean valued Promise when all messages have been received
> - the channel sends 1000 messages to itself in a burst
> - waits 20 seconds for the promise to be set to true
> The test fails because the messages do not arrive within the allotted 20 seconds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-2965) IllegalArgumentException: JBAS014577: Unsupported marshalling version: 1 on shutdown
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2965?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-2965:
------------------------------------
The service providing the infinispan cache for the EJB deployment is missing a dependency on the service that provides the marshalling configuration.
> IllegalArgumentException: JBAS014577: Unsupported marshalling version: 1 on shutdown
> ------------------------------------------------------------------------------------
>
> Key: WFLY-2965
> URL: https://issues.jboss.org/browse/WFLY-2965
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Environment: jdk8
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
>
> {noformat}
> ^C17:12:20,850 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /clusterbench-passivating
> 17:12:20,852 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017535: Unregistered web context: /clusterbench-granular
> 17:12:20,852 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /clusterbench
> 17:12:20,859 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 66) MODCLUSTER000002: Initiating mod_cluster shutdown
> 17:12:20,870 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 17:12:20,872 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 17:12:20,872 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 17:12:20,872 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 17:12:20,884 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 68) ISPN000029: Passivating all entries to disk
> 17:12:20,885 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 68) ISPN000030: Passivated 0 entries in 0 milliseconds
> 17:12:20,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017532: Host default-host stopping
> 17:12:20,873 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 66) ISPN000029: Passivating all entries to disk
> 17:12:20,896 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 65) ISPN000029: Passivating all entries to disk
> 17:12:20,896 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
> 17:12:20,897 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 65) ISPN000030: Passivated 0 entries in 0 milliseconds
> 17:12:20,912 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment clusterbench-ee7.ear
> 17:12:20,917 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
> 17:12:20,930 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010418: Stopped Driver service with driver-name = h2
> 17:12:20,930 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) JBAS010282: Stopped default-host/clusterbench-passivating cache from web container
> 17:12:20,932 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 77) ISPN000029: Passivating all entries to disk
> 17:12:20,934 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 2 entries in 37 milliseconds
> 17:12:20,950 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) JBAS010282: Stopped default-host/clusterbench-granular cache from web container
> 17:12:20,950 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 77) ISPN000030: Passivated 1 entries in 18 milliseconds
> 17:12:20,963 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) JBAS010282: Stopped default-host/clusterbench cache from web container
> 17:12:20,981 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
> 17:12:20,982 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77) JBAS010282: Stopped dist cache from web container
> 17:12:20,942 WARN [org.infinispan.factories.ComponentRegistry] (ServerService Thread Pool -- 66) ISPN000189: While stopping a cache or cache manager, one of its components failed to stop: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.eviction.PassivationManagerImpl.passivateAll() throws org.infinispan.persistence.spi.PersistenceException on object of type PassivationManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:185)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:674)
> at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:552)
> at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:241)
> at org.infinispan.CacheImpl.stop(CacheImpl.java:697)
> at org.infinispan.CacheImpl.stop(CacheImpl.java:692)
> at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:316)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.stop(CacheService.java:96)
> at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:114) [wildfly-clustering-common-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> Caused by: org.infinispan.persistence.spi.PersistenceException: org.infinispan.persistence.spi.PersistenceException: java.lang.IllegalArgumentException: JBAS014577: Unsupported marshalling version: 1
> at org.infinispan.persistence.file.SingleFileStore.write(SingleFileStore.java:317)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.writeToAllStores(PersistenceManagerImpl.java:457)
> at org.infinispan.eviction.PassivationManagerImpl.passivateAll(PassivationManagerImpl.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0]
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:183)
> ... 13 more
> Caused by: org.infinispan.persistence.spi.PersistenceException: java.lang.IllegalArgumentException: JBAS014577: Unsupported marshalling version: 1
> at org.infinispan.marshall.core.MarshalledEntryImpl.marshall(MarshalledEntryImpl.java:107)
> at org.infinispan.marshall.core.MarshalledEntryImpl.getValueBytes(MarshalledEntryImpl.java:88)
> at org.infinispan.persistence.file.SingleFileStore.write(SingleFileStore.java:275)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException: JBAS014577: Unsupported marshalling version: 1
> at org.jboss.as.ejb3.component.stateful.VersionedMarshallingConfigurationService.getMarshallingConfiguration(VersionedMarshallingConfigurationService.java:88)
> at org.jboss.as.clustering.marshalling.SimpleMarshallingContext.getMarshallingConfiguration(SimpleMarshallingContext.java:69) [wildfly-clustering-common-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.clustering.marshalling.SimpleMarshallingContext.createMarshaller(SimpleMarshallingContext.java:65) [wildfly-clustering-common-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.clustering.marshalling.SimpleMarshalledValue.getBytes(SimpleMarshalledValue.java:75) [wildfly-clustering-common-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.clustering.marshalling.SimpleMarshalledValue.writeExternal(SimpleMarshalledValue.java:150) [wildfly-clustering-common-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:876)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62) [jboss-marshalling-1.4.3.Final.jar:1.4.3.Final]
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:115) [jboss-marshalling-1.4.3.Final.jar:1.4.3.Final]
> at org.wildfly.clustering.ejb.infinispan.group.InfinispanBeanGroupEntryExternalizer.writeObject(InfinispanBeanGroupEntryExternalizer.java:50)
> at org.wildfly.clustering.ejb.infinispan.group.InfinispanBeanGroupEntryExternalizer.writeObject(InfinispanBeanGroupEntryExternalizer.java:36)
> at org.infinispan.marshall.core.ExternalizerTable$ForeignExternalizerAdapter.writeObject(ExternalizerTable.java:444)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:148)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62) [jboss-marshalling-1.4.3.Final.jar:1.4.3.Final]
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:115) [jboss-marshalling-1.4.3.Final.jar:1.4.3.Final]
> at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectToObjectStream(AbstractJBossMarshaller.java:74)
> at org.infinispan.marshall.core.VersionAwareMarshaller.objectToBuffer(VersionAwareMarshaller.java:77)
> at org.infinispan.commons.marshall.AbstractMarshaller.objectToBuffer(AbstractMarshaller.java:41)
> at org.infinispan.commons.marshall.AbstractDelegatingMarshaller.objectToBuffer(AbstractDelegatingMarshaller.java:85)
> at org.infinispan.marshall.core.MarshalledEntryImpl.marshall(MarshalledEntryImpl.java:105)
> ... 22 more
> Caused by: an exception which occurred:
> in object org.jboss.as.clustering.marshalling.SimpleMarshalledValue@d8dbecb5
> in object org.wildfly.clustering.ejb.infinispan.group.InfinispanBeanGroupEntry@2fb506a3
> 17:12:20,988 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 1 entries in 6 milliseconds
> 17:12:21,009 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000080: Disconnecting JGroups Channel
> 17:12:21,022 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) JBAS010282: Stopped dist cache from ejb container
> 17:12:21,023 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) JBAS010282: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar cache from ejb container
> 17:12:21,026 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups Channel
> 17:12:21,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017521: Undertow HTTP listener default suspending
> 17:12:21,028 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
> 17:12:21,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017521: Undertow AJP listener ajp suspending
> 17:12:21,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017520: Undertow AJP listener ajp stopped, was bound to /127.0.0.1:8009
> 17:12:21,038 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war) in 202ms
> 17:12:21,041 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war) in 209ms
> 17:12:21,035 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar) in 200ms
> 17:12:21,035 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war) in 203ms
> 17:12:21,041 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017506: Undertow 1.0.0.Final stopping
> 17:12:21,042 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 211ms
> 17:12:21,390 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher
> 17:12:21,392 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000082: Stopping the RpcDispatcher
> 17:12:21,400 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.1.Final-SNAPSHOT "WildFly" stopped in 565ms
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-2679) Jdbc cache store couldn't read databaseType property
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2679?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-2679.
------------------------------
Fix Version/s: 8.0.0.Final
(was: 8.0.1.Final)
Resolution: Done
We already expose a dialect attribute, which allows you to configure the databaseType of the cache store. If you want a fix for infinispan-cachestore-jdbc, then file a separate jira with infinispan.
> Jdbc cache store couldn't read databaseType property
> ----------------------------------------------------
>
> Key: WFLY-2679
> URL: https://issues.jboss.org/browse/WFLY-2679
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.CR1
> Environment: WildFly 8.0.0.Final-SNAPSHOT from 2014-01-17
> Reporter: Tomas Remes
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Final
>
>
> If you want use some driver, which type is not recognizable by Infinispan (e.g. jtds driver), then you are asked to specify your DB type via "databaseType" property in your cache store configuration. But when you specify it, you'll get following exception:
> {noformat}
> org.infinispan.commons.CacheConfigurationException: Couldn't find a setter named [setDatabaseType] which takes a single parameter, for parameter databaseType on class [class org.infinispan.persistence.jdbc.configuration.JdbcBinaryStoreConfigurationBuilder]
> at org.infinispan.configuration.parsing.XmlConfigHelper.setValues(XmlConfigHelper.java:450)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:91)
> at org.infinispan.configuration.cache.AbstractStoreConfigurationBuilder.withProperties(AbstractStoreConfigurationBuilder.java:9)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.processModelNode(CacheAdd.java:542)
> at org.jboss.as.clustering.infinispan.subsystem.ClusteredCacheAdd.processModelNode(ClusteredCacheAdd.java:69)
> at org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheAdd.processModelNode(SharedStateCacheAdd.java:50)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheAdd.processModelNode(DistributedCacheAdd.java:90)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.installRuntimeServices(CacheAdd.java:205)
> at org.jboss.as.clustering.infinispan.subsystem.CacheAdd.performRuntime(CacheAdd.java:179)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:343) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBASMP-64) undeploy-artifact fails with misleading error message
by Harald Wellmann (JIRA)
[ https://issues.jboss.org/browse/JBASMP-64?page=com.atlassian.jira.plugin.... ]
Harald Wellmann updated JBASMP-64:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-maven-plugin/pull/11
> undeploy-artifact fails with misleading error message
> -----------------------------------------------------
>
> Key: JBASMP-64
> URL: https://issues.jboss.org/browse/JBASMP-64
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Environment: wildfly-maven-plugin 1.0.1.Final
> WildFly 8.0.0.Final, Oracle Java 1.7.0_51, Ubuntu 13.10 64-bit
> Reporter: Harald Wellmann
> Assignee: James Perkins
>
> undeploy-artifact fails with the following exception (mvn -X):
> {noformat}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:undeploy-artifact (undeploy) on project deployment: com.example.myapp
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.wildfly.plugin.common.DeploymentFailureException: com.example.myapp
> at org.wildfly.plugin.deployment.UndeployArtifactMojo.validate(UndeployArtifactMojo.java:92)
> at org.wildfly.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136)
> at org.wildfly.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBASMP-64) undeploy-artifact fails with misleading error message
by Harald Wellmann (JIRA)
Harald Wellmann created JBASMP-64:
-------------------------------------
Summary: undeploy-artifact fails with misleading error message
Key: JBASMP-64
URL: https://issues.jboss.org/browse/JBASMP-64
Project: JBoss AS Maven Plugins
Issue Type: Bug
Environment: wildfly-maven-plugin 1.0.1.Final
WildFly 8.0.0.Final, Oracle Java 1.7.0_51, Ubuntu 13.10 64-bit
Reporter: Harald Wellmann
Assignee: James Perkins
undeploy-artifact fails with the following exception (mvn -X):
{noformat}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.1.Final:undeploy-artifact (undeploy) on project deployment: com.example.myapp
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.wildfly.plugin.common.DeploymentFailureException: com.example.myapp
at org.wildfly.plugin.deployment.UndeployArtifactMojo.validate(UndeployArtifactMojo.java:92)
at org.wildfly.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136)
at org.wildfly.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3078) directory-grouping configuration is not getting persisted via CLI when no servers defined
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3078?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3078:
-----------------------------------------------
Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1073715|https://bugzilla.redhat.com/show_bug.cgi?id=1073715] from NEW to POST
> directory-grouping configuration is not getting persisted via CLI when no servers defined
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-3078
> URL: https://issues.jboss.org/browse/WFLY-3078
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Environment: All Operating System
> Reporter: Jay Kumar SenSharma
> Assignee: Emanuel Muckenhuber
> Fix For: 8.0.1.Final
>
>
> - If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml
> {code}
> /host=master/:write-attribute(name=directory-grouping,value=by-type)
> {code}
> - The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months