Our servers run on Linux and when I deploy from Studio the services all run well on all servers. I want to use the cdd method though and have a directory (on Linux) for that. It's shared for direct access from Windows. I use the deployment console on Windows, where I create the cdd and precompile the EDS. A number of small test services have been deployed and run fine, but the more elaborate ones that I've been trying to deploy are consistently giving the following error when testing from Studio with a rule test.
"Error while trying to execute against Remote Decision Service. Please review log for detailed description of the error."
The server log shows the following message:
"CcServer.execute(Document, String, String) (DecisionServiceName=documentDecision[-1, -1, null], HostLocation=cort.dev.local) -- Execution failed due to problems in the Reactor"
The same test works fine on a local Windows instance of the server with the same deployment method. It also works fine when the service is deployed to Linux through studio.
Does anyone have suggestions where to look for a solution?
Our servers run on Linux and when I deploy from Studio the services all run well on all servers. I want to use the cdd method though and have a directory (on Linux) for that. It's shared for direct access from Windows. I use the deployment console on Windows, where I create the cdd and precompile the EDS. A number of small test services have been deployed and run fine, but the more elaborate ones that I've been trying to deploy are consistently giving the following error when testing from Studio with a rule test.
"Error while trying to execute against Remote Decision Service. Please review log for detailed description of the error."
The server log shows the following message:
"CcServer.execute(Document, String, String) (DecisionServiceName=documentDecision[-1, -1, null], HostLocation=cort.dev.local) -- Execution failed due to problems in the Reactor"
The same test works fine on a local Windows instance of the server with the same deployment method. It also works fine when the service is deployed to Linux through studio.
Does anyone have suggestions where to look for a solution?
Flag this post as spam/abuse.
We have a production license installed.
Your post inspired me to try this approach. It's not mu preferred method and I expected it to be a lot of work, which it isn't.
The message is gone and the service executes fine from Studio tests. The WSDL gets automatically added too now. I had forgotten to mention before that WSDLs weren't added.
Could this have something to do with compiling on and deploying from one machine to another?
I can try get a log file to you directly, but I need to take some confidential lines out of it first.
Thank you
We have a production license installed.
Your post inspired me to try this approach. It's not mu preferred method and I expected it to be a lot of work, which it isn't.
The message is gone and the service executes fine from Studio tests. The WSDL gets automatically added too now. I had forgotten to mention before that WSDLs weren't added.
Could this have something to do with compiling on and deploying from one machine to another?
I can try get a log file to you directly, but I need to take some confidential lines out of it first.
Thank you
Flag this post as spam/abuse.
That's an excellent observation. As a matter of fact, the localhost version that does work is 5.4.0, while Studio runs 5.4.1 b6506, which is the same as the version on the development server, where things don't work. I'm pretty sure that this sounds opposite of what would make sense. :-S
As it turns out, the deployment console was using Java 7 while the Linux box is running on Java 6. After downgrading the deployment console's JDK and a few tweaks with extended operators, this worked again. Still not getting an auto-generated WSDL though.
By auto-genrated WSDL, do you mean the WSDL within the .eds file or the link to the WSDL that appears with the deployed decision service on the Server Console ?
The latter: the WSDL link on the console.