[JBoss JIRA] (AS7-5453) Server restart fails with persistent WAB deployment
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5453:
-----------------------------------
Summary: Server restart fails with persistent WAB deployment
Key: AS7-5453
URL: https://issues.jboss.org/browse/AS7-5453
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: 7.2.0.Alpha1
{code}
04:55:16,854 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.0.0.CR21
04:55:17,211 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
04:55:17,219 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
04:55:17,228 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.0
04:55:17,228 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.2.8
04:55:17,479 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: updated-bundle.wab:1.0.1
04:55:17,922 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."updated-bundle.wab".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."updated-bundle.wab".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "updated-bundle.wab"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: java.lang.NullPointerException
at org.jboss.as.osgi.web.WabServletContextServiceProcessor.registerServletContext(WabServletContextServiceProcessor.java:58)
at org.jboss.as.osgi.web.WabServletContextServiceProcessor.deploy(WabServletContextServiceProcessor.java:52)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
04:55:17,938 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011011: Starting bundles for start level: 1
04:55:17,987 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "updated-bundle.wab"
04:55:18,009 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
04:55:18,049 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.0
04:55:18,068 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0
04:55:18,100 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
04:55:18,102 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: updated-bundle.wab:1.0.1
04:55:18,115 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011000: OSGi Framework started
{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
13 years, 8 months
[JBoss JIRA] (JBAS-9515) Server Does Not Boot
by Gautam Banerjee (JIRA)
Gautam Banerjee created JBAS-9515:
-------------------------------------
Summary: Server Does Not Boot
Key: JBAS-9515
URL: https://issues.jboss.org/browse/JBAS-9515
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.1.0.GA
Reporter: Gautam Banerjee
Assignee: Scott Stark
Hi,
We have Jboss 5.1 installed on mainframe s390x with JRE 1.7 64 bit with Teiid 7.7.1 . We have dynamic vdb installed programmatically and the server starts fine. When we stop and restart the server it does not boot and gives the stack trace
03 Sep 2012 14:35:35,000 GMT ERROR [org.jboss.system.server.profileservice.repository.ScopedProfileServiceController] (main) Error installing to Deploy: name=ProfileKey@d4d1d65[domain=default, server=default, name=applications] state=Start mode=On Demand requiredState=Installed
java.lang.NullPointerException
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:775)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:769)
03 Sep 2012 14:35:35,273 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,273 DEBUG main SysErrStream:27 **************************************Failed to boot JBoss:
03 Sep 2012 14:35:35,274 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,273 DEBUG main SysErrStream:27 **************************************java.lang.IllegalStateException: Incompletely deployed:
*** PROFILES IN ERROR: Name -> Error
Profile: ProfileKey@d4d1d65[domain=default, server=default, name=applications] in error due to java.lang.NullPointerException
*** PROFILES MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
ProfileKey@d0e5472[domain=default, server=default, name=default] is missing following dependencies: ProfileKey@d4d1d65[domain=default, server=default, name=applications]{Installed:**ERROR**}
03 Sep 2012 14:35:35,274 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,274 DEBUG main SysErrStream:27 ************************************** at org.jboss.system.server.profileservice.repository.AbstractProfileService.logErrors(AbstractProfileService.java:567)
03 Sep 2012 14:35:35,274 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,274 DEBUG main SysErrStream:27 ************************************** at org.jboss.system.server.profileservice.repository.AbstractProfileService.validate(AbstractProfileService.java:348)
03 Sep 2012 14:35:35,275 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,275 DEBUG main SysErrStream:27 ************************************** at org.jboss.system.server.profileservice.repository.AbstractProfileService.validateProfile(AbstractProfileService.java:331)
03 Sep 2012 14:35:35,275 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,275 DEBUG main SysErrStream:27 ************************************** at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:272)
03 Sep 2012 14:35:35,276 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,275 DEBUG main SysErrStream:27 ************************************** at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
03 Sep 2012 14:35:35,276 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,276 DEBUG main SysErrStream:27 ************************************** at org.jboss.Main.boot(Main.java:221)
03 Sep 2012 14:35:35,276 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,276 DEBUG main SysErrStream:27 ************************************** at org.jboss.Main$1.run(Main.java:556)
03 Sep 2012 14:35:35,277 GMT INFO [STDOUT] (main) 03 Sep 2012 14:35:35,276 DEBUG main SysErrStream:27 ************************************** at java.lang.Thread.run(Thread.java:769)
--
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
13 years, 8 months
[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, 8 months
[JBoss JIRA] (AS7-5480) Add option to exclude attribute from add operation
by Tomaz Cerar (JIRA)
Tomaz Cerar created AS7-5480:
--------------------------------
Summary: Add option to exclude attribute from add operation
Key: AS7-5480
URL: https://issues.jboss.org/browse/AS7-5480
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.2.0.Alpha1
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Fix For: 7.2.0.Alpha1
There are cases when we want to have attribute only present on resource but want them excluded from add operations.
current implementation of DefaultResourceAddDescriptionProvider adds all attributes on resource also to Add operation
We should add an extra flag to AttributeDefinitionBuilder as a signal to DefaultResourceAddDescriptionProvider to not include the parameter, e.g.:
public static final AttributeDefinition NAME = SimpleAttributeDefinitionBuilder.create(ModelDescriptionConstants.NAME, ModelType.STRING, false)
.resourceOnly()
.build();
this would not appear in the model, simply be a field in AttributeDefinition.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-3992) Improve formatting of command line help
by Paul Gier (JIRA)
Paul Gier created AS7-3992:
------------------------------
Summary: Improve formatting of command line help
Key: AS7-3992
URL: https://issues.jboss.org/browse/AS7-3992
Project: Application Server 7
Issue Type: Enhancement
Components: Console
Affects Versions: 7.1.0.Final
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: 7.1.1.Final
For command line parameters where there is both a short or a long version of the same option, the short and long version should be comma separated. This is similar to how many command line tools display help or in man pages.
Current output:
{noformat}
-h Display this message and exit
--help Display this message and exit
{noformat}
Suggested output:
{noformat}
-h, --help Display this message and exit
{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, 8 months
[JBoss JIRA] (AS7-5473) ejb timer not cleared after undeploy causing the redeploy to fail
by Cheng Fang (JIRA)
Cheng Fang created AS7-5473:
-------------------------------
Summary: ejb timer not cleared after undeploy causing the redeploy to fail
Key: AS7-5473
URL: https://issues.jboss.org/browse/AS7-5473
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.2.0.Alpha1
Reporter: Cheng Fang
Assignee: jaikiran pai
The app has some @Schedule timers, and was deployed, and undeployed, and restart as7. These timers are not cleared after the undeploy. Then I updated my app, removing/modifying the timeout methods, and redeploy it --force. It failed, complaining about the missing timeout methods, which have been changed/removed in the newer version of my app:
{noformat}
10:27:22,934 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."test.war".component.TestBean.ejb3.timerService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".component.TestBean.ejb3.timerService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
Caused by: java.lang.IllegalStateException: JBAS014478: Could not find timeout method: test.TestBean.saturdayNight(javax.ejb.Timer)
at org.jboss.as.ejb3.timerservice.CalendarTimer.<init>(CalendarTimer.java:139)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:907)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:634)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.start(TimerServiceImpl.java:191)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
10:27:23,140 INFO [org.jboss.as.server] (management-handler-thread - 6) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".component.TestBean.ejb3.timerService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".component.TestBean.ejb3.timerService: Failed to start service
Caused by: java.lang.IllegalStateException: JBAS014478: Could not find timeout method: test.TestBean.saturdayNight(javax.ejb.Timer)"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.deployment.default-host./test Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"test.war\".component.TestBean.START Missing[JBAS014861: <one or more transitive dependencies>]"]}
10:27:23,152 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 11ms
{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
13 years, 8 months