crash during xml file import
Aldevinas Katkus
2-4-19
Has anyone faced with this?
Our client is importing Swedbank statements (xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02") and occasionally it crashes the server with the following log lines in the server. There is nothing interesting in the log of the client.
I can see the bank statement is as one line with no line breaks, neither CR nor LF (8750 chars in one line). On my test system it does not crash, on the client's system it crashes. I made the xml file "more beautiful" with xml pretty print command in the notepad++ and it imports successfully on the clients system.

XML itself does not have any problems, even though "xml problem: expected >" line in the log says it has.

Any suggestions?


version 8.4 2018-07-26 (build 84192014)

2019-02-04 07:50:04 Last session was not properly terminated
2019-02-04 07:50:04 *** Using LRU Replacement ***
2019-02-04 07:50:04 *** running with new mail receiving and parsing ***
2019-02-04 07:50:04 16384 hash table entries added
2019-02-04 07:50:04 20547 cache sectors added
2019-02-04 07:35:03 VM too large or too small malloc 536870904
2019-02-04 07:33:24 VM xml problem: expected >
2019-02-04 07:33:24 VM xml problem: expected >
2019-02-04 07:33:24 VM Database set to unsafe (import and maintenance) mode
2019-02-04 07:32:08 VM/THREAD(16) SendWebRequest 169.51.66.84 443 /HTSCreateHansaWorldID.hal CallCreateHansaWorldID_Reply res = false
2019-02-04 07:32:08 VM/THREAD(17) SendWebRequest 169.50.37.57 443 /HTSRegisterPresence.hal HTSPresenceLoginReply res = false

2019-02-04 07:32:07 VM Login @192.168.0.18
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Bror-Erik Kotiranta
Clients have their own cache, and then the server has the shared cache, if you want it kind of black and white. Presense should be there as far as i know...
10:55 7 July 2025
Yavuz Yigiterhan
Hello Paul, That is something only HansaWorld can do. But that would help to understand is that causing the problem and - if so - we fix the issue. Additional information is appreciated. Yavuz...
10:45 7 July 2025