1 2 Previous Next 20 Replies Latest reply on Dec 12, 2008 12:15 PM by ilango gurusamy

    UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **

    Nanda Kishore Newbie

      Hi i am getting this error when i am deploying ear file. I did not modified timer service can i know how to solve this problem.


      *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
      
      jboss.ejb:persistencePolicy=database,service=EJBTimerService
       -> jboss.jdbc:datasource=DefaultDS,service=metadata{Start:** NOT FOUND **}
       -> jboss.jca:name=DefaultDS,service=DataSourceBinding{Start:** NOT FOUND **}
       -> jboss.jca:name=DefaultDS,service=DataSourceBinding{Create:** NOT FOUND **}
       -> jboss.jdbc:datasource=DefaultDS,service=metadata{Create:** NOT FOUND **}
      
      jboss.ejb:service=EJBTimerService
       -> jboss.ejb:persistencePolicy=database,service=EJBTimerService{Create:Configured}
       -> jboss.ejb:persistencePolicy=database,service=EJBTimerService{Start:Configured}
      
      jboss.j2ee:ear=iBlue.ear,jar=iBlue-ejb.jar,name=TemperatureFacade,service=EJB3
       -> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **}
      
      jboss.jca:name=JmsXA,service=ConnectionFactoryBinding
       -> jboss.jca:name=JmsXA,service=TxCM{Start:Configured}
       -> jboss.jca:name=JmsXA,service=TxCM{Create:Configured}
      
      jboss.jca:name=JmsXA,service=ManagedConnectionFactory
       -> jboss.messaging:service=ServerPeer{Create:Configured}
       -> jboss.messaging:service=ServerPeer{Start:Configured}
      
      jboss.jca:name=JmsXA,service=ManagedConnectionPool
       -> jboss.jca:name=JmsXA,service=ManagedConnectionFactory{Start:Configured}
       -> jboss.jca:name=JmsXA,service=ManagedConnectionFactory{Create:Configured}
      
      jboss.jca:name=JmsXA,service=TxCM
       -> jboss.jca:name=JmsXA,service=ManagedConnectionPool{Create:Configured}
       -> jboss.jca:name=JmsXA,service=ManagedConnectionPool{Start:Configured}
      
      jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
       -> jboss.messaging:service=ServerPeer{Start:Configured}
       -> jboss.messaging:service=PostOffice{Create:** NOT FOUND **}
       -> jboss.messaging:service=PostOffice{Start:** NOT FOUND **}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
      
      jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
       -> jboss.messaging:service=ServerPeer{Start:Configured}
       -> jboss.messaging:service=PostOffice{Create:** NOT FOUND **}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
       -> jboss.messaging:service=PostOffice{Start:** NOT FOUND **}
      
      jboss.messaging.connectionfactory:service=ConnectionFactory
       -> jboss.messaging:service=PostOffice{Create:** NOT FOUND **}
       -> jboss.messaging:service=PostOffice{Start:** NOT FOUND **}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
       -> jboss.messaging:service=ServerPeer{Start:Configured}
      
      jboss.messaging.destination:name=DLQ,service=Queue
       -> jboss.messaging:service=ServerPeer{Start:Configured}
       -> jboss.messaging:service=PostOffice{Create:** NOT FOUND **}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
       -> jboss.messaging:service=PostOffice{Start:** NOT FOUND **}
      
      jboss.messaging.destination:name=ExpiryQueue,service=Queue
       -> jboss.messaging:service=ServerPeer{Start:Configured}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
       -> jboss.messaging:service=PostOffice{Create:** NOT FOUND **}
       -> jboss.messaging:service=PostOffice{Start:** NOT FOUND **}
      
      jboss.messaging:service=ServerPeer
       -> jboss.messaging:service=JMSUserManager{Start:** NOT FOUND **}
       -> jboss.messaging:service=JMSUserManager{Create:** NOT FOUND **}
       -> jboss.messaging:service=PersistenceManager{Start:** NOT FOUND **}
       -> jboss.messaging:service=PersistenceManager{Create:** NOT FOUND **}
      
      jboss.mq:service=DestinationManager
       -> jboss.messaging:service=ServerPeer{Start:Configured}
       -> jboss.messaging:service=ServerPeer{Create:Configured}
      
      jboss:service=KeyGeneratorFactory,type=HiLo
       -> jboss.jca:name=DefaultDS,service=DataSourceBinding{Start:** NOT FOUND **}
       -> jboss.jca:name=DefaultDS,service=DataSourceBinding{Create:** NOT FOUND **}
      
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      jboss.jdbc:datasource=DefaultDS,service=metadata -> ** NOT FOUND **
      
      jboss.messaging:service=JMSUserManager -> ** NOT FOUND **
      
      jboss.jca:name=DefaultDS,service=DataSourceBinding -> ** NOT FOUND **
      
      jboss.messaging:service=PostOffice -> ** NOT FOUND **
      
      <UNKNOWN> -> ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **
      
      jboss.messaging:service=PersistenceManager -> ** NOT FOUND **


        • 1. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
          jaikiran pai Master

          Which version of JBoss do you use? Also did you change anything in the JBoss that you downloaded? Especially the -ds.xml file configuring the DefaultDS.

          • 2. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
            Nanda Kishore Newbie

            I am useing Jboss 5.0.0 beta4. i changed in mysql-ds.xml.

            • 3. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
              jaikiran pai Master

              Looks like you made some incorrect changes to the -ds.xml file which is resulting in this. Can you post the contents of this file?

              P.S: JBoss-5 CR2 is the latest JBoss-5 version that's available. Beta4 has now become old :-) So you probably would want to use the CR2


              While posting the logs or code or xml content, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted

              • 4. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                Nanda Kishore Newbie

                 

                <?xml version="1.0" encoding="UTF-8"?>
                
                <!-- $Id: mysql-ds.xml 41017 2006-02-07 14:26:14Z acoliver $ -->
                <!-- Datasource config for MySQL using 3.0.9 available from:
                http://www.mysql.com/downloads/api-jdbc-stable.html
                -->
                
                <datasources>
                 <local-tx-datasource>
                 <jndi-name>iBlue</jndi-name>
                 <connection-url>jdbc:mysql://localhost:3306/iBlue</connection-url>
                 <driver-class>com.mysql.jdbc.Driver</driver-class>
                 <user-name>root</user-name>
                 <password>I@sitBc!</password>
                 <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
                 <!-- should only be used on drivers after 3.22.1 with "ping" support
                 <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
                 -->
                 <!-- sql to call when connection is created
                 <new-connection-sql>some arbitrary sql</new-connection-sql>
                 -->
                 <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
                 <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                 -->
                
                 <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
                 <metadata>
                 <type-mapping>mySQL</type-mapping>
                 </metadata>
                 </local-tx-datasource>
                </datasources>


                • 5. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                  Nanda Kishore Newbie

                  Do in need to change any thing in ejb3-timer-service.xml. I am not using any messaging services.

                  • 6. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                    jaikiran pai Master

                    Your -ds.xml looks fine. I reason i asked you to post that was, i thought you had used the DefaultDS as the datasource name.

                    jboss.jdbc:datasource=DefaultDS,service=metadata -> ** NOT FOUND **


                    This datasource is configured through the hssql-ds.xml file present in %JBOSS_HOME%/server/< serverName>/deploy folder. Did you remove that file or change it?

                    Also please post your entire console logs from the point you start the server till you see this exceptions.




                    • 7. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                      Nanda Kishore Newbie

                       

                       JBoss Bootstrap Environment
                      
                       JBOSS_HOME: /var/jboss-5.0.0.Beta4
                      
                       JAVA: /usr/java/jdk1.5.0_16/bin/java
                      
                       JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx200m -XX:MaxPermSize=256m
                      -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
                      
                       CLASSPATH: /var/jboss-5.0.0.Beta4/bin/run.jar:/usr/java/jdk1.5.0_16/lib/tools.jar
                      
                      =========================================================================
                      
                      05:46:20,615 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                      05:46:20,616 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)
                      05:46:20,617 INFO [ServerImpl] Home Dir: /var/jboss-5.0.0.Beta4
                      05:46:20,618 INFO [ServerImpl] Home URL: file:/var/jboss-5.0.0.Beta4/
                      05:46:20,618 INFO [ServerImpl] Library URL: file:/var/jboss-5.0.0.Beta4/lib/
                      05:46:20,618 INFO [ServerImpl] Patch URL: null
                      05:46:20,619 INFO [ServerImpl] Server Name: default
                      05:46:20,619 INFO [ServerImpl] Server Home Dir: /var/jboss-5.0.0.Beta4/server/default
                      05:46:20,619 INFO [ServerImpl] Server Home URL: file:/var/jboss-5.0.0.Beta4/server/default/
                      05:46:20,619 INFO [ServerImpl] Server Data Dir: /var/jboss-5.0.0.Beta4/server/default/data
                      05:46:20,619 INFO [ServerImpl] Server Temp Dir: /var/jboss-5.0.0.Beta4/server/default/tmp
                      05:46:20,619 INFO [ServerImpl] Server Config URL: file:/var/jboss-5.0.0.Beta4/server/default/conf/
                      05:46:20,620 INFO [ServerImpl] Server Library URL: file:/var/jboss-5.0.0.Beta4/server/default/lib/
                      05:46:20,620 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
                      05:46:21,292 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/var/jboss-5.0.0.Beta4/server/default/conf/bootstrap-beans.xml
                      05:46:22,688 INFO [ProfileImpl] Using profile root:/var/jboss-5.0.0.Beta4/server/default
                      05:46:23,722 INFO [ServerInfo] Java version: 1.5.0_16,Sun Microsystems Inc.
                      05:46:23,723 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_16-b02,Sun Microsystems Inc.
                      05:46:23,723 INFO [ServerInfo] OS-System: Linux 2.6.18-92.1.1.el5.028stab057.2ent,i386
                      05:46:23,812 INFO [JMXKernel] Legacy JMX core initialized
                      05:46:33,616 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
                      05:46:35,658 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                      05:46:35,658 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
                      05:46:36,933 INFO [TransactionManagerService] Starting recovery manager
                      05:46:37,492 INFO [TransactionManagerService] Recovery manager started
                      05:46:37,492 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
                      05:47:02,356 INFO [PersistenceUnitParsingDeployer] Found persistence units [org.jboss.ejb3.metadata.jpa.spec.PersistenceUnitMetaData@1710374{name=iBlue-ejbPU}]
                      05:47:02,959 WARN [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
                      05:47:05,520 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@25a311 for BaseClassLoader@18e95d9{vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/ejb3-interceptors-aop.xml}
                      05:47:06,327 WARN [ReferenceMetaDataResolverDeployer] Unresolved references exist in JBossWebMetaData: [TemperatureFacadeLocal/ejb-local-ref/TemperatureFacade available: []]
                      05:47:08,635 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.5.0_16/jre/lib/i386/server:/usr/java/jdk1.5.0_16/jre/lib/i386:/usr/java/jdk1.5.0_16/jre/../lib/i386
                      05:47:08,920 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                      05:47:08,921 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                      05:47:08,921 INFO [Catalina] Initialization processed in 1019 ms
                      05:47:08,921 INFO [StandardService] Starting service jboss.web
                      05:47:08,925 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.0.CR12
                      05:47:09,138 INFO [Catalina] Server startup in 216 ms
                      05:47:09,389 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                      05:47:10,342 INFO [NativeServerConfig] JBoss Web Services - Native
                      05:47:10,342 INFO [NativeServerConfig] jbossws-native-2.0.3.GA (build=200801241020)
                      05:47:12,941 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-context.war
                      05:47:14,299 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
                      05:47:14,620 INFO [RARDeployment] Required license terms exist, view vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/mail-ra.rar/META-INF/ra.xml
                      05:47:14,956 INFO [RARDeployment] Required license terms exist, view vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/jms-ra.rar/META-INF/ra.xml
                      05:47:14,965 INFO [RARDeployment] Required license terms exist, view vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
                      05:47:15,175 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                      05:47:15,205 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                      05:47:15,213 INFO [RAMJobStore] RAMJobStore initialized.
                      05:47:15,213 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                      05:47:15,213 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                      05:47:15,214 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                      05:47:15,480 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
                      05:47:16,785 INFO [MailService] Mail Service bound to java:/Mail
                      05:47:16,871 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
                      05:47:17,108 INFO [RARDeployment] Required license terms exist, view vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                      05:47:17,239 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=iBlue' to JNDI name 'java:iBlue'
                      05:47:17,289 INFO [RARDeployment] Required license terms exist, view vfsfile:/var/jboss-5.0.0.Beta4/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                      05:47:18,403 INFO [MCKernelAbstraction] installing bean: persistence.units:ear=iBlue.ear,jar=iBlue-ejb.jar,unitName=iBlue-ejbPU with dependencies:
                      05:47:18,403 INFO [MCKernelAbstraction] and demands:
                      05:47:18,404 INFO [MCKernelAbstraction] jboss.jca:name=iBlue,service=DataSourceBinding
                      05:47:18,404 INFO [MCKernelAbstraction] and supplies:
                      05:47:18,553 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=iBlue.ear,jar=iBlue-ejb.jar,unitName=iBlue-ejbPU
                      05:47:18,600 INFO [Version] Hibernate Annotations 3.3.1.Beta1
                      05:47:18,618 INFO [Environment] Hibernate 3.2.4.sp1
                      05:47:18,625 INFO [Environment] hibernate.properties not found
                      05:47:18,627 INFO [Environment] Bytecode provider name : javassist
                      05:47:18,637 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
                      05:47:18,741 INFO [Version] Hibernate EntityManager 3.3.2.Beta3
                      05:47:18,837 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
                      05:47:19,003 INFO [AnnotationBinder] Binding entity from annotated class: com.TemperatureEntityBeans.Temperature
                      05:47:19,030 INFO [QueryBinder] Binding Named query: Temperature.findByLoggerid => SELECT t FROM Temperature t WHERE t.loggerid = :loggerid
                      05:47:19,031 INFO [QueryBinder] Binding Named query: Temperature.findByDate => SELECT t FROM Temperature t WHERE t.date = :date
                      05:47:19,031 INFO [QueryBinder] Binding Named query: Temperature.findByTime => SELECT t FROM Temperature t WHERE t.time = :time
                      05:47:19,086 INFO [EntityBinder] Bind entity com.TemperatureEntityBeans.Temperature on table temperature
                      05:47:19,169 INFO [Version] Hibernate Validator 3.0.0.GA
                      05:47:19,366 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
                      05:47:19,371 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
                      05:47:20,253 INFO [SettingsFactory] RDBMS: MySQL, version: 5.0.45
                      05:47:20,254 INFO [SettingsFactory] JDBC driver: MySQL-AB JDBC Driver, version: mysql-connector-java-5.1.5 ( Revision: ${svn.Revision} )
                      05:47:20,283 INFO [Dialect] Using dialect: org.hibernate.dialect.MySQL5InnoDBDialect
                      05:47:20,288 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
                      05:47:20,291 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
                      05:47:20,298 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup
                      05:47:20,298 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled
                      05:47:20,298 INFO [SettingsFactory] Automatic session close at end of transaction: disabled
                      05:47:20,298 INFO [SettingsFactory] JDBC batch size: 15
                      05:47:20,298 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
                      05:47:20,299 INFO [SettingsFactory] Scrollable result sets: enabled
                      05:47:20,299 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): enabled
                      05:47:20,299 INFO [SettingsFactory] Connection release mode: auto
                      05:47:20,300 INFO [SettingsFactory] Maximum outer join fetch depth: 2
                      05:47:20,300 INFO [SettingsFactory] Default batch fetch size: 1
                      05:47:20,300 INFO [SettingsFactory] Generate SQL with comments: disabled
                      05:47:20,300 INFO [SettingsFactory] Order SQL updates by primary key: disabled
                      05:47:20,301 INFO [SettingsFactory] Order SQL inserts for batching: disabled
                      05:47:20,301 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
                      05:47:20,304 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
                      05:47:20,304 INFO [SettingsFactory] Query language substitutions: {}
                      05:47:20,304 INFO [SettingsFactory] JPA-QL strict compliance: enabled
                      05:47:20,304 INFO [SettingsFactory] Second-level cache: enabled
                      05:47:20,304 INFO [SettingsFactory] Query cache: disabled
                      05:47:20,304 INFO [SettingsFactory] Cache provider: org.hibernate.cache.HashtableCacheProvider
                      05:47:20,306 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
                      05:47:20,306 INFO [SettingsFactory] Cache region prefix: iBlue_ear,iBlue-ejb_jar,iBlue-ejbPU
                      05:47:20,306 INFO [SettingsFactory] Structured second-level cache entries: disabled
                      05:47:20,312 INFO [SettingsFactory] Echoing all SQL to stdout
                      05:47:20,312 INFO [SettingsFactory] Statistics: disabled
                      05:47:20,312 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled
                      05:47:20,318 INFO [SettingsFactory] Default entity-mode: pojo
                      05:47:20,318 INFO [SettingsFactory] Named query checking : enabled
                      05:47:20,362 INFO [SessionFactoryImpl] building session factory
                      05:47:20,679 INFO [SessionFactoryObjectFactory] Factory name: persistence.units:ear=iBlue.ear,jar=iBlue-ejb.jar,unitName=iBlue-ejbPU
                      05:47:20,681 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
                      05:47:20,687 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.units:ear=iBlue.ear,jar=iBlue-ejb.jar,unitName=iBlue-ejbPU
                      05:47:20,687 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
                      05:47:20,716 INFO [SchemaUpdate] Running hbm2ddl schema update
                      05:47:20,716 INFO [SchemaUpdate] fetching database metadata
                      05:47:20,722 INFO [SchemaUpdate] updating schema
                      05:47:20,810 INFO [TableMetadata] table found: iBlue.temperature
                      05:47:20,810 INFO [TableMetadata] columns: [temp_logger, text, loggerid, time, date]
                      05:47:20,810 INFO [TableMetadata] foreign keys: []
                      05:47:20,810 INFO [TableMetadata] indexes: []
                      05:47:20,811 INFO [SchemaUpdate] schema update complete
                      05:47:20,813 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
                      05:47:21,197 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=iBlue.ear,jar=iBlue-ejb.jar,name=TemperatureFacade,service=EJB3 with dependencies:
                      05:47:21,197 INFO [MCKernelAbstraction] and demands:
                      05:47:21,197 INFO [MCKernelAbstraction] persistence.units:ear=iBlue.ear,jar=iBlue-ejb.jar,unitName=iBlue-ejbPU
                      05:47:21,197 INFO [MCKernelAbstraction] jboss.ejb:service=EJBTimerService
                      05:47:21,197 INFO [MCKernelAbstraction] and supplies:
                      05:47:21,197 INFO [MCKernelAbstraction] Class:com.TemperatureSessionBeans.TemperatureFacadeLocal
                      05:47:21,291 INFO [TomcatDeployment] deploy, ctxPath=/iBlue-war, vfsUrl=iBlue.ear/iBlue-war.war
                      05:47:21,541 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                      05:47:21,724 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
                      
                      *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
                      
                      jboss.j2ee:ear=iBlue.ear,jar=iBlue-ejb.jar,name=TemperatureFacade,service=EJB3
                       -> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **}
                      
                      
                      *** CONTEXTS IN ERROR: Name -> Error
                      
                      <UNKNOWN> -> ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **
                      
                      
                      05:47:21,834 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                      05:47:21,955 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                      05:47:21,964 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)] Started in 1m:1s:342ms


                      • 8. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                        Nanda Kishore Newbie

                        i removed all %JBOSS_HOME%/server/< serverName>/deploy folder/messaging files and i removed hssql-ds.xml . now i left with this error UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **.
                        do i need to configure %JBOSS_HOME%/server/< serverName>/deploy/ejb3-timer-service.xml for mysql database.

                        • 9. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                          jaikiran pai Master

                           

                          "nanda_kishore" wrote:
                          i removed all %JBOSS_HOME%/server/< serverName>/deploy folder/messaging files and i removed hssql-ds.xml .


                          Any specific reason for doing this? The DefaultDS is used at multiple places in JBoss (as you see in the exceptions) and removing it will result in problems at multiple places. If you are trying to slim down your server, then have a look at http://www.jboss.org/community/docs/DOC-10217

                          • 10. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                            Nanda Kishore Newbie

                            to overcome this error i removed files. can u please give me solution for this problem.

                            • 11. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                              jaikiran pai Master

                               

                              "nanda_kishore" wrote:
                              to overcome this error i removed files. can u please give me solution for this problem.


                              I was (and am still) confused by your first post, in which the failures were because of missing DefaultDS and your post saying:

                              "nanda_kishore" wrote:

                              i removed all %JBOSS_HOME%/server/< serverName>/deploy folder/messaging files and i removed hssql-ds.xml . now i left with this error UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **.


                              Based on your console logs, it looks like the only problem you are having is this:

                              05:47:21,724 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deploymen
                              ts (SEE PREVIOUS ERRORS FOR DETAILS):

                              *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

                              jboss.j2ee:ear=iBlue.ear,jar=iBlue-ejb.jar,name=TemperatureFacade,service=EJB3
                              -> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **}


                              *** CONTEXTS IN ERROR: Name -> Error

                              <UNKNOWN> -> ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService **


                              To summarize, on a clean JBoss if you place your EJB3 application in the deploy folder and start the server you see this exception. Is my understanding correct? If yes, then i think this was a bug which was fixed in the EJBTHREE project. If you use JBoss-5 CR2, the fix is available. The workaround for this issue was to remove the application from the deploy folder, start the server, wait for it to completely start without any errors and then place the application in the deploy folder to be hot deployed.


                              • 13. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                                Nanda Kishore Newbie

                                I am not getting any errors in my tool using jboss 5.0.0 beta4. but when i am trying to deploy in server i am getting error.

                                • 14. Re:  UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService *
                                  jaikiran pai Master

                                   

                                  "nanda_kishore" wrote:
                                  is there no way to solve this problem.


                                  Did you try this (on a clean JBoss):

                                  "jaikiran" wrote:

                                  The workaround for this issue was to remove the application from the deploy folder, start the server, wait for it to completely start without any errors and then place the application in the deploy folder to be hot deployed.


                                  1 2 Previous Next