com.opentext.api.LLIOException - Could not access server

We have an application connecting to ll 9.7.1 using the web services both on authenticated and non authenticeted side. quite often we have an error: "com.opentext.api.LLIOException: Could not access server"

we have 2 instance of livelink with 2 IP addresses and one livelink server install on port 2099 and the other one on port 3099.

in the web.config instance one we have:

and the other web.config on the second instance have:

should I have one web.config pointing to port 3099? Does livelink services listen on all IP addresses so it does not matter which IP I use?

Find more posts tagged with

Comments

Jason_Smith

Not sure I clearly understand your hardware specs here. Are these separate machines or one machine with multiple IP addresses?

Either way it looks like you need to set the livelink.port to 3099 for one of them. It is the port that determines what instance it will communicate with since communication from the application server to Content Server is a direct socket connection using this port.

Kyle_Swidrovich

LLServer only binds to a single IP, so if you have two NICs in the server, it’ll only be listening on one of them.

Guy_Pomerleau

Thanks guys. To complete the info. On the same machine with 2 IP adress I have 2 instances installed (in fact I have 2 server with 2 instance behind a load balancer). One is on port 2099 and one on port 3099. I have 2 web site with one on each Ip. Each web site have a virtuel folder pointing to the "web services' folder.

http://livelink/livelink/les-services/... is load balance among the 4 web sites (4 ip on 2 servers)

So you are saying the livelink serveur is listening only on 1 IP, so how come both web site works?

Now my question, I assume to load balance the charge and for redundancy, I should have one web.config pointing to port 2099 and the other one 3099. And for livelink.host, should I have the servername, localhost or the ip adress of each web site?

Kyle_Swidrovich

Sorry, let me clarify. It will bind to an single IP version stack. That is, it can’t simultaneously listen for both IPv4 and IPv6 traffic.