February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3553) Add support for maven coordinates in OSGi subsystem capability definition

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3553: ----------------------------------- Summary: Add support for maven coordinates in OSGi subsystem capability definition Key: AS7-3553 URL: https://issues.jboss.org/browse/AS7-3553 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler The repository, which is installed by default can handle maven coordinates. It should be possible to use those in the subsystem configuration too {code} <capability name="org.ops4j.pax.web:pax-web-jsp:1.1.2" startlevel="1"/> <capability name="org.ops4j.pax.web:pax-web-jetty-bundle:1.1.2" startlevel="1"/> <capability name="org.ops4j.pax.web:pax-web-extender-war:1.1.2" startlevel="1"/> {code} -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-3024) AS7 cannot startup with standalone-xts.xml configuration file

by Ivo Studensky (Created) (JIRA)

AS7 cannot startup with standalone-xts.xml configuration file ------------------------------------------------------------- Key: AS7-3024 URL: https://issues.jboss.org/browse/AS7-3024 Project: Application Server 7 Issue Type: Bug Components: Transactions Affects Versions: 7.1.0.Beta1b Reporter: Ivo Studensky Assignee: Jonathan Halliday Fix For: 7.1.0.CR1 The docs/examples/configs/standalone-xts.xml seems to be out of date as AS7 fails to start with it. See the output snippet: {noformat} $ sh standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml . . 16:43:10,393 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.messaging.default: org.jboss.msc.service.StartException in service jboss.messaging.default: JBAS011644: Failed to start service at org.jboss.as.messaging.HornetQService.start(HornetQService.java:193) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS011641: Failed to find SocketBinding for connector: netty at org.jboss.as.messaging.HornetQService.start(HornetQService.java:128) ... 5 more 16:43:10,438 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) null null . . 16:43:14,643 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started (with errors) in 5839ms - Started 146 of 220 services (7 services failed or missing dependencies, 66 services are passive or on-demand) {noformat} The problem seems to really be in the outdated standalone-xts.xml file and not in JBossXTS itself since it works correctly when the following patch is applied to standalone-full.xml: {noformat} --- a/standalone-full.xml +++ b/standalone-full.xml @@ -29,6 +29,7 @@ <extension module="org.jboss.as.web"/> <extension module="org.jboss.as.webservices"/> <extension module="org.jboss.as.weld"/> + <extension module="org.jboss.as.xts"/> </extensions> <management> @@ -384,6 +385,9 @@ </endpoint-config> </subsystem> <subsystem xmlns="urn:jboss:domain:weld:1.0"/> + <subsystem xmlns="urn:jboss:domain:xts:1.0"> + <xts-environment url="http://localhost:8080/ws-c11/ActivationService"/> + </subsystem> </profile> <interfaces> {noformat} -- 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

13 years, 10 months

12
17
0 / 0

[JBoss JIRA] (AS7-2579) system property replacement doesn't work

by Radim Hanus (Created) (JIRA)

system property replacement doesn't work ---------------------------------------- Key: AS7-2579 URL: https://issues.jboss.org/browse/AS7-2579 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final Environment: jdk1.6.0_29 Reporter: Radim Hanus property replacement doesn't work in both standalone.xml and persistence.xml details in forum thread -- 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

13 years, 10 months

6
11
0 / 0

[JBoss JIRA] (AS7-2456) Deploying an OSGi bundle with JAX-RS annotations causes an exception

by David Bosschaert (Created) (JIRA)

Deploying an OSGi bundle with JAX-RS annotations causes an exception -------------------------------------------------------------------- Key: AS7-2456 URL: https://issues.jboss.org/browse/AS7-2456 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: David Bosschaert Assignee: Thomas Diesler While trying to get the CXF-DOSGi REST sample (http://cxf.apache.org/distributed-osgi.html) to work in AS7 I noticed that deploying an OSGi bundle with JAX-RS annotations causes an exception. It seems that the AS7 JAX-RS subsystem is trying to take hold of it without success. Should the AS7 JAX-RS subsystem try to process the deployment if it is an OSGi bundle? The exception observed is: {code}22:03:46,219 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar" 22:03:46,271 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar".POST_MODULE: Failed to process phase POST_MODULE of deployment "cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] 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] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] Caused by: java.lang.NullPointerException at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:101) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] ... 5 more 22:03:46,274 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\""}} 22:03:46,280 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar in 6ms 22:03:46,282 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.\"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"cxf-dosgi-ri-samples-greeter-rest-interface-1.3-SNAPSHOT.jar\""}}}} {code} -- 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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (AS7-3552) Specifying the batching attribute on caches enables transactions all the time (for whatever value of batching)

by Tristan Tarrant (JIRA)

Tristan Tarrant created AS7-3552: ------------------------------------ Summary: Specifying the batching attribute on caches enables transactions all the time (for whatever value of batching) Key: AS7-3552 URL: https://issues.jboss.org/browse/AS7-3552 Project: Application Server 7 Issue Type: Bug Reporter: Tristan Tarrant Assignee: Paul Ferraro Priority: Critical >From CacheAdd.java if (cache.hasDefined(ModelKeys.BATCHING)) { InvocationBatchingConfigurationBuilder batchingBuilder = builder.transaction().transactionMode(org.infinispan.transaction.TransactionMode.TRANSACTIONAL).invocationBatching(); if (cache.get(ModelKeys.BATCHING).asBoolean()) { batchingBuilder.enable(); } else { batchingBuilder.disable(); } } -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-3535) Fix average-processing-time issue

by Richard Opalka (JIRA)

Richard Opalka created AS7-3535: ----------------------------------- Summary: Fix average-processing-time issue Key: AS7-3535 URL: https://issues.jboss.org/browse/AS7-3535 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1b, 7.1.0.CR1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.1.0.Final This average-processing-time statistics code is calling wrong statistics method of our runtime. -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3369) Array-accessing constraints can't be jit-optimized

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3369: --------------------------------------- Summary: Array-accessing constraints can't be jit-optimized Key: JBRULES-3369 URL: https://issues.jboss.org/browse/JBRULES-3369 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.4.0.Beta1 Reporter: Davide Sottara Assignee: Mario Fusco -- 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

by John Bailey (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] John Bailey resolved AS7-1338. ------------------------------ Resolution: Done > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Components: Naming > Reporter: Richard Opalka > Assignee: John Bailey > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.0.Final > > > Add support for remote JNDI after all. It was agreed that: > * Remote JNDI would run over Remoting > * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:" > * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else > * Server-side services would opt-in to Remote JNDI; initially we'd only support: > ** Remote EJB interfaces > ** HornetQ connection factories > * In the future we may support: > ** User bindings, so long as they're serializable > * In the future we will never support: > ** Proxied DataSources > ** Proxied JMS invocations > Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now. -- 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

13 years, 10 months

1
0
0 / 0

[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

13 years, 10 months

2
7
0 / 0

[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

13 years, 10 months

4
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012