[
https://issues.apache.org/jira/browse/FELIX-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161993#comment-17161993
]
Veselin commented on FELIX-6308:
--------------------------------
Hi, thanks for the quick response. Yes I'm calling update(). I looked a bit in
the sourcecode of config admin and saw that there are other methods calling
FilePersistenceManager._store() then the one in the stacktrace.
Could my code at all cause this exception or does Felix serialize the access to
the file and protect it from parallel access?
What other potential reasons do you mean that can lead to a bad file descriptor?
> 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)
