Steps to reproduce:

./zabix_get_jmx 127.0.0.1 10052 10.136.92.11 56117 jmx.discovery
{"response":"failed","error":"bad protocol header: 7B 22 72 65 71"}

I'm using this to discover all MBeans. Zabbix is discovering default attributes from java.lang Garbage Collector, but I'm having issue with other unusual MBeans with their own attributes to monitor.

MBean Name & type: com.entimice.mod.sascontroller.poolmanagement.mbeans:type=SasPoolmanagerInfoMBean
And adding attribute
AverageAcquisitionTime

So all looks like this:

jmx[com.entimice.mod.sascontroller.poolmanagement.mbeans:type=SasPoolmanagerInfoMBean,AverageAcquisitionTime]

But it doesn't work , stil [no data] in Zabbix for that item.

That's why I used zabbix_get with jmx.discovery to check those MBeans , but i get bad protocol header. The thing is that I can even check those item which work in zabbix for example:

./zabbix_get_jmx 127.0.0.1 10052 10.136.92.11 56117 'jmx[java.lang:type=Memory,HeapMemoryUsage.used]'
{"response":"failed","error":"bad protocol header: 7B 22 72 65 71"}

So I can't even check/debug what's seems to be the problem. Could someone help with investigating this?

Result:
See screenshot...
See log file...
See memory dump...
Expected:
See screenshot...
See attached patch file...