| Author |
Message
|
| busy_chap |
 Posted: Thu Sep 14, 2006 10:19 am Post subject: Broker error |
 |
|
Acolyte
Joined: 18 May 2006
Posts: 69
|
hi ,
we are using Broker 2.1 on AIX. I am trying to view a flow but when I click on it I am getting the following error.
please help me regarding this.
Thanks.
BIP0062E Cannot read the XML data stream for a resource.
This is an internal error.
The following error occurred when parsing an XML data stream.
Processing MRM/84fdbd91-ed00-0000-0080-81ece6f8b901/MRElement, at line 2
before column 8124, "</D:collection>" expected.
Processing MRM/84fdbd91-ed00-0000-0080-81ece6f8b901/MRElement, at line 2
before column 8124, Invalid document structure.
Turn on Control Center tracing to capture details of the error.
Retry the operation and contact your IBM support center |
|
| Back to top |
|
 |
| busy_chap |
| Posted: Thu Sep 14, 2006 1:07 pm Post subject: Not even a single person knows about this? |
|
|
Acolyte
Joined: 18 May 2006
Posts: 69
|
| Not even a single person knows about this? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Sep 14, 2006 1:27 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
A quick search around hasn't found anything helpful... you could try recycling the control center .... otherwise call IBM service (quickly, while the product is still in support).
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 14, 2006 3:18 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| call IBM service (quickly, while the product is still in support). |
You have about two weeks.
I have forgotten everything I know about 2.1.
On purpose.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 14, 2006 3:33 pm Post subject: Re: Broker error |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| busy_chap wrote: |
hi ,
we are using Broker 2.1 on AIX. I am trying to view a flow but when I click on it I am getting the following error.
please help me regarding this.
Thanks.
BIP0062E Cannot read the XML data stream for a resource.
This is an internal error.
The following error occurred when parsing an XML data stream.
Processing MRM/84fdbd91-ed00-0000-0080-81ece6f8b901/MRElement, at line 2
before column 8124, "</D:collection>" expected.
Processing MRM/84fdbd91-ed00-0000-0080-81ece6f8b901/MRElement, at line 2
before column 8124, Invalid document structure.
Turn on Control Center tracing to capture details of the error.
Retry the operation and contact your IBM support center |
Could it be that you are missing a closing tag with namespace prefix like say
</D:collection>? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Sep 14, 2006 7:03 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi busy_chap,
This "Invalid document structure" happens once in a while when i have opened the toolkit but done some changes to the file in the workspace from the file system...
I usually close the project and open again and rebuild, it works for me...though i'm not sure of v2.1.
But as fjb_saper pointed, i think if you fix the </D:collection> error, it could get solved...do u have an earlier copy of the file ?
Regards. |
|
| Back to top |
|
|
| busy_chap |
| Posted: Fri Sep 15, 2006 5:22 am Post subject: not even a single message flow can be viewed |
|
|
Acolyte
Joined: 18 May 2006
Posts: 69
|
Thanks everybody for giving me some ideas. Now the problem has become even more worse.
I am unable to view all the other flows too and not even in a single workspace. I don't know if it is worth mentioning but some bad messages with different interface names were sent through a different WBI flow. It did error out at the beginning and after that it was corrected and good messages were sent through and broker processed them successfully.
AFter may be 3 or 4 hrs, when we tried to view the flows this is was the error that was displayed.
Can this be caused by some code change which is making the broker to reiterate and cause this error? I tried googling it but looks like this is a very peculiar error. |
|
| Back to top |
|
|
|
|
