Author Message
JamesCregeen2
Joined: Sep 15, 2011
Messages: 2
Offline
Can Avaya clarify that the issue raised in JBoss AS7 is not present when using in JBoss EAPv6.4, excerpt below from the AAOD v7.1 release notes (aaod-7_1_0_0_1212-release-notes):

Section 4 Known Issues: “JBOSS AS7 – On this version of JBOSS, HTTPS for the license URL will not function properly. You can just use HTTP for the WebLM license URL. If you must use HTTPS for the WebLM license URL please contact Tier 4 support for a resolution. HTTPS does not currently work due to issues in the WebLM client library.”


The reason for asking is that the OD Runtime does not attempt to contact the License URL if a ‘https’ address is used in the License URL field -eg. https://<weblmserver.internal.com>:8443
Verified by running a tcpdump command on the WebLM server for port 8443

If I change the url to http://<welbmserver.internal.com>:8443 I can see traffic via tcpdump however this will be to the standard webLM 400 bad Request error page.

I've tried IP and hostnames both have the same effect.

versions:
AAOD 7_1_0_0_1212
JBoss EAD6.4
Tomcat 7
Standalone WebLM on VMware 7.1.11.0 Build Number 7.1.0.0.11.25605

WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
Basically what it says is when you have the https weblm url set in Runtimeconfig, when you run the app, you would see a failure getting the runtime license in the app trace.log at the start of the call. You can post the app trace.log. We can take a look to see what is going on exactly.
JamesCregeen2
Joined: Sep 15, 2011
Messages: 2
Offline
Thanks, I'll get the logs files off the developers and post once obtained.
Go to:   
Mobile view