| Author |
Message
|
| jius |
 Posted: Tue Jul 24, 2007 9:09 am Post subject: BIP2275E: DatabaseRecord... with MessageFlow is not valid |
 |
|
Newbie
Joined: 24 Jul 2007
Posts: 2
|
Hi,
I'm new here.
I have a problem when I startup the WBI Message Broker v5.0 broker. I have the following three errors in the syslog:
BIP2275E: Database record associated with message flow '58dcc7f7-1301-0000-0080-8ad3d786f011' is not valid. : DOF1SBK.e4cc00df-1301-0000-0080-e4f1ff79c5e7: /build/S500_P/src/DataFlowEngine/ImbDataFlowDirector.cpp: 2357: ImbDataFlowDirector::loadAllDataFlowsFromDatabase: ExecutionGroup: e4cc00df-1301-0000-0080-e4f1ff79c5e7
BIP5009E: XML Parsing Errors have occurred. : DOF1SBK.e4cc00df-1301-0000-0080-e4f1ff79c5e7: /build/S500_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 464: XmlImbParser::parseRightSibling: :
BIP5004E: XML parsing error (An exception occurred! Type:UnexpectedEOFException, Message:The end of input was not expected) encountered on line 27289 column 22 while parsing element MessageFlow. : DOF1SBK.e4cc00df-1301-0000-0080-e4f1ff79c5e7: /build/S500_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.cpp: 815: XmlBrokerAsgardParser::error: :
After broker restarting, my workflow in my execution group is stopped and I necessary must delete and deploy it again.
Are any of you willing to help me? Thanks a lot. |
|
| Back to top |
|
 |
| tosaurav |
| Posted: Tue Jul 24, 2007 11:46 am Post subject: |
|
|
Acolyte
Joined: 16 Jan 2007
Posts: 62
|
|
| Back to top |
|
|
| jius |
| Posted: Tue Jul 24, 2007 11:40 pm Post subject: |
|
|
Newbie
Joined: 24 Jul 2007
Posts: 2
|
Hi tosaurav. Thanks for link.
I have alredy seen the technote on IBM support site but I have a different problem on BIP5004E:
XML parsing error (An exception occurred! Type:UnexpectedEOFException, Message:The end of input was not expected) encountered on line 27289 column 22 while parsing element MessageFlow.....bla.bla.bla....
What about this exception: "...The end of input was not expected..." ?
What does it mean? |
|
| Back to top |
|
|
| Degliesp |
| Posted: Wed Sep 05, 2007 7:56 am Post subject: |
|
|
Newbie
Joined: 15 Jan 2007
Posts: 5
|
| I have the same error in my environment. Could you please tell me if in your flow there are node names containing spaces or special characters? My env is WBIMB v5.0.6 with Sybase as broker db. |
|
| Back to top |
|
|
| joe.l3 |
| Posted: Wed Sep 05, 2007 9:14 am Post subject: |
|
|
Novice
Joined: 24 Jul 2007
Posts: 20
Location: ITALY
|
Hi Degliesp,
I think that your problem does not interest spaces or special character because I have developed many message flows with nodes containing spaces in label name. Rather, your issue regards BIP5004E.
You must take a look to the xml document processed by your message flow. For example, if you have the following log
| Quote: |
| BIP5004E: XML parsing error (An exception occurred! Type:UnexpectedEOFException, Message:The end of input was not expected) encountered on line 27936 column 95 while parsing element MessageFlow. : YOURBROKER.blablablablablablabla: /build/S500_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.cpp: 815: XmlBrokerAsgardParser::error: : |
You must examine the xml document and take a look to "line 27936 column 95" because there is an unexpected end of input. |
|
| Back to top |
|
|
| Degliesp |
| Posted: Wed Sep 05, 2007 11:22 pm Post subject: |
|
|
Newbie
Joined: 15 Jan 2007
Posts: 5
|
could you tell me were to find the xml document that describes the Message Flow? Infact I have this message when the broker starts and no application messages are in the input queue for the flow.
So I think that this XML is referred to the description of the Flow saved in the broker db but I don't know ho to find it. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 06, 2007 12:57 am Post subject: There were issues with spaces in V5 |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
A few years ago I was doing a port of a V2.1 system to V5 CSD4 and I found that I ran into all sorts of issues with procedure/functions names in ESQL that contained spaces.
When I replaced them with '_' characters thins behaved more sensibly.
As a result, I just use the '_' character instead of a space to this day.
I know that these problems have been resolved but as an old school programmer, I just hate spaces in file names etc. The handling of names with spaces on different platforms is very different. If you avoid them you don't run into these issues. Just one less item to trip you up when you are least expecting it to.
Stephen D
_________________
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. |
|
| Back to top |
|
|
| joe.l3 |
| Posted: Mon Sep 24, 2007 2:22 am Post subject: |
|
|
Novice
Joined: 24 Jul 2007
Posts: 20
Location: ITALY
|
Hi guys,
I want to help you in this topic because I have solved the same problem!!!
I remember you my problem:
(WBI v.5 - Sybase Broker DB)
I don't insert any file in my InputQueue but BIP2275E-BIP5009E-BIP5004E occurs when I restart my broker. My messageflow is stopped and I must delete it and re-deploy it to my execution group.
The problem affects the connection to Broker DataBase. Infact the message flow can be read from the database and re-instantiated without having to be re-deployed. But on broker re-start, the copy of my message flow definition read from the database is not good (not well formed XML) and hence the BIP2275E errors. So the broker is unable to instantiate the message flow. This problem comes from Sybase driver ODBC which makes a truncation of insert records. ODBC ini file sets a default text size at 1MB. So when I restart my broker the xml file of my message flow (grater then 1Mb) is cropped and a XML parsing error occurs (BIP5004E..Message:The end of input was not expected...).
To solve this problem I have modified ODBC.ini adding a new parameter: DefaultLongDataBuffLen=MyNewBufferLenght
| Quote: |
[MYBROKER]
Driver=/opt/wmqi/merant/lib/UKase18.so
Description=Sybase11
Database=MYBROKERDB
ServerName=MYSERVERNAME
NetworkAddress=MYSERVERIP,MYPORT
DefaultLongDataBuffLen=MyNewBufferLenght |
Now on broker re-start, my message flow is correctly read from Sybase Broker DB so there is no need to cancel and re-deploy it.
HI ALL |
|
| Back to top |
|
|
|
|
