3 Replies Latest reply: Jun 4, 2013 10:46 AM by Michael OBrien RSS

    Full log file / server log / full stack trace

    sangara
      Hi,

      I have built a simple ADF application and trying "hard" :) to deploy on JCS. For some reason, the deployment fails, and the log messages are not much helpful. Even the deployment log is not giving much info on the root cause. Is there a way to get hold of the log files where entire stack-trace is logged to ? Interestingly it runs fine from local JDeveloper.

      Log Messages:
           Warning     1     User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null.
           Error     1     Failure occurred in the execution of deployment request with ID '1365672054249' for task '9'. Error is: 'weblogic.application.ModuleException: '


      Deployment Log:

      2013-04-11 04:20:53 CDT: Starting action "Deploy Application"
      2013-04-11 04:20:53 CDT: Deploy Application started
      2013-04-11 04:21:12 CDT: weblogic.application.ModuleException:
      2013-04-11 04:21:12 CDT: WL action state: failed
      2013-04-11 04:21:12 CDT: Action FAILED with WL action state: failed
      2013-04-11 04:21:12 CDT: Check the server log of your Java cloud service for more info about the failure.
      2013-04-11 04:21:12 CDT: Application deployment failed.
      2013-04-11 04:21:13 CDT: [Deployer:149194]Operation 'remove' on application 'Emp' has succeeded on 'm0'
      2013-04-11 04:21:13 CDT: WL action state: completed
      2013-04-11 04:21:13 CDT: "Deploy Application" complete: status FAILED


      JDeveloper version: 11.1.1.6

      Any help is greatly appreciated...

      Thanks
      Srini
        • 1. Re: Full log file / server log / full stack trace
          Jose Aróstegui
          Hi,

          In the Monitoring Console, you have the "Java Cloud Service Jobs" region, you can select a job and view the log using "Application Whitelist Validation".

          Hope it helps,
          Jose.
          • 2. Re: Full log file / server log / full stack trace
            Michael OBrien
            Jose,
            Hi, those logs are only minimal - for instance I get the following if I try to use @EJB injection on an @ManagedBean

            2013-06-03 22:11:35 CDT: Starting action "Redeploy Application"
            2013-06-03 22:11:35 CDT: Redeploy Application started
            2013-06-03 22:11:36 CDT: weblogic.application.ModuleException: Could not setup environment
            2013-06-03 22:11:36 CDT: WL action state: failed
            2013-06-03 22:11:36 CDT: Action FAILED with WL action state: failed
            2013-06-03 22:11:36 CDT: Check the server log of your Java cloud service for more info about the failure.
            2013-06-03 22:11:36 CDT: Application redeployment failed.
            2013-06-03 22:11:36 CDT: "Redeploy Application" complete: status FAILED


            - it would be nice if we could see the full logs - the example below is for mis-configured @Schedule method on an @Singleton automatic TimerService bean - like the ones that would be in

            D:\opt\wls12110\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log

            that show java exceptions
            javax.ejb.EJBException: EJB Exception: : com.oracle.pitchfork.interfaces.LifecycleCallbackException: Failure to invoke timeout method public void org.obrienlabs.opendatalink.business.CaptureTimerService.process() on bean class class org.obrienlabs.opendatalink.business.CaptureTimerService_jtldc0_Impl with args: []]
                 at com.oracle.pitchfork.inject.Jsr250Metadata.invokeTimeoutMethodInternal(Jsr250Metadata.java:380)

            thank you
            /michael
            • 3. Re: Full log file / server log / full stack trace
              Michael OBrien
              Found some of the system logs

              See post by Nilesh
              access logs in Cloud?

              goto
              http://docs.oracle.com/cloud/123/developer_services/CSJSU/java-admin.htm#CACBHCGJ

              I see logs like the following
              Jun 3, 2013 7:55:32 PM PDT (Warning)
              Message Level     1
              Message     There was a failure in application ServletContext@357599642[app:opendata module:opendata.war path:/opendata spec-version:2.5] when attempting to inject dependencies into org.obrienlabs.opendatalink.MonitorManagedBean. Dependencies will not be injected into this class.

              If you select TRACE - you see detailed exceptions like
              essage Level     16
              Message     THROW
              Supplemental Detail     javax.servlet.ServletException: An error occurred performing resource injection on managed bean monitorBean at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325) at
              ...
              weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.sun.faces.mgbean.ManagedBeanCreationException: An error occurred performing resource injection on managed bean monitorBean at com.sun.faces.mgbean.BeanBuilder.injectResources(BeanBuilder.java:211) at com.sun.faces.mgbean.BeanBuilder.build(BeanBuilder.java:103) at

              see also unsupported WebLogic features doc at
              http://docs.oracle.com/cloud/CSJSU/feat_implement.htm#CEGBGCCE

              /michael