Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
"CIP4 Alces DRUPA-16.05.exe" is not connecting with Tomcat 8.5 server in HTTPS mode
Description
while connecting with tomcat 8.5.9 server in https mode,"CIP4 Alces DRUPA-16.05.exe" is unable to create connection. But the same server can able to connect using "CIP4 Alces DRUPA-16.05-bin". Also, both alces "exe" as well as "bin" can able to connect using http mode. This issue is only visible after upgrading the tomcat server from 6.0.45 to 8.5.9 . PFA of log (alces.log), CIP4 Alces DRUPA-16.05-bin working scenario(screenshot_bat file.jpg), CIP4 Alces DRUPA-16.05.exe not working scenario(screensot_exe.jpg).
Environment
None
Draft
None
Attachments
3
screenshot_bat file.jpg
04 Jan, 2017
screensot_exe.jpg
04 Jan, 2017
alces.log
04 Jan, 2017
Activity
Michel Hartmann
May 20, 2021 at 1:47 PM
#T&I WG 2021-05-20
We are closing this issue due to inactivity and age.
Michel Hartmann
April 15, 2021 at 1:58 PM
#T&I WG 2021-03-15
Hi, @sangeeth c, since this issue is already a few days old, I'd assume that you are not using the referenced version any more. Do you still have this issue in newer version, or can we close it?
Stefan Meissner
February 14, 2018 at 12:47 PM
This part of the application hasn't changed for years. May be you can solve this issue by trusting your self signed certificates on system level manually (i. e. Java Settings etc).
Alces uses a very old library which does not support specific certificate configurations. In order to fix this issue, we would have to refactor the whole connectivity part. If you are capable to refactor this part of the application, feel free to do so!
sangeeth c
February 14, 2018 at 11:17 AM
Yes we are working using self signed certificates. if this is a ssl certificate issue, we should face this issue with every other jdf tools. But server can connect using "CIP4 Alces DRUPA-16.05-bin" version as well as other JDF tools using HTTPS connection
Stefan Meissner
January 18, 2018 at 2:56 PM
@sangeeth c, ping
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
while connecting with tomcat 8.5.9 server in https mode,"CIP4 Alces DRUPA-16.05.exe" is unable to create connection. But the same server can able to connect using "CIP4 Alces DRUPA-16.05-bin".
Also, both alces "exe" as well as "bin" can able to connect using http mode.
This issue is only visible after upgrading the tomcat server from 6.0.45 to 8.5.9 .
PFA of log (alces.log), CIP4 Alces DRUPA-16.05-bin working scenario(screenshot_bat file.jpg), CIP4 Alces DRUPA-16.05.exe not working scenario(screensot_exe.jpg).