wls_deployment timeout about biemond-orawls HOT 5 CLOSED

ok,

we added this timeout cause of the WLST domain daemon, when the py code is not a valid, it will fail and I can't see it and continue forever.

is the app so big that you get a timeout. Probably there is some wlst error in my wls deployment type .
else we can ask @hajee and maybe set this parameter on the wls_setting type

from biemond-orawls.

I'm able to login to the app after the puppet run, it just takes a while to deploy. I was able to bump the timeout in easy_type and it no longer generated the timeout error. Tough problem if invalid py code simply hangs forever.

from biemond-orawls.

good,

Probably the wls_deployment is the only one which can take a long time. But when it hangs on a py formatting error it will a bug of me in one of the py scripts. I didn't validate or test all the parameter combinations

But the timeout is necessary I think when you run puppet in the background and set the timeout parameter on forever.

from biemond-orawls.

You could change line to have a longer timeout. Best thing would be if we could add a timeout parameter to each type. I'll think about that one.

from biemond-orawls.

The Oracle custom types base on easy_type use this:

....

      if timeout_specified
        daemon.execute_sql_command(command, outFile.path, timeout_specified)
      else
        daemon.execute_sql_command(command, outFile.path)
      end
      File.read(outFile.path)
    end

    # This is a little hack to get a specified timeout value
     def timeout_specified
      if respond_to?(:to_hash)
        to_hash.fetch(:timeout) { nil} #
      else
        nil
      end
    end

Maybe you can use this also!

from biemond-orawls.