Re: [Ftpapi] HTTPAPI DNS resolve message

Hi Scott,

Thanks for your prompt reply.

Ah okay. Thanks for confirming. We thought so but can't be 100% sure.

Yes, there's an issue when calling the xdealloc procedure with error but it only happens once in a blue moon.

In the job log, I did notice "The starting address for reallocation is not valid".

However, I made another finding today related to same functionality which is not related to HTTPAPI but is related to you though, YAJL. :-)

The same program utilise both service program to make a restful web service call which returns json.

I'm not going into detail of which line it crashed in YAJL because this is not the right place for it but I noticed that you've fixed it, discussed in the code400.com site. Just downloaded the latest YAJL from your website and going to deploy it and observe to see any more issue occurring.

I thought the xdealloc issue happened because of a knock effect in YAJL but can't prove that just yet.

Eric

On 15 February 2017 at 15:28, Scott Klement <sk@xxxxxxxxxxxxxxxx> wrote:

Eric,

The messages you've provided are diagnostics, explaining how your system's DNS resolver is configured. It is not directly related to the code that you posted. Why are you asking this, is something not working?

-SK

On 2/15/17 3:03 AM, Eric wrote:
Hi,

I got this DNS message shown a few times today.

Does anyone know whether this is a diagnostic message or an actual error?

++++++++++++++++++++++++++++++++++++++

HTTPAPI Ver 1.24 released 2012-01-23

OS/400 Ver V7R1M0

2017-02-14-16.04.10.452000 http_persist_open(): entered

2017-02-14-16.04.10.456000 http_long_ParseURL(): entered

2017-02-14-16.04.10.456000 DNS resolver retrans: 2

2017-02-14-16.04.10.456000 DNS resolver retry : 2

2017-02-14-16.04.10.456000 DNS resolver options: x'00000136'

2017-02-14-16.04.10.456000 DNS default domain: xxx.xxxx.xxxx

2017-02-14-16.04.10.456000 DNS server found: 172.25.34.212

2017-02-14-16.04.10.456000 DNS server found: 172.25.32.211

++++++++++++++++++++++++++++++++++++++

This is in called in COMMSSLR4/CommSSL_New procedure

eval p_Resolve =%paddr('COMMTCP_RESOLVE')

eval p_Read =%paddr('COMMTCP_READ')

eval p_BlockRead =%paddr('COMMTCP_BLOCKREAD')

eval p_BlockWrite=%paddr('COMMTCP_BLOCKWRITE')

eval p_LineRead =%paddr('COMMTCP_LINEREAD')

eval p_LineWrite =%paddr('COMMTCP_LINEWRITE')

eval p_Hangup =%paddr('COMMTCP_HANGUP')

owever, are SSL-specific:

eval p_Connect =%paddr('COMMSSL_CONNECT')

eval p_Upgrade =%paddr('COMMSSL_UPGRADE')

eval p_Cleanup =%paddr('COMMSSL_CLEANUP')

I wasn't sure because this message appears in the RESOLVE, the next few procedures call are successful?

Thanks,
Eric
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi