9 Replies Latest reply: Jun 13, 2012 5:59 AM by Martijnke RSS

    error starting apex listener after java changes

    Martijnke
      Hi,


      I have java 1.6.29 JRE, because I needed a JDK (for jasperreports) I installed JDK 1.7.04
      this gave problems with oracle forms so I uninstalled 1.7.4
      so now only JRE 1.6.29 is on our system

      starting apex gives following error :
      HTTP Status 500
      oracle.dbtools.rt.service.ServiceLocatorException: Exception occurred in activate() method
      have already redeployed, no change
      we use oracle glassfish server 3.1.2


      Kr
      Martin
        • 1. Re: error starting apex listener after java changes
          Prabodh
          Hi,
          Few things to check.

          a.Do you see the correct java version when you run "java -version" from OS prompt?
          b.Is your JAVA_HOME pointing to the JRE6 folder?
          c. Your PATH env var has no reference to JRE 1.7.x but has JRE6 ?

          Regards,
          • 2. Re: error starting apex listener after java changes
            Udo
            Hi,
            so now only JRE 1.6.29 is on our system
            You definetly need a JDK, JRE is not sufficient.
            You could download the most recent 1.6 JDK to stay compatible with Forms. Additionally, you could even use the current 1.7 JDK and configure Forms to use the 1.6 family JRE.

            -Udo
            • 3. Re: error starting apex listener after java changes
              Martijnke
              @Prabodh : already checked all that
              java version is 1.6.0_29


              @Udo : apex has been running for weeks with no JDK installed, will install 1.6.29 JDK anyway since jasper needs it

              so am still left with original error
              (no luck searching MOS either)




              Kr
              Martin
              • 4. Re: error starting apex listener after java changes
                Udo
                @Udo : apex has been running for weeks with no JDK installed, will install 1.6.29 JDK anyway since jasper needs it
                I'm not sure about that. Even GlassFish itself requires a JDK, as documented in the [url http://docs.oracle.com/cd/E26576_01/doc.312/e24939/release-notes.htm#gfgps]Release Notes (and everywhere else).

                Anyway, you only provided the head of the stack trace. The error message you see there could as well be related to the fact that your APEX Listener is not configured yet. This often happens when no permanent location for the configuration file is setup (keywork config.dir ), but the default (temporary) location is used. After a restart, the temp will be erased and the configuration is lost.
                Try to (re)run listenerConfigure and see what happens. If APEX Listener allows you to configure it that way, it means it can't find any other configuration file, so you should proceed. Save the apex-config.xml created in that step to a permanent location and configure APEX Listener to use a config.dir (by editing the web.xml as documented in the Installation and Developement Guide).

                -Udo

                Edited by: Udo on 07.06.2012 11:46
                • 5. Re: error starting apex listener after java changes
                  Martijnke
                  /ListenerConfigure also gives the same 500 error

                  have reinstalled java 1.7.0 JDK, still the same

                  glassfish itself no longer seems to be working :
                  HTTP Status 404 -
                  
                  type Status report
                  
                  message
                  
                  description
                  
                  The requested resource () is not available.
                  Oracle GlassFish Server 3.1.2
                  even worse : uninstalling glassfish doesn't work either, the installer just hangs during unconfiguring domain

                  if I try a reinstall it syas there is already a admin console running on port 4848 (how can I stop this ?)


                  Kr
                  Martin
                  • 6. Re: error starting apex listener after java changes
                    Udo
                    Hi Martin,
                    /ListenerConfigure also gives the same 500 erro
                    please provide the log output for APEX Listener, including the complete stack trace for that 500 error. Otherwhise it's really hard to tell what's going wrong in your instance.
                    even worse : uninstalling glassfish doesn't work either, the installer just hangs during unconfiguring domain
                    Sounds like your system is messed up "in general", not just concerning APEX Listener.
                    if I try a reinstall it syas there is already a admin console running on port 4848 (how can I stop this ?)
                    This would be a question to be asked in some GlassFish-related forum.

                    -Udo
                    • 7. Re: error starting apex listener after java changes
                      Martijnke
                      Hi Udo,

                      was able to uninstall
                      reinstalled glassfish and apex listener

                      still the same error
                      so here is the logfile :
                      [#|2012-06-12T22:30:01.593+0200|WARNING|oracle-glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=29;_ThreadName=Thread-2;|StandardWrapperValve[HttpEndPoint]: PWC1406: Servlet.service() for servlet HttpEndPoint threw exception
                      oracle.dbtools.rt.service.ServiceLocatorException: Exception occurred in activate() method
                           at oracle.dbtools.rt.service.Provider.activate(Provider.java:56)
                           at oracle.dbtools.rt.service.Provider.match(Provider.java:111)
                           at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
                           at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
                           at oracle.dbtools.rt.service.ServiceLocator.acquire(ServiceLocator.java:74)
                           at oracle.dbtools.rt.service.Provider.inject(Provider.java:137)
                           at oracle.dbtools.rt.service.Provider.activate(Provider.java:39)
                           at oracle.dbtools.rt.service.Provider.match(Provider.java:111)
                           at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
                           at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
                           at oracle.dbtools.rt.service.ServiceLocator.acquire(ServiceLocator.java:74)
                           at oracle.dbtools.rt.service.Provider.inject(Provider.java:137)
                           at oracle.dbtools.rt.service.Provider.activate(Provider.java:39)
                           at oracle.dbtools.rt.service.Provider.match(Provider.java:111)
                           at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
                           at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
                           at oracle.dbtools.rt.service.ServiceLocator.acquire(ServiceLocator.java:74)
                           at oracle.dbtools.rt.service.Provider.inject(Provider.java:137)
                           at oracle.dbtools.rt.service.Provider.activate(Provider.java:39)
                           at oracle.dbtools.rt.service.Provider.match(Provider.java:111)
                           at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
                           at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
                           at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:104)
                           at oracle.dbtools.rt.web.RequestDispatchers.choose(RequestDispatchers.java:85)
                           at oracle.dbtools.rt.web.RequestDispatchers.dispatch(RequestDispatchers.java:52)
                           at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:85)
                           at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
                           at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
                           at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
                           at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
                           at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
                           at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
                           at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
                           at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
                           at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
                           at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
                           at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                           at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                           at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                           at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                           at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                           at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                           at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                           at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                           at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                           at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                           at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                           at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                           at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                           at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                           at java.lang.Thread.run(Thread.java:662)
                      Caused by: oracle.dbtools.rt.web.WebException: Universal Connection Pool kan niet worden gestart.: oracle.ucp.UniversalConnectionPoolException: De verbinding kan niet worden opgehaald uit de gegevensbron.
                           at oracle.dbtools.rt.web.WebException.internalError(WebException.java:124)
                           at oracle.dbtools.rt.query.jdbc.BaseJDBCCallProvider.activated(BaseJDBCCallProvider.java:56)
                           at oracle.dbtools.rt.query.jdbc.ora.OraJDBCCallProvider.activate(OraJDBCCallProvider.java:25)
                           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                           at java.lang.reflect.Method.invoke(Method.java:597)
                           at oracle.dbtools.rt.service.__Reflections.invoke(__Reflections.java:85)
                           at oracle.dbtools.rt.service.Provider.activate(Provider.java:43)
                           ... 50 more
                      Caused by: java.sql.SQLException: Universal Connection Pool kan niet worden gestart.: oracle.ucp.UniversalConnectionPoolException: De verbinding kan niet worden opgehaald uit de gegevensbron.
                           at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:588)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:277)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:647)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:614)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:608)
                           at oracle.dbtools.apex.Connections.getConnection(Connections.java:116)
                           at oracle.dbtools.rt.query.jdbc.ora.OraJDBCCallProvider.connection(OraJDBCCallProvider.java:31)
                           at oracle.dbtools.rt.query.jdbc.BaseJDBCCallProvider.activated(BaseJDBCCallProvider.java:44)
                           ... 57 more
                      Caused by: oracle.ucp.UniversalConnectionPoolException: De verbinding kan niet worden opgehaald uit de gegevensbron.
                           at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:421)
                           at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:389)
                           at oracle.ucp.jdbc.DataSourceConnectionFactoryAdapter.createConnection(DataSourceConnectionFactoryAdapter.java:106)
                           at oracle.ucp.common.UniversalConnectionPoolImpl$UniversalConnectionPoolInternal.createOnePooledConnectionInternal(UniversalConnectionPoolImpl.java:1613)
                           at oracle.ucp.common.UniversalConnectionPoolImpl$UniversalConnectionPoolInternal.access$600(UniversalConnectionPoolImpl.java:1421)
                           at oracle.ucp.common.UniversalConnectionPoolImpl.createOnePooledConnection(UniversalConnectionPoolImpl.java:488)
                           at oracle.ucp.common.UniversalConnectionPoolImpl.addNewConnections(UniversalConnectionPoolImpl.java:988)
                           at oracle.ucp.common.UniversalConnectionPoolBase.getInitialConnections(UniversalConnectionPoolBase.java:541)
                           at oracle.ucp.common.UniversalConnectionPoolBase.start(UniversalConnectionPoolBase.java:655)
                           at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:271)
                           ... 63 more
                      Caused by: java.sql.SQLException: Listener refused the connection with the following error:
                      ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
                       
                           at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:419)
                           at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
                           at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
                           at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
                           at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
                           at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:280)
                           at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:207)
                           at oracle.ucp.jdbc.DataSourceConnectionFactoryAdapter.createConnection(DataSourceConnectionFactoryAdapter.java:100)
                           ... 70 more
                      Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:
                      ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
                       
                           at oracle.net.ns.NSProtocol.connect(NSProtocol.java:386)
                           at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1054)
                           at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:308)
                           ... 77 more
                      |#]
                      hope this helps

                      Kr
                      Martin
                      • 8. Re: error starting apex listener after java changes
                        Udo
                        Hi Martin,

                        it does help. The stack has a root cause:
                        ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
                        This has nothing to do with your Java update nor APEX Listener itself, though I'd like to see future APEX versions to give end users a more comprehensive error message. It seems you are connecting with wrong database parameters. Try to delete your apex-config.xml and rerun +/listenerConfigure/+ with proper access parameters. Also make sure your Database Listener is configured correctly.

                        -Udo
                        • 9. Re: error starting apex listener after java changes
                          Martijnke
                          Hi Udo,

                          thx for your time
                          there was something wrong with the system which had nothing to do with oracle or java but caused the database to stop
                          oradim gave me the clue, it was unable to start the database stating : 'windows application event log is full'

                          after fixing that everything is working fine now


                          Kr
                          Martin