[ https://issues.apache.org/jira/browse/FELIX-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned FELIX-6298: --------------------------------------- Assignee: Carsten Ziegeler > ipojo ServiceRegistry concurrency > --------------------------------- > > Key: FELIX-6298 > URL: https://issues.apache.org/jira/browse/FELIX-6298 > Project: Felix > Issue Type: Bug > Reporter: Alexander Shaklein > Assignee: Carsten Ziegeler > Priority: Major > Fix For: healthcheck.core 2.0.16 > > > Hello. > During source code analyzing i've found some issues. > For example class org.apache.felix.ipojo.context.ServiceRegistry: > {code:java} > synchronized (m_regs) { > ServiceRegistrationImpl reg = new ServiceRegistrationImpl(this, instance, > new String[] { clazz }, new Long(m_serviceId++), svcObj, dict); > m_regs.add(reg); > fireServiceChanged(new ServiceEvent(ServiceEvent.REGISTERED, > reg.getReference())); > return reg; > } > {code} > Is not good cause: > * may result deadlock > * too complex code in synchronized > So the question is - should i contribute some fixes in PR. Are you interested? > [https://github.com/apache/felix-dev/pull/34] -- This message was sent by Atlassian Jira (v8.20.10#820010)