[JBoss JIRA] (WFLY-2679) Jdbc cache store couldn't read databaseType property
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2679?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2679:
-------------------------------
Fix Version/s: 8.0.1.Final
(was: 8.0.0.Final)
> 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.1.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, 5 months
[JBoss JIRA] (WFLY-2555) StackOverflowError with ObjectFactory OSGi service
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2555?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2555:
-------------------------------
Fix Version/s: 8.0.1.Final
(was: 8.0.0.Final)
> StackOverflowError with ObjectFactory OSGi service
> --------------------------------------------------
>
> Key: WFLY-2555
> URL: https://issues.jboss.org/browse/WFLY-2555
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Naming
> Affects Versions: 8.0.0.Beta1
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 8.0.1.Final
>
>
> {code}
> Tests in error:
> JNDITestCase.testObjectFactoryOSGiService » StackOverflow
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0
> {code}
> {code}
> 15:57:00,295 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "example-jndi" (runtime-name : "example-jndi")
> 15:57:02,355 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-2-thread-1) BeanManager not found.
> 15:57:02,497 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-2-thread-1) BeanManager not found.
> 15:57:02,618 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-2-thread-1) Failed: org.jboss.as.test.integration.osgi.jndi.JNDITestCase.testObjectFactoryOSGiService: java.lang.StackOverflowError
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
> at com.sun.naming.internal.VersionHelper12.getJndiProperties(VersionHelper12.java:106) [rt.jar:1.7.0_25]
> at com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:202) [rt.jar:1.7.0_25]
> at javax.naming.InitialContext.init(InitialContext.java:238) [rt.jar:1.7.0_25]
> at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_25]
> at org.jboss.as.test.integration.osgi.jndi.JNDITestCase$TestObjectFactory$1.<init>(JNDITestCase.java:167)
> at org.jboss.as.test.integration.osgi.jndi.JNDITestCase$TestObjectFactory.getObjectInstance(JNDITestCase.java:167)
> at org.jboss.as.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:131)
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_25]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_25]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_25]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_25]
> {code}
--
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, 5 months
[JBoss JIRA] (WFLY-2845) On WildFly clean shutdown: failed marshalling rsp (UnsuccessfulResponse)
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2845?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2845:
-------------------------------
Fix Version/s: 8.0.1.Final
(was: 8.0.0.Final)
> On WildFly clean shutdown: failed marshalling rsp (UnsuccessfulResponse)
> ------------------------------------------------------------------------
>
> Key: WFLY-2845
> URL: https://issues.jboss.org/browse/WFLY-2845
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.CR1
> Environment: RHEL6 x86_64; Oracle JDK 7
> Reporter: Michal Babacek
> Assignee: Paul Ferraro
> Labels: clustering
> Fix For: 8.0.1.Final
>
>
> I've got two standalone-ha instances running on a one box. Each of these instances has {{<distributable/>}} [clusterbench|https://github.com/Karm/clusterbench/tree/simplified-and-pure] app deployed. When I start to shut the instances down via CLI command, one of them throws:
> {noformat}
> 08:59:33,341 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-4,shared=udp) ISPN000094: Received new cluster view: [jboss-eap-8.0/web|4] (1) [jboss-eap-8.0/web]
> 08:59:33,368 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher
> 08:59:33,379 ERROR [org.jgroups.blocks.RequestCorrelator] (remote-thread-0) failed marshalling rsp (UnsuccessfulResponse): java.lang.NullPointerException
> 08:59:33,380 ERROR [org.jgroups.blocks.RequestCorrelator] (remote-thread-1) failed marshalling rsp (UnsuccessfulResponse): java.lang.NullPointerException
> 08:59:33,392 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Final-SNAPSHOT "WildFly" stopped in 558ms
> {noformat}
> In the log. It's a non-deterministic problem and it does not emerge always.
--
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, 5 months
[JBoss JIRA] (WFLY-2720) Ability for Deployment Overlays to overlay System Properties
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-2720?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2720:
-------------------------------
Fix Version/s: 8.0.1.Final
(was: 8.0.0.Final)
> Ability for Deployment Overlays to overlay System Properties
> ------------------------------------------------------------
>
> Key: WFLY-2720
> URL: https://issues.jboss.org/browse/WFLY-2720
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Joshua Henn
> Fix For: 8.0.1.Final
>
>
> Currently Deployment Overlays allow only the replacing whole resource files. It would be nice to also be able to overlay System Properties that take precedent over globally defined properties.
> ie.
> {code:xml}
> <deployment-overlays>
> <deployment-overlay name="myOverlay">
> <system-properties>
> <property name="datasource" value="java:jboss/datasources/controller"/>
> </system-properties>
> <deployment name="controller.war"/>
> </deployment-overlay>
> </deployment-overlays>
> {code}
> Usecase:
> Have two deployments active of the same application, run-time configured by descriptor replacements via System Properties.
--
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, 5 months