[JBoss JIRA] (AS7-3481) Infinispan subsystem setting wrong properties for RemoteCacheStore
by Martin Gencur (JIRA)
Martin Gencur created AS7-3481:
----------------------------------
Summary: Infinispan subsystem setting wrong properties for RemoteCacheStore
Key: AS7-3481
URL: https://issues.jboss.org/browse/AS7-3481
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Reporter: Martin Gencur
Assignee: Paul Ferraro
Fix For: 7.1.0.Final
I'm getting this exception when I configure an infinispan cache with remote-store:
11:19:31,657 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.infinispan.default.memcachedCache.config: org.jboss.msc.service.StartException in service jboss.infinispan.default.memcachedCache.config: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.infinispan.config.ConfigurationException: Couldn't find a setter named [setInfinispan.client.hotrod.server_list] which takes a single parameter, for parameter infinispan.client.hotrod.server_list on class [class org.infinispan.loaders.remote.RemoteCacheStoreConfig]
at org.infinispan.config.parsing.XmlConfigHelper.setValues(XmlConfigHelper.java:471)
at org.infinispan.configuration.cache.LegacyConfigurationAdaptor.adapt(LegacyConfigurationAdaptor.java:208)
at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:430)
at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.defineConfiguration(DefaultEmbeddedCacheManager.java:121)
at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationService.start(CacheConfigurationService.java:100)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
For this to work, Infinispan subsystem (CacheAdd class) should now set different properties for the RemoteCacheStore. It now sets "infinispan.client.hotrod.server_list" directly as a property while it should most likely set "HotRodClientProperties" as a key and a Properties object (which would contain "infinispan.client.hotrod.server_list" as a key and proper value as a value) as a value.
See http://docs.jboss.org/infinispan/5.1/apidocs/org/infinispan/loaders/remot...
...hope that helps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1425) Cannot obtain SchemaFactory when TCCL points to ARQ module
by Thomas Diesler (JIRA)
Cannot obtain SchemaFactory when TCCL points to ARQ module
----------------------------------------------------------
Key: AS7-1425
URL: https://issues.jboss.org/browse/AS7-1425
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.1.0.Alpha1
{code}
10:46:41,387 ERROR [org.apache.aries.blueprint.container.BlueprintContainerImpl] (pool-7-thread-1) Unable to start blueprint container for bundle example-blueprint: java.lang.IllegalArgumentException: No SchemaFactory that implements the schema language specified by: http://www.w3.org/2001/XMLSchema could be loaded
at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:207) [:1.6.0_26]
at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchemaFactory(NamespaceHandlerRegistryImpl.java:266) [NamespaceHandlerRegistryImpl.class:]
at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchema(NamespaceHandlerRegistryImpl.java:236) [NamespaceHandlerRegistryImpl.class:]
at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:306) [NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.class:]
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-940) javax.xml.xpath.XPathFactory.newInstance() fails when invoked from a user bundle
by David Bosschaert (JIRA)
javax.xml.xpath.XPathFactory.newInstance() fails when invoked from a user bundle
--------------------------------------------------------------------------------
Key: AS7-940
URL: https://issues.jboss.org/browse/AS7-940
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: David Bosschaert
When deploying the simple greeter impl bundle (CXF-DOSGi demo) the following exception appears. Note that this does work fine with other OSGi frameworks like Equinox and Felix.
Creating Service {http://greeter.samples.dosgi.cxf.apache.org/}GreeterService from class org.apache.cxf.dosgi.samples.greeter.GreeterService
Exception in thread "pool-3-thread-1" java.lang.ExceptionInInitializerError
at org.apache.cxf.aegis.type.XMLTypeCreator.<init>(XMLTypeCreator.java:134)
at org.apache.cxf.aegis.AegisContext.createRootTypeCreator(AegisContext.java:119)
at org.apache.cxf.aegis.AegisContext.createTypeCreator(AegisContext.java:108)
at org.apache.cxf.aegis.AegisContext.initialize(AegisContext.java:150)
at org.apache.cxf.aegis.databinding.AegisDatabinding.initialize(AegisDatabinding.java:262)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:467)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:530)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:278)
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:99)
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
at org.apache.cxf.dosgi.dsw.handlers.PojoConfigurationTypeHandler.createServer(PojoConfigurationTypeHandler.java:125)
at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminCore.exportService(RemoteServiceAdminCore.java:244)
at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(RemoteServiceAdminInstance.java:78)
at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(RemoteServiceAdminInstance.java:71)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportService(RemoteServiceAdminInstance.java:71)
at org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportService(RemoteServiceAdminInstance.java:40)
at org.apache.cxf.dosgi.topologymanager.TopologyManager$2.run(TopologyManager.java:254)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.RuntimeException: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory implementation found for the object model: http://java.sun.com/jaxp/xpath/dom
at javax.xml.xpath.XPathFactory.newInstance(XPathFactory.java:101)
at org.apache.cxf.helpers.XPathUtils.<clinit>(XPathUtils.java:34)
... 21 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3148) Allow dependency configuration for deployment scanner
by Brent Douglas (Created) (JIRA)
Allow dependency configuration for deployment scanner
-----------------------------------------------------
Key: AS7-3148
URL: https://issues.jboss.org/browse/AS7-3148
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.0.CR1
Environment: AS7.1.0.Final-SNAPSHOT in standalone using standalone-ha.xml
Reporter: Brent Douglas
It would be really handy to be able to specify dependencies for the deployment scanner to abide by. E.g. I have an application with the following structure:
A.ear
|-B.jar
\-C.war
D.war
If D has a dependency on B and they are deployed at the same time I'll get:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.module.spec.service."deployment.A.ear".main (missing) dependants: [service jboss.module.service."deployment.D.war".main, service jboss.deployment.unit."D.war".POST_MODULE]
service jboss.module.spec.service."deployment.A.ear.B.jar".main (missing) dependants: [service jboss.module.service."deployment.D.war".main, service jboss.deployment.unit."D.war".POST_MODULE]
It would be great though if I could specify that I don't want to deploy D until A is deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months