Use this Forum to post your “How to …” questions about your use of aXes. This is not a technical support forum. Both the aXes Support Team at LANSA and other aXes customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.
we run aXes in a IBM i and there is sometimes that the users in some companies (at least happend in 2 different companies) they get following response from aXes:
The application works correctly 10s of other companies, just in these 2 we get this message from time to time...
It looks like the attached screenshot and error message are not accessible at the moment, but I experienced a similar issue earlier.
unnamed.png (5.66 KiB) Viewed 25 times
After investigating, we found that Trend Micro’s Virus Buster “Real-Time Scan” feature was affecting JSM sessions.
We also confirmed that adding the AXES URL to the exception list for that feature prevents the sessions from being disconnected (see the figure below).
image001.png (317.77 KiB) Viewed 25 times
So you might want to check similar settings in your antivirus software.
I experienced a similar issue in my environemt in the past, so I’d like to share what I found at that time.
It only occurred for JSM sessions via AWS (it did not happen with internal connections or VPN connections).
After about five minutes since the JSM session signed on, the session was disconnected, and the following message appeared on the AXES sign-on screen:
Disconnected - Unexpected client request, unexpected client IP address
Ultimately, the issue was resolved by changing the forwarding method to IBM i from an ALB (Application Load Balancer) to an NLB (Network Load Balancer).
My understanding is that this change fixed the problem by replacing periodically changing internal IP addresses with a fixed one.
