July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9351) Description Providers for OSGi subsystem

by Kabir Khan (JIRA)

Description Providers for OSGi subsystem ---------------------------------------- Key: JBAS-9351 URL: https://issues.jboss.org/browse/JBAS-9351 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Thomas Diesler Fix For: 7.0.0.Beta4 The OSGi subsystem needs to provide its descriptions, if I do this in the command line tool: :read-resource-description(recursive=1,operations=1,inherited=0) osgi currently does not give any meaningful descriptions of either its model or operations: ... "osgi" => {"operations" => {"add" => undefined}}, ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1137) ClusterChooserInterceptor does not support transaction failover authorisations

by Galder Zamarreno (JIRA)

ClusterChooserInterceptor does not support transaction failover authorisations ------------------------------------------------------------------------------ Key: EJBTHREE-1137 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1137 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno org.jboss.aspects.remoting.ClusterChooserInterceptor does not contain logic to deal with transaction failover authorisations, contrary to legacy JRMP invoker or Unified invoker. The reason I'm entering this as a bug rather than as a feature request is because not having such logic is allowing failovers when they shouldn't happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1141) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Galder Zamarreno (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: EJBTHREE-1141 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1141 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Create EJB3 transaction sticky load balance policies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1205) Remove URL handler warnings at startup

by Thomas Diesler (JIRA)

Remove URL handler warnings at startup -------------------------------------- Key: AS7-1205 URL: https://issues.jboss.org/browse/AS7-1205 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler 14:01:59,833 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-1) Unable to set the URLStreamHandlerFactory 14:01:59,834 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-1) Unable to set the ContentHandlerFactory -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1134) OSGi XService intergration cannot be used with Maven snapshots

by David Bosschaert (JIRA)

OSGi XService intergration cannot be used with Maven snapshots -------------------------------------------------------------- Key: AS7-1134 URL: https://issues.jboss.org/browse/AS7-1134 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: David Bosschaert When using OSGi XServices, for instance to invoke an OSGi service from a Servlet, the user needs to add an extra dependency to the manifest in the Dependencies header. For instance the following Maven instruction in the maven-war-plugin can be used to do this: <Dependencies>org.osgi.core,org.jboss.modules,org.jboss.logging,deployment.jboss-as-web-osgi-api-bundle:${project.version}</Dependencies> This works fine for release versions, such as 7.0.0, however it causes issues with SNAPSHOT versions as 7.0.0-SNAPSHOT gets translated into 7.0.0.SNAPSHOT on the OSGi level while the MSC dependency mechanism is looking for 7.0.0-SNAPSHOT and hence can't find it. For more context see the following console output: 17:03:32,149 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: jboss-as-web-osgi-api-bundle:7.0.0.SNAPSHOT 17:03:32,153 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-15) Bundle started: jboss-as-web-osgi-api-bundle:7.0.0.SNAPSHOT 17:03:32,180 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "jboss-as-web-osgi-api-bundle-7.0.0-SNAPSHOT.jar" 17:04:17,253 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) Starting deployment of "jboss-as-web-osgi-war.war" 17:04:17,287 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "jboss-as-web-osgi-war.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"jboss-as-web-osgi-war.war\".CONFIGURE_MODULE"]} 17:04:17,287 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report New missing/unsatisfied dependencies: service jboss.module.information.service."deployment.jboss-as-web-osgi-api-bundle"."7.0.0-SNAPSHOT" (missing) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1144) Document how to change the default user name and password for the Felix Web Console

by David Bosschaert (JIRA)

Document how to change the default user name and password for the Felix Web Console ----------------------------------------------------------------------------------- Key: AS7-1144 URL: https://issues.jboss.org/browse/AS7-1144 Project: Application Server 7 Issue Type: Task Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Optional Currently the Felix Web Console operates under the default username and password (admin/admin). We need to document how to change this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1143) Should pre-populated modules a high start level be loaded in lower start levels?

by David Bosschaert (JIRA)

Should pre-populated modules a high start level be loaded in lower start levels? -------------------------------------------------------------------------------- Key: AS7-1143 URL: https://issues.jboss.org/browse/AS7-1143 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Optional A number of modules are specified to be pre-loaded in the OSGi framework in the <modules> section of the osgi subsystem configuration. {code}<modules> <module identifier="javaee.api"/> <module identifier="org.jboss.logging"/> <module identifier="org.apache.aries.util"/> <module identifier="org.jboss.osgi.webconsole"/> <module identifier="org.osgi.compendium"/> <module identifier="org.apache.felix.log" startlevel="1"/> <module identifier="org.jboss.osgi.logging" startlevel="1"/> <module identifier="org.apache.felix.configadmin" startlevel="1"/> <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/> <module identifier="org.apache.aries.jmx" startlevel="2"/> <module identifier="org.apache.felix.eventadmin" startlevel="2"/> <module identifier="org.apache.felix.metatype" startlevel="2"/> <module identifier="org.apache.felix.webconsole" startlevel="2"/> <module identifier="org.jboss.osgi.jmx" startlevel="2"/> <module identifier="org.jboss.osgi.http" startlevel="2"/> <module identifier="org.jboss.osgi.blueprint" startlevel="3"/> <module identifier="org.jboss.osgi.webapp" startlevel="3"/> <module identifier="org.jboss.osgi.xerces" startlevel="3"/> </modules>{code} Currently all modules are loaded, regardless of start level and only those that have a start level <= the current one are actually started. I wonder whether this is desirable. When a module has a startlevel specified, it clearly needs to be started and is likely not useful when not started. It would therefore make sense to me to not pre-load modules with a higher start level, but only load these once their start level is being reached. This would improve subsystem start times too... I.e. even when start level 1 is specified, the following output appears when the framework is started: {code}13:52:28,008 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: system.bundle:0.0.0 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: javaee.api:0.0.0 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-10) Install bundle: org.jboss.logging:3.0.0 13:52:28,133 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: jboss-as-osgi-configadmin:7.0.0.CR1 13:52:28,137 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-webconsole:1.0.6 13:52:28,140 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-12) Install bundle: jboss-osgi-logging:1.0.0 13:52:28,176 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-7) Install bundle: jboss-osgi-jmx:1.0.10 13:52:28,204 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-5) Install bundle: org.apache.felix.metatype:1.0.4 13:52:28,219 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8 13:52:28,228 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: org.apache.aries.util:0.3.0 13:52:28,229 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: org.apache.aries.jmx:0.3.0 13:52:28,237 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: org.apache.felix.log:1.0.0 13:52:28,240 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-16) Install bundle: jbosgi-blueprint:1.0.2 13:52:28,313 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webapp:1.0.2 13:52:28,325 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.apache.felix.eventadmin:1.2.6 13:52:28,333 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-9) Install bundle: jboss-osgi-xerces:2.9.1.SP7 13:52:28,368 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-13) Install bundle: org.apache.felix.webconsole:3.1.6.SP1 13:52:28,394 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-15) Install bundle: jboss-osgi-http:1.0.3 13:52:28,460 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.cmpn:4.2.0.200908310645 {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1222) Subsystem developers guide

by Brian Stansberry (JIRA)

Subsystem developers guide -------------------------- Key: AS7-1222 URL: https://issues.jboss.org/browse/AS7-1222 Project: Application Server 7 Issue Type: Task Reporter: Brian Stansberry Assignee: Kabir Khan Fix For: 7.0.1.Final A guide on how to develop an AS7 extension/subsystem and a maven archetype for same. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1172) JNDI

by Alexandre Gattiker (JIRA)

JNDI ----- Key: AS7-1172 URL: https://issues.jboss.org/browse/AS7-1172 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.CR1 Reporter: Alexandre Gattiker If a JMS destination is created with a JNDI name starting with "/jms/", the JNDI View issues an error message. The destination appears to be up and running fine though. <h1>java: Namespace</h1> <pre> +- topic (class: javax.naming.Context) | +- test (class: org.jboss.as.naming.context.ModularReference) +- app (class: javax.naming.Reference) +- module (class: javax.naming.Reference) +- comp (class: javax.naming.Reference) +- queue (class: javax.naming.Context) | +- test (class: org.jboss.as.naming.context.ModularReference) +- jms (class: javax.naming.Context) Failed to lookup: jms, errmsg=Name 'jms' not found in context '' +- global (class: javax.naming.Reference) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1360) Incorrect soap:address connector port generated in WSDL for JAX-WS service

by Abhijit Sarkar (JIRA)

Incorrect soap:address connector port generated in WSDL for JAX-WS service -------------------------------------------------------------------------- Key: AS7-1360 URL: https://issues.jboss.org/browse/AS7-1360 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.0.0.Final Environment: Ubuntu 11.04, JBoss AS 7.0.0.Final, RESTEasy 2.2.1.GA Reporter: Abhijit Sarkar Assignee: Alessio Soldano Default soap:address connector port generated in WSDL even though server is running on a different HTTP port. Please see forum reference for detail. ?? jaikiran pai wrote: Please open a JIRA for this. The way the connector port is being inferred from the configured connectors, from the JBoss WS code, will not work in AS7. ?? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011