Visual LANSA Forum

Posted: **Fri Dec 10, 2021 10:07 am**

Hello forum,

I'm trying to setup a JSM pool server from this tip with no luck.

https://docs.lansa.com/14/en/lansa093/i ... 3_0055.htm

The AMPJSMLIB subsystem is starting the 6 job and pointing to the correct 3 ports (see attached file).

: jobs.jpg (117.24 KiB) Viewed 27248 times

If I use the pool server port 4472 in the open_jsm, the jsmdirect does not work.

ERR3014
No data returned from service
DEBITOBACKOFFICE

If I use the port 4572 which the first tcp port defined, the JSM_open works, but it does not used any additional ports. I’m sending hundreds of requests to test and all of them are handle by just port 4572.

Has anyone used the pool server setup? Any ideas how to troubleshoot?

this is an extract fo manager.properties

tcp.port=4572
tcp.backlog=20
tcp.interface=*all
tcp.client.address=*all
console.tcp.port=4573
console.tcp.backlog=20
console.tcp.interface=*all
console.client.address=*all
studio.client.address=*all
pool.tcp.port=4472
pool.tcp.backlog=20
pool.tcp.interface=*all
pool.hosts=HOST1:4572,HOST2:4372,HOST3:4272
#
# Additional instance 1
#
additional.tcp.port.1=4372
additional.tcp.interface.1=*all
#
# Additional instance 2
#
additional.tcp.port.2=4272
additional.tcp.interface.2=*all

Posted: **Fri Dec 10, 2021 10:56 am**

I think the manager.properties is wrong.

I think it should be something like:

Code: Select all

tcp.port=4572
tcp.backlog=20
tcp.interface=*all
tcp.client.address=*all
console.tcp.port=4573
console.tcp.backlog=20
console.tcp.interface=*all
console.client.address=*all
studio.client.address=*all
pool.tcp.port=4472
pool.tcp.backlog=20
pool.tcp.interface=*all
pool.hosts=HOST1:4574                    <<<< NOTE THE CHANGE
#
# Additional instance 1
#
additional.tcp.port.1=4372
additional.tcp.interface.1=*all
#
# Additional instance 2
#
additional.tcp.port.2=4272
additional.tcp.interface.2=*all

Posted: **Fri Dec 10, 2021 11:25 am**

thanks, I will try it as soon as I get back to my post. where is that 4574 port coming from?

Posted: **Sat Dec 11, 2021 4:41 am**

Hi Brendan, I made the change and still does not work.

I tried the jsm_open with ports 4472(pool server) 4574(host) and 4572(one of three ports)

on 4472 - jsmdirect error
on 4574 - jsmdirect error
on 4572 - no error, but process only in one job.

Here the 3 managers started in the trace

Manager 1

Code: Select all

manager: manager server configuration
manager: tcp.port           : 4572
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4572 across all interfaces
manager: bind to socket address
manager: start manager server

manager: pool server configuration
manager: pool.tcp.port           : 4472
manager: pool.tcp.interface      : *all
manager: pool.tcp.backlog        : 20
manager: pool.tcp.nodelay        : <null>
manager: pool.tcp.buffer.send    : <null>
manager: pool.tcp.buffer.receive : <null>
manager: create pool server
manager: create socket address to listen on port 4472 across all interfaces
manager: bind to socket address
manager: start pool server
manager: pool host : HOST1:4574

manager: console server configuration
manager: console.tcp.port           : 4573
manager: console.tcp.interface      : *all
manager: console.tcp.backlog        : 20
manager: console.tcp.nodelay        : <null>
manager: console.tcp.buffer.send    : <null>
manager: console.tcp.buffer.receive : <null>
manager: create console server
manager: create socket address to listen on port 4573 across all interfaces
manager: bind to socket address
manager: start console server

manager: instance servers started

manager: accept all connections
manager: ready

Manager 2

Code: Select all

manager: manager server configuration
manager: tcp.port           : 4572
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4572 across all interfaces
manager: bind to socket address
manager: bind exception : El nombre de socket ya se está utilizando. (Bind failed)

manager: manager server configuration
manager: tcp.port           : 4372
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4372 across all interfaces
manager: bind to socket address
manager: start manager server

manager: no pool server configuration

manager: no console server configuration

manager: additional '1' instance servers started

manager: accept all connections
manager: ready

Manager 3

Code: Select all

manager: manager server configuration
manager: tcp.port           : 4572
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4572 across all interfaces
manager: bind to socket address
manager: bind exception : El nombre de socket ya se está utilizando. (Bind failed)

manager: manager server configuration
manager: tcp.port           : 4372
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4372 across all interfaces
manager: bind to socket address
manager: bind exception : El nombre de socket ya se está utilizando. (Bind failed)

manager: manager server configuration
manager: tcp.port           : 4272
manager: tcp.interface      : *all
manager: tcp.backlog        : 20
manager: tcp.nodelay        : <null>
manager: tcp.buffer.send    : <null>
manager: tcp.buffer.receive : <null>
manager: create manager server
manager: create socket address to listen on port 4272 across all interfaces
manager: bind to socket address
manager: start manager server

manager: no pool server configuration

manager: no console server configuration

manager: additional '2' instance servers started

manager: accept all connections
manager: ready

I found this in two of the manager traces

"manager: bind exception : El nombre de socket ya se está utilizando. (Bind failed)"
translated to: manager: bind exception : name of the socket already in use. (Bind failed)

I wonder if this is normal warning or there's something really wrong.

I appreciate the help...

Posted: **Thu Dec 16, 2021 10:00 am**

Hi Cesar ,

According to the guides it should look something like this , if you want 3 ports to run on

Code: Select all

 
 # Manager Server definition 
tcp.port=4560
tcp.backlog=256
tcp.timeout=2000
tcp.interface=*all
#
console.tcp.port=4561
console.tcp.backlog=5
console.tcp.timeout=2000
console.tcp.interface=*all
#
[b]# Pool server definition[/b]
pool.tcp.port=4562
pool.tcp.backlog=100
pool.tcp.timeout=2000
pool.tcp.interface=*all
#
pool.hosts=LOCALHOST:4564,LOCALHOST:4566,LOCALHOST:4568
#
# Default Server (Server 0 )
tcp.port=4564
tcp.interface=*all
tcp.backlog=50
console.tcp.port=4565
console.tcp.backlog=5
console.timezone=GMT+01:00
#
# Additional Server (Server 1 )
additional.tcp.port.1=4566
additional.tcp.interface.1=*all
additional.tcp.backlog.1=50
additional.console.tcp.port.1=4567
additional.console.tcp.backlog.1=5
additional.console.timezone.1=GMT+01:00
#
# Additional Server (Server 2) 
additional.tcp.port.2=4568
additional.tcp.interface.2=*all
additional.tcp.backlog.2=50
additional.console.tcp.port=4569
additional.console.tcp.backlog.2=5
additional.console.timezone.2=GMT+01:00

Visual LANSA Forum

Integrator Pool Server

Integrator Pool Server

Re: Integrator Pool Server

Re: Integrator Pool Server

Re: Integrator Pool Server

Re: Integrator Pool Server