2 Replies Latest reply: Mar 22, 2013 7:57 AM by 997468 RSS

    wlst "deploy(...)" shows an exception occurred but there are no details?

    Jon OBrien
      Hi,

      Using WLS 10.3.6

      I'm using a python script to call wlst command line to deploy our .ear application:

      try:
      print '---------------------------------------'
      print 'Deploying '+appName
      print '---------------------------------------'
      progress = deploy(appName, earPath, clusterName, 'nostage', securityModel='DDOnly')
      progress.printStatus()
      except Exception:
      print '======================================='
      print 'ERROR deploying '+appName+' on '+clusterName
      print '======================================='
      exit()
      pass

      The output shows the following:

      ---------------------------------------
      Deploying ISSViewer
      ---------------------------------------
      Deploying application from /app/oracle/admin/iss/deploy/6.5.2013.02.20.02.32.28/ISSViewer.ear to targets ISSVCluster (upload=false) ...
      <Feb 20, 2013 5:23:58 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, ISSViewer [archive: /app/oracle/admin/iss/deploy/6.5.2013.02.20.02.32.28
            /ISSViewer.ear], to ISSVCluster .>
      .Completed the deployment of Application with status completed
      Current Status of your Deployment:
      Deployment command type: deploy
      Deployment State : completed
      Deployment Message : [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application ISSViewer [Version=6.5.2013.02.20.02.32.28] on ISSVCluster.: .
      Current Status of your Deployment:
      Deployment command type: deploy
      Deployment State : completed
      Deployment Message : [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application ISSViewer [Version=6.5.2013.02.20.02.32.28] on ISSVCluster.: .

      The "Deployment Message" says an exception occurred but no exception details are shown and the app has actually deployed fine and works well.

      Is this a "real" exception?

      If so, how can I see details of what caused the exception?

      If it's not a "real" exception is there a way to get the deploy to display a more user friendly message?

      Thanks in advance

      Jon