Unknown host connection error in copied application

[Anon Anon]

I am missing an environment parameter and I cannot find where to set it, it appears to be hidden.

 

I exported a working application, and then immediately imported and renamed it effectively making a copy of a working application.

 

I sent a deployment through the new application and found quickly that the environment parameters do not export or import, so I re-populated those values.

 

(Included in those parameter values are database connection and credential values.)

 

However, the new application is still failing in initialization when the action attempts to insert a new record into the 'inflight' database.

 

The error claims unknown host.

 

Action failed. An error occurred during database connection establishment

Failed to get connection for: jdbc:oracle:thin:@//[e-mail]:'correct port number appears here'/'correct database info appears here'
IO Error: Unknown host specified

 

Any hints would be most appreciated.

 

Many thanks.

[Gregg Stewart]

Maybe the version (or tag) of the process that is being used isn't setting the hostname via an environment variable. You should be able to have a closer look at the action within the version of the process being used to see which variables it is using, their types, default values (for internal parameters), etc...

 

Since you said that you already repopulated the environment parameters for other env parameters it sounds like maybe the action isn't configured in the process correctly. Otherwise you should see env parameter for the hostname to set along with the other env parameters that you are giving values. If you confirm that the process is setup to correctly use an env parameter for the hostname then maybe try making a small change to save and republish and then check the env parameters section again. If that doesn't help then I would recommend opening a support issue.

 

Cheers,
Gregg

[Anon Anon]

thanks gregg, i touched it enough times and got it to recognize the values

 

when the error was originally being reported, the error message had the correct values in it for the conneciton, but it's like the code actually making the connection was only finding a null, even though the message displayed correct values.

 

but your recommendation was right on, i deleted, re-added the parameters, got a better message, re-published, and now have redundant tags and variables in my environment, but getting the process to execute, so progress...

 

i think there's an underlying issue here that will warrant a support ticket, but for now i'm moving on