How to debug app connection problem.

Posted by OctavioOlguin on 30-Jan-2015 13:07

Hi there!  Greetings friends.

(app server 11.5 on windows 7, 32 bits 4 gb ram, proof of concept for appserver adoption)

I have this problem... the following succeeds instantly to connect: 

lg = hs:connect ("-H 10.101.102.208 -DirectConnect -S 3090 -sessionModel Session-free ").

but when omitted  the -DirectConnect  parameter, the instruction waits some minute or so to fail with the message:

Name Server at Host 10.101.102.208 Port 3090 is not responsive. (8239)

Checkiing on knowledgebase , I disabled firewall, and stuff, but it won't connect.

The log of asbroker1.asbroker.log shows the connection, but not the missed connection.

Is there some kind of debugging info that allows me to catch where the error is?

OpenEdge General - Forum

All Replies

Posted by TheMadDBA on 30-Jan-2015 13:14

When you use -DirectConnect the -S value is the port of the AppServer you are directly connecting to.

If you want to use the NameServer to connect to the appserver you need to use this syntax:

-AppService appservice -H nameserverhost -S nameserverport

Posted by Libor Laubacher on 30-Jan-2015 13:16

The message itself answers the question IMO.

Ø  Name Server at Host 10.101.102.208 Port 3090 is not responsive. (8239)

When you don’t specify the –DirectConnect (read: direct connect to AppServer broker), the connection goes via nameserver.

You nameserver is not running on port 3090 as the message says.

 

 
[collapse]
From: OctavioOlguin [mailto:bounce-OctavioOlguin@community.progress.com]
Sent: Friday, January 30, 2015 8:09 PM
To: TU.OE.General@community.progress.com
Subject: [Technical Users - OE General] How to debug app connection problem.
 
Thread created by OctavioOlguin

Hi there!  Greetings friends.

(app server 11.5 on windows 7, 32 bits 4 gb ram, proof of concept for appserver adoption)

I have this problem... the following succeeds instantly to connect: 

lg = hs:connect ("-H 10.101.102.208 -DirectConnect -S 3090 -sessionModel Session-free ").

but when omitted  the -DirectConnect  parameter, the instruction waits some minute or so to fail with the message:

Name Server at Host 10.101.102.208 Port 3090 is not responsive. (8239)

Checkiing on knowledgebase , I disabled firewall, and stuff, but it won't connect.

The log of asbroker1.asbroker.log shows the connection, but not the missed connection.

Is there some kind of debugging info that allows me to catch where the error is?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by OctavioOlguin on 30-Jan-2015 13:56

Thanks all for the info.

but.....

these are last events on log (apart from numerous 8209 message lines )

  1. [15/01/30@11:20:09.525-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  2. [15/01/30@11:20:16.429-0600] P-004844 T-NS1 2 NS NSPlumbing Desregistrando el Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8210)
  3. [15/01/30@11:20:24.837-0600] P-004844 T-NS1 2 NS NSPlumbing Registrando el Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8205)
  4. [15/01/30@11:20:24.838-0600] P-004844 T-NS1 2 NS NSPlumbing Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 Ha sido registrado para el Application Service AS.schAS1. (8207)
  5. [15/01/30@11:20:24.838-0600] P-004844 T-NS1 3 NS NSPlumbing Respuesta mandada a 127.0.0.1 59872. (8202)
  6. [15/01/30@11:20:54.842-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  7. [15/01/30@11:21:24.842-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  8. [15/01/30@11:21:47.718-0600] P-004844 T-NS1 3 NS NSPlumbing Petición recibido desde 10.101.102.66 58515 para AS.[Default]. (8201)
  9. [15/01/30@11:21:47.719-0600] P-004844 T-NS1 3 NS NSPlumbing AppService = AS.[Default] Encontró = false Número de Brokers = 1. (8206)
  10. [15/01/30@11:21:47.758-0600] P-004844 T-NS1 3 NS NSPlumbing Respuesta mandada a 10.101.102.66 58515. (8202)

the lines like 323 or  329 appears hundreds of times.

line 323, ip 66 is the machine I use to test, is where connection was achieved...

this is the beginning of log file, as I restarted computer...

  1. ======================================================================
  2. [15/01/30@08:45:03.194-0600] P-004844 T-main 1 --- --- C:\OpenEdge\WRK\NS1.ns.log opened.
  3. [15/01/30@08:45:03.199-0600] P-004844 T-main 1 --- --- Logging level set to = 4
  4. [15/01/30@08:45:03.199-0600] P-004844 T-main 1 --- --- Log entry types activated: NSPlumbing,
  5. [15/01/30@08:45:03.220-0600] P-004844 T-main 2 NS NSPlumbing Reading Ubroker Property File Name : C:\Progress\OpenEdge\properties\ubroker.properties
  6. [15/01/30@08:45:03.220-0600] P-004844 T-main 2 NS NSPlumbing RestartPort Property Value :0
  7. [15/01/30@08:45:03.223-0600] P-004844 T-main 2 NS NSPlumbing Inicializando el NameServer NS1 rmi://appserver:20931/NS1 Puerto = 5162 TimeOut = 35. (8196)
  8. [15/01/30@08:45:03.224-0600] P-004844 T-main 2 NS NSPlumbing Balanceo de Cargas deshabilitado para el NameServer NS1. (8200)
  9. [15/01/30@08:45:08.446-0600] P-004844 T-NS1 2 NS NSPlumbing Registrando el Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8205)
  10. [15/01/30@08:45:08.448-0600] P-004844 T-NS1 2 NS NSPlumbing Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 Ha sido registrado para el Application Service AS.schAS1. (8207)
  11. [15/01/30@08:45:08.449-0600] P-004844 T-NS1 3 NS NSPlumbing Respuesta mandada a 127.0.0.1 55885. (8202)

The following instruction gives a connection:

lg = hs:connect ("-H 10.101.102.208 -S 5162 -AppService schAS1 -sessionModel Session-free").

As instructed by Libor (thanks btw)

So then I'm confused:  Must I route port 3090 udp/tcp on firewall (pf sense) or 5162 udp/tcp, or both or some combination of udp  - tcp ?  Is the 5162 port changing on some future event (restart/reboot)?

I guess one port is where the service will be available? and other for the nameserver?  If so, there is a range of ports to be used?  all clients come through 3090? or 3090 is just the first of a pool ?

Posted by Libor Laubacher on 30-Jan-2015 14:01

Octavio,
 
are you going to use DirectConnect or go via NS ?
 
Well – check this article http://knowledgebase.progress.com/articles/Article/P111654 for the ports & firewall
 
/LL
 
[collapse]
From: OctavioOlguin [mailto:bounce-OctavioOlguin@community.progress.com]
Sent: Friday, January 30, 2015 8:58 PM
To: TU.OE.General@community.progress.com
Subject: RE: [Technical Users - OE General] How to debug app connection problem.
 
Reply by OctavioOlguin

Thanks all for the info.

but.....

these are last events on log (apart from numerous 8209 message lines )

  1. [15/01/30@11:20:09.525-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  1. [15/01/30@11:20:16.429-0600] P-004844 T-NS1 2 NS NSPlumbing Desregistrando el Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8210)
  1. [15/01/30@11:20:24.837-0600] P-004844 T-NS1 2 NS NSPlumbing Registrando el Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8205)
  1. [15/01/30@11:20:24.838-0600] P-004844 T-NS1 2 NS NSPlumbing Broker 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 Ha sido registrado para el Application Service AS.schAS1. (8207)
  1. [15/01/30@11:20:24.838-0600] P-004844 T-NS1 3 NS NSPlumbing Respuesta mandada a 127.0.0.1 59872. (8202)
  1. [15/01/30@11:20:54.842-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  1. [15/01/30@11:21:24.842-0600] P-004844 T-NS1 3 NS NSPlumbing Broker ya conocido 932.99.999.XXX:1ee77e:cf3bbe3d33:-8000 AS.asbroker1 appserver/10.101.102.208 3090. (8209)
  1. [15/01/30@11:21:47.718-0600] P-004844 T-NS1 3 NS NSPlumbing Petición recibido desde 10.101.102.66 58515 para AS.[Default]. (8201)
  1. [15/01/30@11:21:47.719-0600] P-004844 T-NS1 3 NS NSPlumbing AppService = AS.[Default] Encontró = false Número de Brokers = 1. (8206)
  1. [15/01/30@11:21:47.758-0600] P-004844 T-NS1 3 NS NSPlumbing Respuesta mandada a 10.101.102.66 58515. (8202)

the lines like 323 or  329 appears hundreds of times.

line 323, ip 66 is the machine I use to test, is where connection was achieved...

this is the beginning of log file, as I restarted computer...

  1. ======================================================================
  1. [15/01/30@08:45:03.194-0600] P-004844 T-main 1 --- --- C:\OpenEdge\WRK\NS1.ns.log opened.
  1. [15/01/30@08:45:03.199-0600] P-004844 T-main 1 --- --- Logging level set to = 4
[/collapse]

Posted by OctavioOlguin on 30-Jan-2015 14:19

Thanks Libor!!!

I think I should go NS, as directed by docs. that I read that advised against DirectConnect.

And the article you pointed was the missing info!!!

Thanks!!!

This thread is closed