Pub Sub Issue v3.2

Hi Guys

I’m busy evaluating Zato ESB.

I’m having issues with creating pubsub topics and endpoints

Ive created a simple pub sub topic /ticket/service/incident via admin
and end endpoint ticket.pubsub.incident.endpoint
with
pub=/ticket/service/incident/*
sub=/ticket/service/incident/*

I cant seem to publish to this endpoint, always getting an error →
CID: 9213c14fbe3d5973a3aa3e8c
Details: You are not allowed to access this resource

what could cause this ? This is on 3.2 version.

Thanks,

Albert

Hello @albertoncaffeine,

to make sure that you have all the latest updates - can you please send in the output from this command?

$ zato --version

Thanks.

Hi @dsuch

Thanks, I’m running this on a docker container, for some reason cant executing the command on CLI
Not sure if below could help ?

cat release.json

{“major”:3, “minor”:“2”, “micro”:“0”}

cat revision.txt

b179426108a88126e892516be0710ade8a212a4d#

This does not seem to be the latest version - please install all the updates and post back the output from “zato --version”.

Also trying out on v3.1 stable

self.patterns.parallel.invoke and self.patterns.fanout.invoke

I’m get a strange response in the logs and callbacks are not executed, not sure if i missed some configurations.

2021-03-09 12:21:43,834 DEBG 'zatoserver1' std

out output:

2021-03-09 12:21:43,833 - ERROR - 487:DummyThread-290 - zato:0 - Could not handle broker msg:Bunch(action='101802', callback=None, channel='parallel-exec-call', cid='e08309eec89731a49339100c', data_format='dict', environ={}, is_async=True, msg_type='0001', payload='{}', service='za.service.ticket.create-ticket-sm9', transport=None, zato_ctx={'parallel_exec_cid': 'b010f3c7bf2cfccb08ee3c8b'}), e:`Traceback (most recent call last):

File “/opt/zato/3.1.0/code/zato-broker/src/zato/broker/init.py”, line 52, in on_broker_msg

getattr(self, handler)(msg)

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/base/worker/init.py”, line 1891, in on_broker_msg_SERVICE_PUBLISH

return self.on_message_invoke_service(msg, msg.get(‘channel’) or CHANNEL.INVOKE_ASYNC, ‘SERVICE_PUBLISH’, args)

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/base/worker/init.py”, line 1576, in on_message_invoke_service

environ=msg.get(‘environ’))

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/service/init.py”, line 606, in update_handle

wmq_ctx=kwargs.get(‘wmq_ctx’), channel_info=kwargs.get(‘channel_info’))

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/service/init.py”, line 1166, in update

channel_item.get(‘id’), channel_item.get(‘name’), channel_type,

AttributeError: ‘NoneType’ object has no attribute ‘get’

`

2021-03-09 12:21:43,837 DEBG ‘zatoserver2’ stdout output:

2021-03-09 12:21:43,837 - ERROR - 511:DummyThread-297 - zato:0 - Could not handle broker msg:Bunch(action='101802', callback=None, channel='parallel-exec-call', cid='548a4e860ba913c149109b35', data_format='dict', environ={}, is_async=True, msg_type='0001', payload='{}', service='za.service.ticket.create-ticket-cache', transport=None, zato_ctx={'parallel_exec_cid': 'b010f3c7bf2cfccb08ee3c8b'}), e:`Traceback (most recent call last):

File “/opt/zato/3.1.0/code/zato-broker/src/zato/broker/init.py”, line 52, in on_broker_msg

getattr(self, handler)(msg)

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/base/worker/init.py”, line 1891, in on_broker_msg_SERVICE_PUBLISH

return self.on_message_invoke_service(msg, msg.get(‘channel’) or CHANNEL.INVOKE_ASYNC, ‘SERVICE_PUBLISH’, args)

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/base/worker/init.py”, line 1576, in on_message_invoke_service

environ=msg.get(‘environ’))

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/service/init.py”, line 606, in update_handle

wmq_ctx=kwargs.get(‘wmq_ctx’), channel_info=kwargs.get(‘channel_info’))

File “/opt/zato/3.1.0/code/zato-server/src/zato/server/service/init.py”, line 1166, in update

channel_item.get(‘id’), channel_item.get(‘name’), channel_type,

AttributeError: ‘NoneType’ object has no attribute ‘get’

Hi @dsuch

Thanks so much, i downloaded stable version 3.1. all seems working fine now.

Best Regards,

Albert

Please note that v3.2 is slated for a release very soon - within a week or two - and any new installation should use 3.2 instead of 3.1.

There have been numerous changes to pub/sub in 3.2 and community support for 3.1 will be dropped as soon as 3.2 is out.

@dsuch Thank you. Let me try get updates on 3.2 and run some updates, will keep you posted