- OutSystems.com
-
My Platform
- Community
Log in
Sign Up
link管理
链接快照平台
- 输入网页链接，自动生成快照
- 标签化管理网页链接
相关文章推荐
|
豁达的跑步鞋 · 物理吸附问题集锦（二）_辰麦检测· 3 月前 · |
|
|
发呆的黑框眼镜 · 星云加速器下载地址-水母加速器· 3 月前 · |
|
|
气势凌人的大葱 · 在adf中将字符串转换为星号-腾讯云开发者社 ...· 5 月前 · |
|
|
含蓄的人字拖 · Scientific Python - ...· 5 月前 · |
|
|
气宇轩昂的香菇 · 清冷美人的神奇游戏(抹茶沙冰)最新章节_清冷 ...· 8 月前 · |
wrote:
Agree with Jorge, you're probably going to find an SSL certificate issue at play.
At design time, it is your copy of Service Studio on your desktop doing the SSL connection to the REST service, at run time it is the Java application container on the server doing the connection, they may have very different lists of trusted certificates.
J.Ja
I don't think so. During design time, I am connected to the environment and test connection call is going from the environment where I have connected.
Earlier, even the test connection was failing. I have imported the SSL certificate into the server environment, then the test connection (design time) has started working. I thought everything would be fine then, but surprised when it is not working during run time. (Please dev and front-end is the same server)
I think that proves that design time and run time is in the same environment. However, one work others don't
I have used below instructions to install the certificate into the environment.
https://success.outsystems.com/Support/Enterprise_Customers/Installation/Install_a_trusted_root_CA__or_self-signed_certificate
Thereafter, the test connection started working. but run time connection is not.
Hi Arunkumar.
Did you follow the instructions to install the certificate on a Windows machine or a Linux machine?
The error you provided is a Java error, which means your platform server is running on a Linux machine. Your development environment (Service Studio) is a Windows desktop application. So they cannot be the same machine.
I suspect that you have installed the certificate on your development environment (the Windows machine running Service Studio). If that's the case, then you must also install the certificate on the Linux machine running your platform server.
I have followed the instruction given for the Linux machine. I have installed the certificate on the linux server where the platform server installed. But still the error.
Fortunately, I have another windows environment. I follow the instruction given on the same page . I have installed the certificate there. It is working if I connect to windows environment. So that I am able to continue.
But still, it is an issue with Linux stack.
Your error is a closed connection by remote host, so it would be good if you could obtain logs from the remote host to see if there's any reason why it's rejecting the linux requests.
This could be related to the TLS version being supported by the remote host. If the remote host supports only TLS 1.2, and weblogic is trying to connect using TLS 1.0 or 1.1, then you won't be able to connect, even though you have correctly installed the certificate.
There are online tools that show which TLS versions your server is accepting, for example: https://www.ssllabs.com/ssltest/ . On your weblogic client, you can add the option -javax.net.debug=ssl to the JVM initialization script, and this will log information about the SSL handshake, including the TLS version being used. You can then compare the versions and see if there's a mismatch.