(Migrated) Re: Failing to create http channel

(This message has been automatically imported from the retired mailing list)

Here you go.
I cannot find any response in the admin log. I shut down the VM afterwards
so the below is the last two entries in the admin.log on server1. Server2
has nothing at the relevant time.

2014 - 10 - 16 19 : 17 : 28, 396 - INFO - 2690 : Dummy - 3 - zato_admin :
22 - cid : [K05FHDRM94Q7S2088TG6W9FE3BKK], name : [zato.service.invoke],
SIO request : [{
u ‘name’ : u ‘zato.http-soap.create’,
u ‘data_format’ : u ‘json’,
u ‘id’ : u ‘’,
u ‘channel’ : u ‘invoke’,
u ‘async’ : False,
u ‘payload’ : u
’eyJzZWNfdGxzX2NhX2NlcnRfaWQiOiAiWkFUT19OT05FIiwgImlzX2ludGVybmFsIjogZmFsc2=
Us\nICJzb2FwX2FjdGlvbiI6ICIiLCAiY2x1c3Rlcl9pZCI6ICIxIiwgImhhc19yYmFjIjogZmF=
sc2Us\nICJzZXJpYWxpemF0aW9uX3R5cGUiOiAic3RyaW5nIiwgInBpbmdfbWV0aG9kIjogbnVs=
bCwgImlk\nIjogbnVsbCwgInRyYW5zcG9ydCI6ICJwbGFpbl9odHRwIiwgInNlcnZpY2UiOiAic=
2lvLWV4YW1w\nbGUubXktc2VydmljZSIsICJzb2FwX3ZlcnNpb24iOiBudWxsLCAibWV0aG9kIj=
ogIiIsICJpc19h\nY3RpdmUiOiB0cnVlLCAiaG9zdCI6IG51bGwsICJ1cmxfcGF0aCI6ICJcL2p=
zb25cL3Npby1leGFt\ncGxlLm15LXNlcnZpY2UiLCAibWVyZ2VfdXJsX3BhcmFtc19yZXEiOiBm=
YWxzZSwgIm5hbWUiOiAi\nbXktc2VydmljZS5qc29uIiwgImRhdGFfZm9ybWF0IjogImpzb24iL=
CAicG9vbF9zaXplIjogbnVs\nbCwgInVybF9wYXJhbXNfcHJpIjogInFzLW92ZXItcGF0aCIsIC=
Jjb25uZWN0aW9uIjogImNoYW5u\nZWwiLCAidGltZW91dCI6IG51bGwsICJzZWN1cml0eV9pZCI=
6ICJaQVRPX05PTkUiLCAicGFyYW1z\nX3ByaSI6ICJjaGFubmVsLXBhcmFtcy1vdmVyLW1zZyJ9=
\n’,
u ‘transport’ : None,
u ‘expiration’ : 15
}
]
2014 - 10 - 16 19 : 17 : 28, 399 - INFO - 2690 : Dummy - 3 - zato_admin :
22 - cid : [K05FHDRM94Q7S2088TG6W9FE3BKK], name : [zato.http -
soap.create], SIO request : [{
u ‘sec_tls_ca_cert_id’ : u ‘ZATO_NONE’,
u ‘is_internal’ : False,
u ‘is_active’ : True,
u ‘soap_action’ : u ‘’,
u ‘host’ : None,
u ‘cluster_id’ : 1,
u ‘has_rbac’ : False,
u ‘serialization_type’ : u ‘string’,
u ‘url_path’ : u ‘/json/sio-example.my-service’,
u ‘transport’ : u ‘plain_http’,
u ‘ping_method’ : None,
u ‘name’ : u ‘my-service.json’,
u ‘service’ : u ‘sio-example.my-service’,
u ‘soap_version’ : None,
u ‘data_format’ : u ‘json’,
u ‘pool_size’ : None,
u ‘url_params_pri’ : u ‘qs-over-path’,
u ‘connection’ : u ‘channel’,
u ‘merge_url_params_req’ : False,
u ‘timeout’ : None,
u ‘security_id’ : u ‘ZATO_NONE’,
u ‘params_pri’ : u ‘channel-params-over-msg’,
u ‘method’ : u ‘’
}
]
On Thu, Oct 16, 2014 at 7:40 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 16/10/14 19:26, Baad Sequel wrote:

user@zatoTest:~/zato$ zato --version
Zato 2.0.0pre0.rev-3a804fec

When I try to create the http channel(following the example on same web
page). I do notice that the register http channel form has changed sinc=
e

1.1 and differs from the docs. I get this error when clicking OK after
filling in what I believe is the right details:

Hi Baad,

you’re on a recent version so can you please do the following?

  • Open /path/to/server/logs/admin.log
  • Find the CID K05FHDRM94Q7S2088TG6W9FE3BKK you received in response
  • Send the contents of admin.log related to that call from web-admin?
    Both request and response.

All the calls to admin services are now stored in admin.log so it’s easy
to find them.

On 16/10/14 19:50, Baad Sequel wrote:

I cannot find any response in the admin log. I shut down the VM
afterwards so the below is the last two entries in the admin.log on
server1. Server2 has nothing at the relevant time.

Thanks Baad - can you update to the latest from git
(689c519de5c7a73ed8fa3e66cac5963b3d73ba43 as of now) and try again?

On 16/10/14 19:50, Baad Sequel wrote:

I cannot find any response in the admin log. I shut down the VM
afterwards so the below is the last two entries in the admin.log on
server1. Server2 has nothing at the relevant time.

Thanks Baad - can you update to the latest from git
(689c519de5c7a73ed8fa3e66cac5963b3d73ba43 as of now) and try again?

Hi,
Pulled the git repo, and tried again.

user@zatoTest:~/zato$ zato --version
Zato 2.0.0pre0.rev-cd82c9b6

Channel registers ok, although the admin gui breaks.

When pressing OK after filling in the register plain http channel form the
gui dissapears and the following is shown:

{“message”: “Successfully created the Plain HTTP channel [my-service.json],
check server logs for details”, “id”: 357, “transport”: “plain_http”}

I guess it should route back to the admin gui?
You can always just click back in the browser, but it does not look very
slick :wink:

Anyway, service channel works:

user@zatoTest:~/zato$ curl localhost:17010/json/sio-example.my-service -d
’{“name”:“wendy”, “type”:“AXC”}’

{“response”: {“is_allowed”: true}}

Thanx!

On Thu, Oct 16, 2014 at 9:09 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 16/10/14 19:50, Baad Sequel wrote:

I cannot find any response in the admin log. I shut down the VM
afterwards so the below is the last two entries in the admin.log on
server1. Server2 has nothing at the relevant time.

Thanks Baad - can you update to the latest from git
(689c519de5c7a73ed8fa3e66cac5963b3d73ba43 as of now) and try again?


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python