January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-931) Logical addresses: canonicalize UUIDs with IDs (shorts)

by Bela Ban (JIRA)

Logical addresses: canonicalize UUIDs with IDs (shorts) ------------------------------------------------------- Key: JGRP-931 URL: https://jira.jboss.org/jira/browse/JGRP-931 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 Instead of using UUIDs as addresses, the cluster members should agree on shorts, e.g. 1 for A, 2 for B and so on, and use these instead of UUIDs. This happens after a certain warmup time. E.g. the coord could assign these IDs, so they're unique. IdAddress and UUID have to be able to do equals() or compareTo() with each other ! Advantage: - we send a short (2 bytes) instead of a UUID (16 bytes) - we use an IdAddress (class with a short) instead of a UUID. This is 6 bytes less per instance - IdAddress might be faster with equals() and hashCode() than UUID -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
12
0 / 0

[JBoss JIRA] Created: (JGRP-1370) Use variable-length encoding for primitive data types int, long, short

by Bela Ban (JIRA)

Use variable-length encoding for primitive data types int, long, short ---------------------------------------------------------------------- Key: JGRP-1370 URL: https://issues.jboss.org/browse/JGRP-1370 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 Use variable-length encoding [1], to compress data on the wire even more. We currently compress longs and long ranges, but prefix them with a length byte. Using variable-length encoding, we can save that byte for most values. [1] http://lucene.apache.org/java/2_4_0/fileformats.html#VInt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] (AS7-3152) Cannot deploy OSGI bundle with datasource

by Peter Penzov (Created) (JIRA)

Cannot deploy OSGI bundle with datasource ------------------------------------------ Key: AS7-3152 URL: https://issues.jboss.org/browse/AS7-3152 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.1.0.CR1b Environment: Centos 5.6, JBoss 7.1.0CR1b, Netbeans 7.1 Reporter: Peter Penzov Assignee: Thomas Diesler Priority: Blocker I cannot deploy OSGI bundle with defined datasource. This is the error stack: [root@Testserver bin]# [root@Testserver bin]# ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /opt/jboss-as-7.1.0.CR1b JAVA: /opt/jdk1.7.0_01/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 17:15:59,245 INFO [org.jboss.modules] JBoss Modules version 1.1.0.CR6 17:15:59,603 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA 17:15:59,664 INFO [org.jboss.as] JBoss AS 7.1.0.CR1b "Flux Capacitor" starting 17:16:01,027 INFO [org.jboss.as] Creating http management service using socket-binding (management-http) 17:16:01,028 INFO [org.xnio] XNIO Version 3.0.0.CR7 17:16:01,041 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.0.CR7 17:16:01,055 INFO [org.jboss.remoting] JBoss Remoting version 3.2.0.CR8 17:16:01,074 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers 17:16:01,132 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 17:16:01,166 INFO [org.jboss.as.clustering] (ServerService Thread Pool -- 30) JBAS010300: Activating Infinispan subsystem. 17:16:01,168 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011910: Activating OSGi Subsystem 17:16:01,198 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) Activating Security Subsystem 17:16:01,219 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.6.Final) 17:16:01,251 INFO [org.jboss.as.security] (MSC service thread 1-3) Picketbox version=4.0.6.Beta2 17:16:01,425 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) JBossOSGi Framework Core - 1.1.0 17:16:01,460 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension 17:16:01,492 INFO [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /10.10.10.6:4447 17:16:01,411 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem 17:16:01,616 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service 17:16:01,617 INFO [org.jboss.as.jaxr] (MSC service thread 1-1) Binding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory 17:16:01,662 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] 17:16:01,727 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: system.bundle:0.0.0 17:16:01,823 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.0.GA 17:16:01,881 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--10.10.10.6-8080 17:16:02,209 WARN [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011918: Found OSGi bundle in modules hierarchy: /opt/jboss-as-7.1.0.CR1b/modules/org/jboss/netty/main/netty-3.2.5.Final.jar 17:16:02,419 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.metatype:1.0.4 17:16:02,456 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jbosgi-webconsole:1.0.6 17:16:02,511 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.aries.jmx:0.3.0 17:16:02,592 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.configadmin:1.2.8 17:16:02,612 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-as-osgi-configadmin:7.1.0.CR1b 17:16:02,640 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: javax.transaction.api:0.0.0 17:16:02,674 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-jmx:1.0.10 17:16:03,423 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: stilts-stomplet-server-bundle:0.1.20 17:16:03,425 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.scr:1.6.0 17:16:03,534 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.log:1.0.0 17:16:03,543 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.aries.util:0.3.0 17:16:03,788 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webapp:1.0.5 17:16:03,790 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: javax.servlet.api:0.0.0 17:16:03,950 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-xerces:2.9.1.SP7 17:16:04,030 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.jboss.netty:3.2.5.Final 17:16:04,093 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-blueprint:1.0.3 17:16:04,107 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-logging:1.0.0 17:16:04,109 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: javax.api:0.0.0 17:16:04,164 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.webconsole:3.1.6.SP1 17:16:04,389 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.eventadmin:1.2.6 17:16:04,482 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "SH_15-1.0-SNAPSHOT.jar" 17:16:04,497 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.0.CR1b/standalone/deployments 17:16:04,571 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-http:1.0.5 17:16:04,592 INFO [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /10.10.10.6:9999 17:16:04,802 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.cmpn:4.2.0.200908310645 17:16:04,873 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-4) Starting bundles for start level: 1 17:16:04,892 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named SessionHandle in deployment unit deployment "SH_15-1.0-SNAPSHOT.jar" are as follows: java:global/SH_15-1.0-SNAPSHOT/SessionHandle!com.SH_15.SessionHandle java:app/SH_15-1.0-SNAPSHOT/SessionHandle!com.SH_15.SessionHandle java:module/SessionHandle!com.SH_15.SessionHandle java:global/SH_15-1.0-SNAPSHOT/SessionHandle java:app/SH_15-1.0-SNAPSHOT/SessionHandle java:module/SessionHandle 17:16:05,351 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-osgi-logging:1.0.0 17:16:05,438 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-as-osgi-configadmin:7.1.0.CR1b 17:16:05,479 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.log:1.0.0 17:16:05,507 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.configadmin:1.2.8 17:16:05,508 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-4) Starting bundles for start level: 2 17:16:05,558 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.scr:1.6.0 17:16:05,637 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.jboss.netty:3.2.5.Final 17:16:05,707 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.eventadmin:1.2.6 17:16:05,896 INFO [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.ops4j.pax.web)) jetty-7.x.y-SNAPSHOT 17:16:05,966 INFO [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.ops4j.pax.web)) Started NIOSocketConnectorWrapper@0.0.0.0:8090 17:16:05,980 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jbosgi-http:1.0.5 17:16:06,037 INFO [org.projectodd.stilts.stomplet.bundle.StompletServerActivator] (MSC service thread 1-4) start: BundleContext[stilts-stomplet-server-bundle:0.1.20] 17:16:06,050 INFO [org.projectodd.stilts.stomplet.bundle.StompletServerActivator] (MSC service thread 1-4) adding transaction manager: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@7e8c37b3 17:16:06,054 INFO [org.projectodd.stilts.stomplet.server.StompletServer] (MSC service thread 1-4) STOMPLET_SERVER start() 17:16:06,054 ERROR [org.projectodd.stilts.conduit.ConduitServer] (MSC service thread 1-4) CONDUIT_SERVER.start com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@7e8c37b3 17:16:06,127 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: stilts-stomplet-server-bundle:0.1.20 17:16:06,228 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-osgi-jmx:1.0.10 17:16:06,240 INFO [org.apache.aries.jmx] (Thread-64) Starting JMX OSGi agent 17:16:06,259 INFO [org.apache.aries.jmx] (Thread-64) Registering MBean with ObjectName [osgi.compendium:service=cm,version=1.3] for service with service.id [13] 17:16:06,271 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.aries.jmx:0.3.0 17:16:06,377 INFO [org.apache.aries.jmx] (Thread-64) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@4a272157 with name osgi.compendium:service=cm,version=1.3 17:16:06,377 INFO [org.apache.aries.jmx] (Thread-64) Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@4a272157 with name osgi.core:type=packageState,version=1.5 17:16:06,378 INFO [org.apache.aries.jmx] (Thread-64) Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@4a272157 with name osgi.core:type=serviceState,version=1.5 17:16:06,409 INFO [org.apache.aries.jmx] (Thread-64) Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@4a272157 with name osgi.core:type=bundleState,version=1.5 17:16:06,411 INFO [org.apache.aries.jmx] (Thread-64) Registering org.osgi.jmx.framework.FrameworkMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@4a272157 with name osgi.core:type=framework,version=1.5 17:16:06,638 INFO [org.eclipse.jetty.util.log] (MSC service thread 1-4) started HttpServiceContext{httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext@108b0d7d} 17:16:06,686 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.webconsole:3.1.6.SP1 17:16:06,703 INFO [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.apache.felix.webconsole.internal.servlet.OsgiManager)) stopped HttpServiceContext{httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext@108b0d7d} 17:16:06,705 INFO [org.eclipse.jetty.util.log] (CM Configuration Updater (ManagedService Update: pid=org.apache.felix.webconsole.internal.servlet.OsgiManager)) started HttpServiceContext{httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext@7903d594} 17:16:06,763 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.metatype:1.0.4 17:16:06,764 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-4) Starting bundles for start level: 3 17:16:06,876 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jbosgi-blueprint:1.0.3 17:16:06,975 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jbosgi-webapp:1.0.5 17:16:07,156 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-osgi-xerces:2.9.1.SP7 17:16:07,158 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-4) OSGi Framework started 17:16:07,375 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "SH_15-1.0-SNAPSHOT.jar" 17:16:07,379 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.jdbc-driver._ojdbc6_jar (missing) dependents: [service jboss.data-source.java:/Oracle] 17:16:07,385 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1b "Flux Capacitor" started (with errors) in 8372ms - Started 160 of 234 services (3 services failed or missing dependencies, 69 services are passive or on-demand) 17:16:07,392 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "_ojdbc6.jar" 17:16:07,619 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2) 17:16:07,654 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/Oracle] 17:16:07,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "_ojdbc6.jar" 17:16:07,725 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014776: Newly corrected services: service jboss.jdbc-driver._ojdbc6_jar (no longer required) 17:16:29,174 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment SH_15-1.0-SNAPSHOT.jar in 20ms 17:16:29,188 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS018558: Undeployed "SH_15-1.0-SNAPSHOT.jar" 17:16:29,188 INFO [org.jboss.as.server.deployment.repository.impl] (HttpManagementService-threads - 1) JBAS014901: Content removed from location /opt/jboss-as-7.1.0.CR1b/standalone/data/content/95/13516bb68ff3a569140babc910dcf21b0b2f24/content 17:17:18,856 INFO [org.jboss.as.server.deployment.repository.impl] (HttpManagementService-threads - 1) JBAS014900: Content added at location /opt/jboss-as-7.1.0.CR1b/standalone/data/content/c6/30f0ab7b40ff39918a61ff080d09e135dd59a1/content 17:17:22,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "test-1.0-SNAPSHOT.jar" 17:17:22,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."test-1.0-SNAPSHOT.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-1.0-SNAPSHOT.jar".POST_MODULE: Failed to process phase POST_MODULE of deployment "test-1.0-SNAPSHOT.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] 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.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] Caused by: java.lang.NullPointerException at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.isEnvEntryType(ResourceInjectionAnnotationParsingProcessor.java:296) at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.process(ResourceInjectionAnnotationParsingProcessor.java:227) at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.processFieldResource(ResourceInjectionAnnotationParsingProcessor.java:184) at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.deploy(ResourceInjectionAnnotationParsingProcessor.java:146) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] ... 5 more 17:17:22,045 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015856: Undeploy of deployment "test-1.0-SNAPSHOT.jar" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test-1.0-SNAPSHOT.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test-1.0-SNAPSHOT.jar\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"test-1.0-SNAPSHOT.jar\""}} 17:17:22,121 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment test-1.0-SNAPSHOT.jar in 75ms 17:17:22,122 INFO [org.jboss.as.controller] (HttpManagementService-threads - 1) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."test-1.0-SNAPSHOT.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-1.0-SNAPSHOT.jar".POST_MODULE: Failed to process phase POST_MODULE of deployment "test-1.0-SNAPSHOT.jar" -- 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, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1975) Initial OSGi JPA implementation

by Thomas Diesler (JIRA)

Initial OSGi JPA implementation ------------------------------- Key: EJBTHREE-1975 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1975 Project: EJB 3.0 Issue Type: Feature Request Reporter: Thomas Diesler Part of Enterprise OSGi there is JPA specification that we would like to have support for. This issue is the entry point for the initial implementation. Apache Aries ------------------ http://wiki.apache.org/incubator/AriesProposal Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a Java persistence project. It is related to Aries as a JPA persistence provider, including entity scanning and enhancement. The Aries project will make it easy for JPA persistence providers such as OpenJPA to be used in an OSGi environment and will provide container managed persistence for the Blueprint container. Eclipse Gemini -------------------- http://eclipse.org/proposals/gemini/ The subprojects will be created with the following initial IP components and donating companies: * Blueprint Service Implementation — SpringSource * Web Container Integration code — SpringSource * JPA Integration code for EclipseLink — Oracle * Implementation of JMX Mbeans and composite data types — Oracle * Derby JDBC Service Implementation — Oracle * JNDI Service Integration code — Oracle http://www.eclipse.org/eclipselink/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
14
0 / 0

[JBoss JIRA] Created: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format

by Paul Gier (JIRA)

Migrate existing Nexus Audit information to standard XML format --------------------------------------------------------------- Key: JBBUILD-670 URL: https://issues.jboss.org/browse/JBBUILD-670 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: John Casey Fix For: Build Support 2011 We currently have audit information (username, timestamp) stored in .json files in the repository. Nexus uses an XML format to store this information, and recent versions of Nexus allow easy way to view this information in the Nexus UI. The existing audit information should be migrated to the standard Nexus XML format. These XML files are located in the directory "sonatype-work/nexus/proxy/attributes". For each file in each Maven repository hosted by Nexus, there is a file with the same name in this attributes directory. For example, "sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar" is actually an XML file containing the attributes for the named jar file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
9
0 / 0

[JBoss JIRA] Created: (JBBUILD-523) Issues with custom packaging in maven

by Paul Gier (JIRA)

Issues with custom packaging in maven ------------------------------------- Key: JBBUILD-523 URL: https://jira.jboss.org/jira/browse/JBBUILD-523 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2009 Steve ran into some issues when using custom packaging for the jdocbook plugin. - Transitive dependency resolution does not work - Two dependencies with the same packaging but different artifact handlers cannot both be resolved, because no info about the handler is encoded into the repo - The plugin containing the custom packaging needs to programmatically register the artifact handler in addition to specifiying it in the components.xml this has to be done by: (1) retrieve the handler using @parameter expression="${component.org.apache.maven.artifact.handler.ArtifactHandler#jdocbook-style}" (2) manually register it using project.getArtifact().setArtifactHandler( artifactHandler ); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1326) Cannot redeploy OSGi bundle that is wired to webapp

by Thomas Diesler (JIRA)

Cannot redeploy OSGi bundle that is wired to webapp --------------------------------------------------- Key: AS7-1326 URL: https://issues.jboss.org/browse/AS7-1326 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Final Reporter: Thomas Diesler Assignee: Thomas Diesler {code} 09:12:12,719 ERROR [org.jboss.msc.service] (MSC service thread 1-1) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@2789a406" failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.jboss-osgi-example-jbossas-bundle"."0.0.0" is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) at org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:122) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:340) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:225) at org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:248) at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:226) at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:161) at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:146) at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:121) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (AS7-735) Failed OSGi deployments still show as .deployed in hotdeploy folder

by David Bosschaert (JIRA)

Failed OSGi deployments still show as .deployed in hotdeploy folder ------------------------------------------------------------------- Key: AS7-735 URL: https://issues.jboss.org/browse/AS7-735 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Assignee: Jason Greene When deploying a bundle in AS7 in the hotdeploy directory that has missing dependencies and therefore fails the OSGi resolution process, the deployment still shows up as deployed successfully (a .deployed file appears). I think it should be marked as .failed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
15
0 / 0

[JBoss JIRA] Created: (JGRP-1302) RELAY: issues with shared transport

by Bela Ban (JIRA)

RELAY: issues with shared transport ----------------------------------- Key: JGRP-1302 URL: https://issues.jboss.org/browse/JGRP-1302 Project: JGroups Issue Type: Task Affects Versions: 2.12 Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12.1 JBoss 6 creates a separate channel for each of its webapps that are marked as <distributable/> when mode=distribution. The reason is outlined in https://issues.jboss.org/browse/ISPN-658. This is a problem if we have for example a stack called "relay" (and in infinispan-configs.xml the "web" configuration refers to "relay"), and the transport is shared (singleton_name is set): - webapp web.war is deployed - A channel for web.war is created by Infinispan - The channel creates the shared transport and RELAY establishes the TCP bridge cluster as first member - Webapp SessionDemo.war is deployed - A new channel is created. The shared transport is not initialized again, as it already was for web.war - However, RELAY joins the TCP bridge cluster and thus is in the same cluster as web.war ! ==> However, both subclusters are named the same ! This leads to issues -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
5
0 / 0

[JBoss JIRA] (AS7-3107) Not all CDI scopes available to MDB's

by Stuart Douglas (Created) (JIRA)

Not all CDI scopes available to MDB's ------------------------------------- Key: AS7-3107 URL: https://issues.jboss.org/browse/AS7-3107 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.0.Final -- 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, 8 months

4
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012