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
David Delač
2-6-19
Hello Aldevinas,

This is very difficult to debug like this but there is few things that I would like to know:
- what is the difference between the test system and client's system?
- when did this start happening and did it work properly before? Have you made any modifications to the system that might cause such behaviour?
- have you tried comparing XML before and after "XML pretty print command" was used?

Best regards,
David D.
HansaWorld Support
Aldevinas Katkus
2-8-19
Created byDavid Delač17:05 6 Feb 2019
Hello Aldevinas, This is very difficult to debug like this but there is few things that I would like to know: - what is the difference between the test system and client's system? - when did this start happening and did it work properly before? Have you
Today we had it again. After the first failure (this has been done by our customer) I have tried to import the same xml file without "prettyfying" it and it crashed the server and the node with all the servers on that node.
Client system is on the Hansaworld cloud and our system is on our dedicated server (linux)
It works a few days normally, then it crashes some day.
XML is the same, pretty print just splits one long line into shorter lines. As I said xml is OK (no syntax errors).
Today xml was even smaller (some 5100 chars in one and the only line).
We use the same hal as the client for importing bank statements.
Aldevinas Katkus
2-11-19
Today it crashed again. I can see some strange lines in the log an hour before importing:
2019-02-11 06:57:49 RT --------------------- backtrace end --------------------------
2019-02-11 06:57:49 RT 25: hansa-autoserver-37018218() [0x406bc1]
2019-02-11 06:57:49 RT 24: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f00426ac830]
2019-02-11 06:57:49 RT 23: hansa-autoserver-37018218() [0x406b24]
Aldevinas Katkus
2-22-19
well we have checked on customer's premises and it did not crash both in single user and client -server mode with the same files which caused the server in the cloud to crash. Cloud issue?
David Delač
1-9-20
Hello Aldevinas,

Have you managed to resolve your issue?

Best Regards,
David D.
Aldevinas Katkus
7-4-22
Today we had the same accident with same customer. Version 2021-01-13. We have to do a Force Stop Server in order to restart the server. Customer imported on xml file (Swedbank), then tried to import another one (SEB) and the server crashed.
The same "too large or too small malloc" error occured.
7-12-22
Created byAldevinas Katkus15:37 4 July 2022
Today we had the same accident with same customer. Version 2021-01-13. We have to do a Force Stop Server in order to restart the server. Customer imported on xml file (Swedbank), then tried to import another one (SEB) and the server crashed. The same "to
Hi Aldevinas

Did you manage to resolve this issue?
Aldevinas Katkus
7-12-22
I left the issue "as is", because I cannot replicate it on my test system with the same version, same hals, same xml import file, in single user and client-server mode.

Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
David Delač
Hi Piotr, The log entry:
2024-12-14 08:40:43 0.000 CallHal(IsHansaWorldCustomer) appears because the server is running with the verbosity=debug-detailed setting in its parameters.txt file. Thi...
09:43 16 Dec 2024
Brittany McGrath
Hi Vaughn, I can confirm this has been fixed now and is live in Standard ERP 2024-11-20 Version: 85556786. Thank you. ...
10:04 10 Dec 2024