[OSGI] SLSB Business Interfaces registered multiple times as Services

[ekke]

just noticed a strange thing,
while tracking services I noticed, that Services for SLSB are registered
more then one time.

think your loop is wrong

it goes this way:

ALocal
ARemote
ALocal
ARemote
BLocal
BRemote
ALocal
ARemote
BLocal
BRemote
CLocal
CRemoteALocal
ARemote
BLocal
BRemote
CLocal
CRemote
DLocal
DRemote

and so on...
my service.id is > 80.000 ;-)

should I report this as bug ?

ekke
(using 1.1.0 snapshot 2008_07_23)

[Guillaume Sauthier]

Yes, that's strange
Business interfaces should be registered only when the ejbjar is started.
Notice that all the business interfaces of the bean are registered, so
if you have multiples local or remote interfaces, it ends up with
multiple registration.
Are your beans reusing the interfaces? so it's normal that they gets
registered multiple times ...

--G

ekke a écrit :

> just noticed a strange thing,
> while tracking services I noticed, that Services for SLSB are
> registered more then one time.
>
> think your loop is wrong
>
> it goes this way:
>
> ALocal
> ARemote
> ALocal
> ARemote
> BLocal
> BRemote
> ALocal
> ARemote
> BLocal
> BRemote
> CLocal
> CRemoteALocal
> ARemote
> BLocal
> BRemote
> CLocal
> CRemote
> DLocal
> DRemote
>
> and so on...
> my service.id is > 80.000 ;-)
>
> should I report this as bug ?
>
> ekke
> (using 1.1.0 snapshot 2008_07_23)
>
>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume,

Bean A has @Local and @Remote
so there should be 2 registered services for this bean:
one for the local and one for the remote

but if I have Beans A,B,C,D then there should be 8 services,
buit there are 20:
8 for A
6 for B
4 for C
2 for D

and if I list the services from OSGI console I see (looking at the id)
that they are registered like the list below

so I think there must be something wrong

I think you have testcases with more then one bean to see if the
services are registered, but perhaps you only test if there's a service
found for the remote or local interface and not how many exist ?

ekke

Guillaume Sauthier schrieb:

> Yes, that's strange
> Business interfaces should be registered only when the ejbjar is started.
> Notice that all the business interfaces of the bean are registered, so
> if you have multiples local or remote interfaces, it ends up with
> multiple registration.
> Are your beans reusing the interfaces? so it's normal that they gets
> registered multiple times ...
>
> --G
>
> ekke a écrit :
>> just noticed a strange thing,
>> while tracking services I noticed, that Services for SLSB are
>> registered more then one time.
>>
>> think your loop is wrong
>>
>> it goes this way:
>>
>> ALocal
>> ARemote
>> ALocal
>> ARemote
>> BLocal
>> BRemote
>> ALocal
>> ARemote
>> BLocal
>> BRemote
>> CLocal
>> CRemoteALocal
>> ARemote
>> BLocal
>> BRemote
>> CLocal
>> CRemote
>> DLocal
>> DRemote
>>
>> and so on...
>> my service.id is > 80.000 ;-)
>>
>> should I report this as bug ?
>>
>> ekke
>> (using 1.1.0 snapshot 2008_07_23)
>>
>>
>>
>

[Guillaume Sauthier]

ekke a écrit :

> Guillaume,
>
> Bean A has @Local and @Remote
> so there should be 2 registered services for this bean:
> one for the local and one for the remote
>
> but if I have Beans A,B,C,D then there should be 8 services,
> buit there are 20:
> 8 for A
> 6 for B
> 4 for C
> 2 for D
>
> and if I list the services from OSGI console I see (looking at the id)
> that they are registered like the list below

In this order ?
Or is D started first, and then C, then B and finally A ?

After a little digging in our code ,I've seen something wrong, but it
does not explains the behavior at first glance...
In EZB, we have the concept of BindingFactory, that manage how we
publishes business interfaces of the beans.
So there is a default one, that manages JNDI. And for OSGi, we added an
OSGiBindingFactory. This is that class that register/unregister services
for your bean's interfaces.
This factory is added in a singleton BindingManager.
It's added during the core component startup, but it's never removed.
You see where I wanna go ?
if you start multiple cores, the OSGiBindingFactory will be registered
multiple times, with the effect of adding 2 more services (1 for @Local
1 for @Remote) for each of your beans ...

So the question is: "Do you start multiple cores ?"

Cheers
--Guillaume

>
> so I think there must be something wrong
>
> I think you have testcases with more then one bean to see if the
> services are registered, but perhaps you only test if there's a service
> found for the remote or local interface and not how many exist ?
>
> ekke
>
> Guillaume Sauthier schrieb:
>> Yes, that's strange
>> Business interfaces should be registered only when the ejbjar is
>> started.
>> Notice that all the business interfaces of the bean are registered,
>> so if you have multiples local or remote interfaces, it ends up with
>> multiple registration.
>> Are your beans reusing the interfaces? so it's normal that they gets
>> registered multiple times ...
>>
>> --G
>>
>> ekke a écrit :
>>> just noticed a strange thing,
>>> while tracking services I noticed, that Services for SLSB are
>>> registered more then one time.
>>>
>>> think your loop is wrong
>>>
>>> it goes this way:
>>>
>>> ALocal
>>> ARemote
>>> ALocal
>>> ARemote
>>> BLocal
>>> BRemote
>>> ALocal
>>> ARemote
>>> BLocal
>>> BRemote
>>> CLocal
>>> CRemoteALocal
>>> ARemote
>>> BLocal
>>> BRemote
>>> CLocal
>>> CRemote
>>> DLocal
>>> DRemote
>>>
>>> and so on...
>>> my service.id is > 80.000 ;-)
>>>
>>> should I report this as bug ?
>>>
>>> ekke
>>> (using 1.1.0 snapshot 2008_07_23)
>>>
>>>
>>>
>>
>
>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:

> ekke a écrit :
>> Guillaume,
>>
>> Bean A has @Local and @Remote
>> so there should be 2 registered services for this bean:
>> one for the local and one for the remote
>>
>> but if I have Beans A,B,C,D then there should be 8 services,
>> buit there are 20:
>> 8 for A
>> 6 for B
>> 4 for C
>> 2 for D
>>
>> and if I list the services from OSGI console I see (looking at the id)
>> that they are registered like the list below
>
> In this order ?
> Or is D started first, and then C, then B and finally A ?

see my other example I just sent before

>
> After a little digging in our code ,I've seen something wrong, but it
> does not explains the behavior at first glance...
> In EZB, we have the concept of BindingFactory, that manage how we
> publishes business interfaces of the beans.
> So there is a default one, that manages JNDI. And for OSGi, we added an
> OSGiBindingFactory. This is that class that register/unregister services
> for your bean's interfaces.
> This factory is added in a singleton BindingManager.
> It's added during the core component startup, but it's never removed.
> You see where I wanna go ?
> if you start multiple cores, the OSGiBindingFactory will be registered
> multiple times, with the effect of adding 2 more services (1 for @Local
> 1 for @Remote) for each of your beans ...
>
> So the question is: "Do you start multiple cores ?"
>

no, there's only one easybeans.core

I'm using the EasyBeans agent to start all Easybeans components
and I'm only waitong until all components are registered,
then I wait until all datasources are available
then I start my EJB bundle (containing SLSB and Interfaces in one bundle,
also containing persistence.xml)

ekke

[Guillaume Sauthier]

ekke a écrit :

> Guillaume Sauthier schrieb:
>> ekke a écrit :
>>> Guillaume,
>>>
>>> Bean A has @Local and @Remote
>>> so there should be 2 registered services for this bean:
>>> one for the local and one for the remote
>>>
>>> but if I have Beans A,B,C,D then there should be 8 services,
>>> buit there are 20:
>>> 8 for A
>>> 6 for B
>>> 4 for C
>>> 2 for D
>>>
>>> and if I list the services from OSGI console I see (looking at the id)
>>> that they are registered like the list below
>>
>> In this order ?
>> Or is D started first, and then C, then B and finally A ?
>
> see my other example I just sent before
>
>>
>> After a little digging in our code ,I've seen something wrong, but it
>> does not explains the behavior at first glance...
>> In EZB, we have the concept of BindingFactory, that manage how we
>> publishes business interfaces of the beans.
>> So there is a default one, that manages JNDI. And for OSGi, we added
>> an OSGiBindingFactory. This is that class that register/unregister
>> services for your bean's interfaces.
>> This factory is added in a singleton BindingManager.
>> It's added during the core component startup, but it's never removed.
>> You see where I wanna go ?
>> if you start multiple cores, the OSGiBindingFactory will be
>> registered multiple times, with the effect of adding 2 more services
>> (1 for @Local 1 for @Remote) for each of your beans ...
>>
>> So the question is: "Do you start multiple cores ?"
>>
> no, there's only one easybeans.core
>
> I'm using the EasyBeans agent to start all Easybeans components

The agent delete the existing configuration for all the old component's
Configurationµ.
It doesn't do that for the core...
Hmmm, it still doesn't explains that "incremental" behavior...
Can you check that there is no multiple EZBCoreService instances
registered ?
--G

> and I'm only waitong until all components are registered,
> then I wait until all datasources are available
> then I start my EJB bundle (containing SLSB and Interfaces in one bundle,
> also containing persistence.xml)
>
> ekke
>
>
>


[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:

> Can you check that there is no multiple EZBCoreService instances
> registered ?

did some things perhaps some information to you ?

starting all up - there's only one time:

(I) EZBCoreService.activate : Activating EasyBeans/OSGi/Core

here's what happened after shutdown:

I found also only one entry

11.08.08 11:06:17 (I) EZBCoreService.deactivate : Deactivating
EasyBeans/OSGi/Core

hope it helps

ekke

osgi> shutdown
11.08.08 11:06:17 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-jdbcpool_1.1.0-SNAPSHOT.jar/ [37]
11.08.08 11:06:17 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jdbcpool.JDBCPoolComponent2.
11.08.08 11:06:17 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jdbcpool.jdbcpoolcomponent-1218444097014-12 deleted
11.08.08 11:06:17 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jdbcpool.JDBCPoolComponent.
11.08.08 11:06:17 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jdbcpool.jdbcpoolcomponent-1218444097000-4 deleted
11.08.08 11:06:17 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jdbcpool.JDBCPoolComponent23.
11.08.08 11:06:17 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jdbcpool.jdbcpoolcomponent-1218444097010-10 deleted
11.08.08 11:06:17 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jdbcpool.JDBCPoolComponent2345.
11.08.08 11:06:17 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jdbcpool.jdbcpoolcomponent-1218444097004-6 deleted
11.08.08 11:06:17 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jdbcpool.JDBCPoolComponent234.
11.08.08 11:06:17 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jdbcpool.jdbcpoolcomponent-1218444097007-8 deleted
11.08.08 11:06:17 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-joram_1.1.0-SNAPSHOT.jar/ [12]
11.08.08 11:06:17 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-core_1.1.0-SNAPSHOT.jar/ [18]
11.08.08 11:06:17 (I) EZBCoreService.deactivate : Deactivating EasyBeans/OSGi/Core
11.08.08 11:06:18 (I) Embedded.removeContainer : Container 'org.ekkehard.abc.dataManager' removed
11.08.08 11:06:18 (I) Embedded.removeContainer : Container 'org.ekkehard.bb.dataManager' removed
11.08.08 11:06:18 (I) Embedded.removeContainer : Container 'org.ekkehard.ies.dataManager' removed
11.08.08 11:06:18 (I) Embedded.removeContainer : Container 'org.ekkehard.foo.dataManager' removed
11.08.08 11:06:18 (I) Embedded.removeContainer : Container 'org.ekkehard.sample.dataManager' removed
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.carol.CarolComponent.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.jotm.JOTMComponent.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.quartz.QuartzComponent.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.hsqldb.HSQLDBComponent.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.hsqldb.HSQLDBComponent2.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.hsqldb.HSQLDBComponent23.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.hsqldb.HSQLDBComponent234.
11.08.08 11:06:18 (I) ComponentRegistry.unregister : Unregistering component with name org.ow2.easybeans.component.hsqldb.HSQLDBComponent2345.
Mon Aug 11 11:06:18 CEST 2008 DEBUG [Thread-4] org.eclipse.riena.security.common.authorization.RienaPolicy rienapolicy: domain: getPermissions domain=file:/Volumes/ekkes_daten/Dev/_run/e34target/riena/plugins/org.eclipse.riena.security.common_1.0.0.M3.jar
11.08.08 11:06:18 (I) Embedded.stop : EasyBeans '1.1.0-SNAPSHOT' is now stopped.
11.08.08 11:06:18 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-hsqldb_1.1.0-SNAPSHOT.jar/ [19]
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.hsqldb.hsqldbcomponent-1218444097002-5 deleted
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.hsqldb.hsqldbcomponent-1218444097005-7 deleted
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.hsqldb.hsqldbcomponent-1218444097011-11 deleted
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.hsqldb.hsqldbcomponent-1218444097008-9 deleted
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.hsqldb.hsqldbcomponent-1218444096999-3 deleted
11.08.08 11:06:18 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-quartz_1.1.0-SNAPSHOT.jar/ [53]
11:06:18,480  INFO QuartzScheduler:542 - Scheduler EasyBeans_$_NON_CLUSTERED shutting down.
11:06:18,481  INFO QuartzScheduler:470 - Scheduler EasyBeans_$_NON_CLUSTERED paused.
11:06:18,486  INFO QuartzScheduler:592 - Scheduler EasyBeans_$_NON_CLUSTERED shutdown complete.
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.quartz.quartzcomponent-1218444096979-0 deleted
11.08.08 11:06:18 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-jotm_1.1.0-SNAPSHOT.jar/ [51]
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.jotm.jotmcomponent-1218444096998-2 deleted
11.08.08 11:06:18 (I) Activator.stop : Stopping Bundle initial@reference:file:../../easyBeans/bundles/easybeans-component-carol_1.1.0-SNAPSHOT.jar/ [7]
11.08.08 11:06:18 (I) CarolComponent.stop : Carol Component Stopped
11.08.08 11:06:18 (I) EZBComponentServiceFactory.deleted : Component with pid org.ow2.easybeans.component.carol.carolcomponent-1218444096996-1 deleted
Mon Aug 11 11:06:18 CEST 2008 INFO [Thread-4] org.eclipse.riena.internal.communication.factory.hessian.Activator stop hessian support on client
11:06:18,591  INFO Activator:42 - stop hessian support on client
2008.08.11 11:06:18 CEST ekke@MacProEkke INFO [OSGi Console] org.eclipse.riena.internal.communication.publisher.hessian.Activator stop hessian support on server
11:06:25,770  INFO ThreadedServer:659 - Stopping Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
11:06:25,871  INFO SocketListener:213 - Stopped SocketListener on 0.0.0.0:8080
11:06:25,872  INFO Container:166 - Stopped org.eclipse.equinox.http.jetty.internal.Servlet25Handler@1d57c7
11:06:25,872  INFO Container:166 - Stopped HttpContext[/,/]
11:06:25,873  INFO Container:166 - Stopped org.mortbay.http.HttpServer@c39d09

[Guillaume Sauthier]

Hmmm, I still do not see what is going wrong.
The only thing that could register mulitple OSGiBF is multiple start()
of the EZBCoreService (or multiple easybeans-core bundles being activated).

I'm adding a testcase to see if I can reproduce the problem here.
I let you know the result ...
--G


ekke a écrit :

> Guillaume Sauthier schrieb:
>
>> Can you check that there is no multiple EZBCoreService instances
>> registered ?
>
> did some things perhaps some information to you ?
>
> starting all up - there's only one time:
>
> (I) EZBCoreService.activate : Activating EasyBeans/OSGi/Core
>
> here's what happened after shutdown:
>
> I found also only one entry
>
> 11.08.08 11:06:17 (I) EZBCoreService.deactivate : Deactivating
> EasyBeans/OSGi/Core
>
> hope it helps
>
> ekke

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:
> Hmmm, I still do not see what is going wrong.
> The only thing that could register mulitple OSGiBF is multiple start()
> of the EZBCoreService (or multiple easybeans-core bundles being activated).
>
> I'm adding a testcase to see if I can reproduce the problem here.
> I let you know the result ...

thanbks

ekke

[Guillaume Sauthier]

I can reproduce the problem here with our test suite:

org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times

.... some time passed ....

OK, I think I got it.
the problem was not in easybeans-osgi after all :)
It's directly in easybeans, we manage, at the EjbJarContainer level, a
list of BindingReference (used to bind object in JNDI or register them
as services).
During the container startup, we collect a list of BindingRef (using
@Local, @Remote + EJB2.x style interfaces), BUT, the usage of theses
references is done at the bean level, so it ends up with the list binded
for the first bean (1 reference in the list), then it is binded again
for the 2nd EJB (now we have 2 interfaces in the list)... So, the first
bean interface/reference is binded, rebinded and re-re-binded ...

I should be able to make a fix quickly
--G

ekke a écrit :

> Guillaume Sauthier schrieb:
>> Hmmm, I still do not see what is going wrong.
>> The only thing that could register mulitple OSGiBF is multiple
>> start() of the EZBCoreService (or multiple easybeans-core bundles
>> being activated).
>>
>> I'm adding a testcase to see if I can reproduce the problem here.
>> I let you know the result ...
>
> thanbks
>
> ekke
>
>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[Guillaume Sauthier]

Should be fixed now

Ekke, once the SNAPSHOT have been deployed and published (tomorow
morning should be OK) in the m2 repository of OW2, could you check that
the problem is fixed ?
If so, tell me so, and I will close the JIRA.

Cheers
--Guillaume

Guillaume Sauthier a écrit :

> I can reproduce the problem here with our test suite:
>
> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>
> .... some time passed ....
>
> OK, I think I got it.
> the problem was not in easybeans-osgi after all :)
> It's directly in easybeans, we manage, at the EjbJarContainer level, a
> list of BindingReference (used to bind object in JNDI or register them
> as services).
> During the container startup, we collect a list of BindingRef (using
> @Local, @Remote + EJB2.x style interfaces), BUT, the usage of theses
> references is done at the bean level, so it ends up with the list
> binded for the first bean (1 reference in the list), then it is binded
> again for the 2nd EJB (now we have 2 interfaces in the list)... So,
> the first bean interface/reference is binded, rebinded and
> re-re-binded ...
>
> I should be able to make a fix quickly
> --G
>
> ekke a écrit :
>> Guillaume Sauthier schrieb:
>>> Hmmm, I still do not see what is going wrong.
>>> The only thing that could register mulitple OSGiBF is multiple
>>> start() of the EZBCoreService (or multiple easybeans-core bundles
>>> being activated).
>>>
>>> I'm adding a testcase to see if I can reproduce the problem here.
>>> I let you know the result ...
>>
>> thanbks
>>
>> ekke
>>
>>
>>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:
> Should be fixed now
>

GREAT !

> Ekke, once the SNAPSHOT have been deployed and published (tomorow
> morning should be OK) in the m2 repository of OW2, could you check that
> the problem is fixed ?

of course :-)

> If so, tell me so, and I will close the JIRA.
>

thx for soon fixing

btw: now I've seen that registering 80000+ services is no problem for
equinox ;-)

ekke

[Brice Ruzand]

Is it possible to have this fix in EZB 1.0.x too ?

Thx

Brice

Guillaume Sauthier a écrit :

> Should be fixed now
>
> Ekke, once the SNAPSHOT have been deployed and published (tomorow
> morning should be OK) in the m2 repository of OW2, could you check
> that the problem is fixed ?
> If so, tell me so, and I will close the JIRA.
>
> Cheers
> --Guillaume
>
> Guillaume Sauthier a écrit :
>> I can reproduce the problem here with our test suite:
>>
>> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
>> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>>
>> .... some time passed ....
>>
>> OK, I think I got it.
>> the problem was not in easybeans-osgi after all :)
>> It's directly in easybeans, we manage, at the EjbJarContainer level,
>> a list of BindingReference (used to bind object in JNDI or register
>> them as services).
>> During the container startup, we collect a list of BindingRef (using
>> @Local, @Remote + EJB2.x style interfaces), BUT, the usage of theses
>> references is done at the bean level, so it ends up with the list
>> binded for the first bean (1 reference in the list), then it is
>> binded again for the 2nd EJB (now we have 2 interfaces in the
>> list)... So, the first bean interface/reference is binded, rebinded
>> and re-re-binded ...
>>
>> I should be able to make a fix quickly
>> --G
>>
>> ekke a écrit :
>>> Guillaume Sauthier schrieb:
>>>> Hmmm, I still do not see what is going wrong.
>>>> The only thing that could register mulitple OSGiBF is multiple
>>>> start() of the EZBCoreService (or multiple easybeans-core bundles
>>>> being activated).
>>>>
>>>> I'm adding a testcase to see if I can reproduce the problem here.
>>>> I let you know the result ...
>>>
>>> thanbks
>>>
>>> ekke
>>>
>>>
>>>
>>
>

--

Brice Ruzand
Bull, Architect of an Open World TM
http://www.bull.com
01 49 45 50 16

[Guillaume Sauthier]

Hi Brice

AFAIKT, for classic usage of EZB (only RMI & JNDI), this bug is not a
blocker (otherwise you told me so :) ).
At least, you can add a comment and an "affect version" explaining that
this problem is also in 1.0.x
Are you using the BindingFactory mechanism too ?
--G

Note: Now, it's sure, the SNAPSHOT have been deployed, you can give it a
try ekke

Brice Ruzand a écrit :

> Is it possible to have this fix in EZB 1.0.x too ?
>
> Thx
>
> Brice
>
> Guillaume Sauthier a écrit :
>> Should be fixed now
>>
>> Ekke, once the SNAPSHOT have been deployed and published (tomorow
>> morning should be OK) in the m2 repository of OW2, could you check
>> that the problem is fixed ?
>> If so, tell me so, and I will close the JIRA.
>>
>> Cheers
>> --Guillaume
>>
>> Guillaume Sauthier a écrit :
>>> I can reproduce the problem here with our test suite:
>>>
>>> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
>>> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>>>
>>> .... some time passed ....
>>>
>>> OK, I think I got it.
>>> the problem was not in easybeans-osgi after all :)
>>> It's directly in easybeans, we manage, at the EjbJarContainer level,
>>> a list of BindingReference (used to bind object in JNDI or register
>>> them as services).
>>> During the container startup, we collect a list of BindingRef (using
>>> @Local, @Remote + EJB2.x style interfaces), BUT, the usage of theses
>>> references is done at the bean level, so it ends up with the list
>>> binded for the first bean (1 reference in the list), then it is
>>> binded again for the 2nd EJB (now we have 2 interfaces in the
>>> list)... So, the first bean interface/reference is binded, rebinded
>>> and re-re-binded ...
>>>
>>> I should be able to make a fix quickly
>>> --G
>>>
>>> ekke a écrit :
>>>> Guillaume Sauthier schrieb:
>>>>> Hmmm, I still do not see what is going wrong.
>>>>> The only thing that could register mulitple OSGiBF is multiple
>>>>> start() of the EZBCoreService (or multiple easybeans-core bundles
>>>>> being activated).
>>>>>
>>>>> I'm adding a testcase to see if I can reproduce the problem here.
>>>>> I let you know the result ...
>>>>
>>>> thanbks
>>>>
>>>> ekke
>>>>
>>>>
>>>>
>>>
>>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[Brice Ruzand]

I thought it was the same thing, but may be not.
My ejb "PingFacade" has 2 interfaces (1 remote , 1 local) and I got the
following trace :

 WARN  [org.ow2.easybeans.resolver.ContainerJNDIResolver] Data already
set for
JNDIData[name=fr.mi.siv.mas.pac.ping.service.facade.PingFacade_fr.mi.siv.mas.pac.ping.service.PingService@Remote,
beanName=PingFacade] for the container URL
file:/SSIV/tmp/jonas/EasyBeans-Deployer-siv/EAR/siv-ear-all-1.6.ear/mas-pac-ejb-1.6.jar.

I don't think I am using the BindingFactory mechanism.
Nerver mind ;)

Brice

Guillaume Sauthier a écrit :

> Hi Brice
>
> AFAIKT, for classic usage of EZB (only RMI & JNDI), this bug is not a
> blocker (otherwise you told me so :) ).
> At least, you can add a comment and an "affect version" explaining
> that this problem is also in 1.0.x
> Are you using the BindingFactory mechanism too ?
> --G
>
> Note: Now, it's sure, the SNAPSHOT have been deployed, you can give it
> a try ekke
>
> Brice Ruzand a écrit :
>> Is it possible to have this fix in EZB 1.0.x too ?
>>
>> Thx
>>
>> Brice
>>
>> Guillaume Sauthier a écrit :
>>> Should be fixed now
>>>
>>> Ekke, once the SNAPSHOT have been deployed and published (tomorow
>>> morning should be OK) in the m2 repository of OW2, could you check
>>> that the problem is fixed ?
>>> If so, tell me so, and I will close the JIRA.
>>>
>>> Cheers
>>> --Guillaume
>>>
>>> Guillaume Sauthier a écrit :
>>>> I can reproduce the problem here with our test suite:
>>>>
>>>> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
>>>> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>>>>
>>>> .... some time passed ....
>>>>
>>>> OK, I think I got it.
>>>> the problem was not in easybeans-osgi after all :)
>>>> It's directly in easybeans, we manage, at the EjbJarContainer
>>>> level, a list of BindingReference (used to bind object in JNDI or
>>>> register them as services).
>>>> During the container startup, we collect a list of BindingRef
>>>> (using @Local, @Remote + EJB2.x style interfaces), BUT, the usage
>>>> of theses references is done at the bean level, so it ends up with
>>>> the list binded for the first bean (1 reference in the list), then
>>>> it is binded again for the 2nd EJB (now we have 2 interfaces in the
>>>> list)... So, the first bean interface/reference is binded, rebinded
>>>> and re-re-binded ...
>>>>
>>>> I should be able to make a fix quickly
>>>> --G
>>>>
>>>> ekke a écrit :
>>>>> Guillaume Sauthier schrieb:
>>>>>> Hmmm, I still do not see what is going wrong.
>>>>>> The only thing that could register mulitple OSGiBF is multiple
>>>>>> start() of the EZBCoreService (or multiple easybeans-core bundles
>>>>>> being activated).
>>>>>>
>>>>>> I'm adding a testcase to see if I can reproduce the problem here.
>>>>>> I let you know the result ...
>>>>>
>>>>> thanbks
>>>>>
>>>>> ekke
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

--

Brice Ruzand
Bull, Architect of an Open World TM
http://www.bull.com
01 49 45 50 16

[ekke]

Guillaume Sauthier schrieb:

> Note: Now, it's sure, the SNAPSHOT have been deployed, you can give it a
> try ekke
>

hmmm
just looked at
http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/osgi/ow2-easybeans-osgi/1.1.0-SNAPSHOT/

its still from 11-Aug-2008 13:46

ekke

[Guillaume Sauthier]

Brice Ruzand a écrit :

> I thought it was the same thing, but may be not.
> My ejb "PingFacade" has 2 interfaces (1 remote , 1 local) and I got
> the following trace :
>
> WARN  [org.ow2.easybeans.resolver.ContainerJNDIResolver] Data already
> set for
> JNDIData[name=fr.mi.siv.mas.pac.ping.service.facade.PingFacade_fr.mi.siv.mas.pac.ping.service.PingService@Remote,
> beanName=PingFacade] for the container URL
> file:/SSIV/tmp/jonas/EasyBeans-Deployer-siv/EAR/siv-ear-all-1.6.ear/mas-pac-ejb-1.6.jar.
>
>
> I don't think I am using the BindingFactory mechanism.
> Nerver mind ;)

Maybe that's another issue, I'm not really up to date with the
JNDIResolver stuff :)
To know, maybe you can make a try with latests EZB snapshots of version
1.1.0 ?

--G

>
> Brice
>
> Guillaume Sauthier a écrit :
>> Hi Brice
>>
>> AFAIKT, for classic usage of EZB (only RMI & JNDI), this bug is not a
>> blocker (otherwise you told me so :) ).
>> At least, you can add a comment and an "affect version" explaining
>> that this problem is also in 1.0.x
>> Are you using the BindingFactory mechanism too ?
>> --G
>>
>> Note: Now, it's sure, the SNAPSHOT have been deployed, you can give
>> it a try ekke
>>
>> Brice Ruzand a écrit :
>>> Is it possible to have this fix in EZB 1.0.x too ?
>>>
>>> Thx
>>>
>>> Brice
>>>
>>> Guillaume Sauthier a écrit :
>>>> Should be fixed now
>>>>
>>>> Ekke, once the SNAPSHOT have been deployed and published (tomorow
>>>> morning should be OK) in the m2 repository of OW2, could you check
>>>> that the problem is fixed ?
>>>> If so, tell me so, and I will close the JIRA.
>>>>
>>>> Cheers
>>>> --Guillaume
>>>>
>>>> Guillaume Sauthier a écrit :
>>>>> I can reproduce the problem here with our test suite:
>>>>>
>>>>> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
>>>>> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>>>>>
>>>>> .... some time passed ....
>>>>>
>>>>> OK, I think I got it.
>>>>> the problem was not in easybeans-osgi after all :)
>>>>> It's directly in easybeans, we manage, at the EjbJarContainer
>>>>> level, a list of BindingReference (used to bind object in JNDI or
>>>>> register them as services).
>>>>> During the container startup, we collect a list of BindingRef
>>>>> (using @Local, @Remote + EJB2.x style interfaces), BUT, the usage
>>>>> of theses references is done at the bean level, so it ends up with
>>>>> the list binded for the first bean (1 reference in the list), then
>>>>> it is binded again for the 2nd EJB (now we have 2 interfaces in
>>>>> the list)... So, the first bean interface/reference is binded,
>>>>> rebinded and re-re-binded ...
>>>>>
>>>>> I should be able to make a fix quickly
>>>>> --G
>>>>>
>>>>> ekke a écrit :
>>>>>> Guillaume Sauthier schrieb:
>>>>>>> Hmmm, I still do not see what is going wrong.
>>>>>>> The only thing that could register mulitple OSGiBF is multiple
>>>>>>> start() of the EZBCoreService (or multiple easybeans-core
>>>>>>> bundles being activated).
>>>>>>>
>>>>>>> I'm adding a testcase to see if I can reproduce the problem here.
>>>>>>> I let you know the result ...
>>>>>>
>>>>>> thanbks
>>>>>>
>>>>>> ekke
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[Guillaume Sauthier]

That's okay now:
http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/osgi/ow2-easybeans-osgi/1.1.0-SNAPSHOT/

--G

ekke a écrit :

> Guillaume Sauthier schrieb:
>
>> Note: Now, it's sure, the SNAPSHOT have been deployed, you can give
>> it a try ekke
>>
>
> hmmm
> just looked at
> http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/osgi/ow2-easybeans-osgi/1.1.0-SNAPSHOT/ 
>
>
> its still from 11-Aug-2008 13:46  
>
> ekke
>
>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:
> That's okay now:
> http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/osgi/ow2-easybeans-osgi/1.1.0-SNAPSHOT/ 
>
>
now its there
..I'll test it today

ekke

[Brice Ruzand]

I try the 1.1.0-SNAPSHOT version it does remove the
ContainerJNDIResolver trace.
But the deploy time has change from 71s to 26s on your heavier ear ;)
Brice

Guillaume Sauthier a écrit :

> Brice Ruzand a écrit :
>> I thought it was the same thing, but may be not.
>> My ejb "PingFacade" has 2 interfaces (1 remote , 1 local) and I got
>> the following trace :
>>
>> WARN  [org.ow2.easybeans.resolver.ContainerJNDIResolver] Data already
>> set for
>> JNDIData[name=fr.mi.siv.mas.pac.ping.service.facade.PingFacade_fr.mi.siv.mas.pac.ping.service.PingService@Remote,
>> beanName=PingFacade] for the container URL
>> file:/SSIV/tmp/jonas/EasyBeans-Deployer-siv/EAR/siv-ear-all-1.6.ear/mas-pac-ejb-1.6.jar.
>>
>>
>> I don't think I am using the BindingFactory mechanism.
>> Nerver mind ;)
>
> Maybe that's another issue, I'm not really up to date with the
> JNDIResolver stuff :)
> To know, maybe you can make a try with latests EZB snapshots of
> version 1.1.0 ?
>
> --G
>
>>
>> Brice
>>
>> Guillaume Sauthier a écrit :
>>> Hi Brice
>>>
>>> AFAIKT, for classic usage of EZB (only RMI & JNDI), this bug is not
>>> a blocker (otherwise you told me so :) ).
>>> At least, you can add a comment and an "affect version" explaining
>>> that this problem is also in 1.0.x
>>> Are you using the BindingFactory mechanism too ?
>>> --G
>>>
>>> Note: Now, it's sure, the SNAPSHOT have been deployed, you can give
>>> it a try ekke
>>>
>>> Brice Ruzand a écrit :
>>>> Is it possible to have this fix in EZB 1.0.x too ?
>>>>
>>>> Thx
>>>>
>>>> Brice
>>>>
>>>> Guillaume Sauthier a écrit :
>>>>> Should be fixed now
>>>>>
>>>>> Ekke, once the SNAPSHOT have been deployed and published (tomorow
>>>>> morning should be OK) in the m2 repository of OW2, could you check
>>>>> that the problem is fixed ?
>>>>> If so, tell me so, and I will close the JIRA.
>>>>>
>>>>> Cheers
>>>>> --Guillaume
>>>>>
>>>>> Guillaume Sauthier a écrit :
>>>>>> I can reproduce the problem here with our test suite:
>>>>>>
>>>>>> org.ow2.easybeans.examples.osgi.SimpleInterface registered 1 times
>>>>>> org.ow2.easybeans.examples.osgi.ISimpleDependency registered 2 times
>>>>>>
>>>>>> .... some time passed ....
>>>>>>
>>>>>> OK, I think I got it.
>>>>>> the problem was not in easybeans-osgi after all :)
>>>>>> It's directly in easybeans, we manage, at the EjbJarContainer
>>>>>> level, a list of BindingReference (used to bind object in JNDI or
>>>>>> register them as services).
>>>>>> During the container startup, we collect a list of BindingRef
>>>>>> (using @Local, @Remote + EJB2.x style interfaces), BUT, the usage
>>>>>> of theses references is done at the bean level, so it ends up
>>>>>> with the list binded for the first bean (1 reference in the
>>>>>> list), then it is binded again for the 2nd EJB (now we have 2
>>>>>> interfaces in the list)... So, the first bean interface/reference
>>>>>> is binded, rebinded and re-re-binded ...
>>>>>>
>>>>>> I should be able to make a fix quickly
>>>>>> --G
>>>>>>
>>>>>> ekke a écrit :
>>>>>>> Guillaume Sauthier schrieb:
>>>>>>>> Hmmm, I still do not see what is going wrong.
>>>>>>>> The only thing that could register mulitple OSGiBF is multiple
>>>>>>>> start() of the EZBCoreService (or multiple easybeans-core
>>>>>>>> bundles being activated).
>>>>>>>>
>>>>>>>> I'm adding a testcase to see if I can reproduce the problem here.
>>>>>>>> I let you know the result ...
>>>>>>>
>>>>>>> thanbks
>>>>>>>
>>>>>>> ekke
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

--

Brice Ruzand
Bull, Architect of an Open World TM
http://www.bull.com
01 49 45 50 16