| Author |
Message
|
| yobyalp |
 Posted: Tue Dec 01, 2015 2:20 am Post subject: JSON Parser error |
 |
|
Newbie
Joined: 18 Feb 2013
Posts: 6
|
Hi - Trying to construct JSON message using ESQL. Selected JSON parser and coding is done. while deploying getting below error.
Currently broker version V7.0.0.4
Required help on below.
++++++++++++++++++++++++++++++++++++++++++
BIP2087E: Broker <Broker> was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group '<EG>' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP2294E: The parser 'JSON' is not a valid message domain option on object 'JsonTestConsumer.HTTP Request' because the current fix pack function level of '7.0.0.1' does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality.
A configuration message was received, which had parser 'JSON' as the message domain option on object 'JsonTestConsumer.HTTP Request'. The message cannot be processed because the current fix pack function level of '7.0.0.1' does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this (and all other) functionality.
Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Dec 01, 2015 2:31 am Post subject: Re: JSON Parser error |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| yobyalp wrote: |
Currently broker version V7.0.0.4
|
and this
| yobyalp wrote: |
BIP2294E: The parser 'JSON' is not a valid message domain option on object 'JsonTestConsumer.HTTP Request' because the current fix pack function level of '7.0.0.1' does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality.
A configuration message was received, which had parser 'JSON' as the message domain option on object 'JsonTestConsumer.HTTP Request'. The message cannot be processed because the current fix pack function level of '7.0.0.1' does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this (and all other) functionality.
Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation. |
Seem to be at odds with each other.
Have you installed the 7.00.4 fixpack on the runtime?
If so, have you enabled it as recommended in the error message?
Finally,
V7 went out of support last September. Are you planning on moving to a newer version that will also have better JSON support?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Last edited by smdavies99 on Tue Dec 01, 2015 2:34 am; edited 1 time in total |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Dec 01, 2015 2:31 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| BIP2294E: The parser 'JSON' is not a valid message domain option on object 'JsonTestConsumer.HTTP Request' because the current fix pack function level of '7.0.0.1' does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality. |
Did you notice the above message embedded in the error you posted?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Dec 01, 2015 2:47 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You need to do -f all
That's what I always do..... 
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| yobyalp |
| Posted: Tue Dec 01, 2015 2:49 am Post subject: |
|
|
Newbie
Joined: 18 Feb 2013
Posts: 6
|
Yea there is plan to start migrate WMB 7 to IIB9 or 10 version in coming year from Jan 2016.
for JSON parser is it required to enable broker properties which will not impact on other parser which currently running.
mqsichangebroker <brokerName> -f all' |
|
| Back to top |
|
|
| timber |
| Posted: Tue Dec 01, 2015 5:13 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| for JSON parser is it required to enable broker properties which will not impact on other parser which currently running |
Not sure that I understand the question, but but the important facts are:
- you have v7.0.0.4
- you are running it with v7.0.0.1 capabilities
- if you want to use JSON then you must enable the v7.0.0.4 features using mqsichangebroker
You don't have to worry about affecting other parsers. The JSON parser is independent of the other parsers. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 01, 2015 5:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yobyalp wrote: |
| for JSON parser is it required to enable broker properties which will not impact on other parser which currently running. |
You can't enable one piece of new functionality (like the JSON parser) and not enable all the other new functions.
This is what you get for being so back level.
Try it on a test broker, and regression test any other functions you're particularly worried about.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
