0 Replies Latest reply on Dec 23, 2009 10:06 AM by YE

    Caused by: java.lang.IllegalStateException: Locked entries

    YE
      Hi,

      I post the following thread to Jdev forum. But someone recommended that I should create thread here since it is a weblogic problem.

      My colleagues create an ADF application which is migrated from Jde 11.1.1.1. After migeration, they use Jdev11.1.1.2 to modify this application.
      Developers deploy the ADF application to Weblogic (10.3.2) domain.
      Then, testers start to test this application.
      Every tester has a username. Every username is unique.
      In a page, there is a button. After the button is clicked by testers, an exception appears and the page goes to the error page.
      They have to back to the original page from web browser.

      Developers test this application in the default Weblogic installed with Jdeveloper. The above exception does not appear.


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

      Caused by: java.lang.IllegalStateException: Locked entries
      [Thread[

      at fuego.pool.TimedMultiValuatedCache.clear(TimedMultiValuatedCache.java:384)
      at fuego.connector.impl.pool.PoolManager.stop(PoolManager.java:71)
      at fuego.connector.impl.BaseJDBCConnector.stop(BaseJDBCConnector.java:296)
      at fuego.connector.ConnectorService.stopService(ConnectorService.java:778)
      at fuego.connector.ConnectorService.stop(ConnectorService.java:486)
      at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:54)
      at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:395)
      at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:331)
      at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:313)
      at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:216)
      at fuego.directory.Directory.fillPassport(Directory.java:123)
      at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:275)



      --------------------------------------------------------------------------------
      ####<2009-12-22 CST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <WINDOWS-D6GMTZ2> <AdminServer>
      <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1261469009637> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>

      --------------------------------------------------------------------------------
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

      Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The Network Adapter could not establish the connection
      at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:256)

      ####<2009-12-22 CST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <WINDOWS-D6GMTZ2> <AdminServer> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1261473870326> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>

      Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The Network Adapter could not establish the connection

      ###<2009-12-22 下午05时24分25秒 CST> <Error> <Deployer> <WINDOWS-D6GMTZ2> <AdminServer> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1261473865443> <BEA-149205> <Failed to initialize the application 'ysjk109' due to error weblogic.application.ModuleException: .