0 Replies Latest reply on Jun 5, 2014 4:18 AM by Madhavi G

    Getting naming context read only exception when deployed jbpm 3.3 in jboss 7.1.1.final

    Madhavi G Newbie

      I am getting the following exception in the log due to which the jobs are never get executed. It works fine in Jboss 4.2.  We recently migrated to Jboss 7 and all naming contexts are by default readonly in Jboss 7.

       

      -----------------------------

      Named query checking : enabled

      15:56:35,874 INFO  [org.hibernate.impl.SessionFactoryImpl] (JbpmJobExecutor:172.20.187.105:5) building session factory

      15:56:35,874 WARN  [net.sf.ehcache.CacheManager] (JbpmJobExecutor:172.20.187.105:5) Creating a new instance of CacheManager using the diskStorePath "C:\Users\663401\AppData\Local\Temp\" which is already used by an existing CacheManager.

      The source of the configuration was classpath.

      The diskStore path for this CacheManager will be set to C:\Users\663401\AppData\Local\Temp\\ehcache_auto_created_1392114395874.

      To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance.

      15:56:36,192 INFO  [org.hibernate.impl.SessionFactoryObjectFactory] (JbpmJobExecutor:172.20.187.105:5) Factory name: java:/hibernate/SessionFactory

      15:56:36,192 INFO  [org.hibernate.util.NamingHelper] (JbpmJobExecutor:172.20.187.105:5) JNDI InitialContext properties:{}

      15:56:36,192 INFO  [org.hibernate.util.NamingHelper] (JbpmJobExecutor:172.20.187.105:5) Creating subcontext: hibernate

      15:56:36,192 ERROR [org.jbpm.job.executor.JobExecutorThread] (JbpmJobExecutor:172.20.187.105:5) exception in job executor thread. waiting 60000 milliseconds: java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only

        at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)

        at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:116)

        at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:338)

        at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:346)

        at org.hibernate.util.NamingHelper.bind(NamingHelper.java:69) [hibernate-3.2.6.ga.jar:3.2.6.ga]

        at org.hibernate.impl.SessionFactoryObjectFactory.addInstance(SessionFactoryObjectFactory.java:90) [hibernate-3.2.6.ga.jar:3.2.6.ga]

        at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:306) [hibernate-3.2.6.ga.jar:3.2.6.ga]

        at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) [hibernate-3.2.6.ga.jar:3.2.6.ga]

        at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:105) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:95) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:99) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:373) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:630) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:106) [MasterCraftSGM-core-1.1.jar:]

        at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:54) [MasterCraftSGM-core-1.1.jar:]

       

       

      15:56:36,195 INFO  [org.hibernate.util.NamingHelper] (JbpmJobExecutor:172.20.187.105:4) JNDI InitialContext properties:{}

      15:56:36,195 INFO  [org.hibernate.connection.DatasourceConnectionProvider] (JbpmJobExecutor:172.20.187.105:4) Using datasource: java:jboss/datasources/MasterCraftSGM

      15:56:36,195 INFO  [org.hibernate.cfg.SettingsFactory] (JbpmJobExecutor:172.20.187.105:4) RDBMS: PostgreSQL, version: 9.0.3

      --------------------------

       

      Googled a lot to find solution for this, but no luck. Please help me in solving this issue.@@