Solace .NET API

Access type mismatch has been reported before - the user was able to resolve the problem: Boomi Solace listener: com.solacesystems.jcsmp.PropertyMismatchException: Access Type mismatch — Solace Community
I’ll dig a bit deeper later this week.

And also for DLQ I am looking for if any other properties are to be set and what values need to be for retries as well.
I was having error in my process before reaching destination so the message stays in queue - how many retries will happen in order for message to go DLQ and which properties to be configured for that.
These are setting on the queue that you do not have control over when creating queues automatically. Defaults will be used for this (the documentation currently doesn’t list the defaults, I’ll add an enhancement request for it). You can change the retry, DMQ behaviour, default TTL of messages etc via the Solace PS+ admin UI (or any of the other admin tools/protocols in case you are automating broker configuration)