From java we launch LO under Headless mode(socket connection with 5instance of LO) and concurrent request made to convert odt to doc, XOutputStream used to output doc resulted in document mixup.
Concurrent request to convert odt to doc, XOutputStream used to write DOC result in document mixup.
I have A.odt and B.odt and converting it to A.doc and B.doc respectively.
Either A.doc contains the content of B.odt or B.doc contains the content of A.odt.
This happens very randomly not always.
Steps to reproduce:
1. launch LO under headless mode(5 instance socket connection )from java
2. Make 100 concurrent request to convert documents every document has different contents.
3. Verify the conversion(randomly documents are mixed up)
Dont use XOutputStream wrapper to store file, Save the converted file to local file, and use standard java api to write to the java outputstrem
This issue is reproducible in all versions of LO 3.x and 4.x
Operating System: Windows 7
Version: 184.108.40.206 release
Hi Ranjeeth -
First: Thanks so much for reporting the issue
Second: Is there any way that you can get us a test kit for this? it's hard for us to reproduce bugs that require us to do something like "100 concurrent requests"
So what would be ideal is if you could provide a zip file with 100 files (simple files if possible) along with a script of some kind to run the 100 concurrent requests.
Lastly, when reporting a bug please always describe each step completely - assume that the bug reader knows nothing about what you're talking about. In this case - "launch LO under headless mode(5 instance socket connection )from java" is pretty advanced - if you could explain this further as to how we can do it, that'd be great.
Apologies for the long delay (we're catching up on a back log of bugs). Marking this as NEEDINFO - if you could provide at least clearer repro steps and if at all possible a test kit, that would be great. Then please mark the bug as UNCONFIRMED. Thanks!
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This NEEDINFO message was generated on: 2015-09-03
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-10-14