[
https://issues.apache.org/jira/browse/FELIX-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162000#comment-17162000
]
Carsten Ziegeler commented on FELIX-6308:
-----------------------------------------
I think another reason is that the output stream gets closed too early - not
sure there might be other reasons.
Looking at the code, it writes a tmp file first, so even if that part is called
concurrently, the files should be unique.
> Bad File Descriptor while persisting service configuration
> ----------------------------------------------------------
>
> Key: FELIX-6308
> URL: https://issues.apache.org/jira/browse/FELIX-6308
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.9.16
> Reporter: Veselin
> Priority: Major
> Attachments: stacktrace.txt
>
>
> I got un unusual exception while flushing some configuration by calling
> ConfigurationAdapter.update() : java.io.IOException: Bad file descriptor. As
> I understood the exception this can happen in multithreading environment if
> the ouput stream is closed.
>
> Is update() threadsafe?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
