There is no magic in OSGi. Normal Java object reference rules apply. If a strongly referenced object A has a strong reference to object B, then B can't be garbage collected. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: "Pruitt, Byron S" <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2009/04/27 16:04 Subject: RE: [osgi-dev] can't get rid of temporaryqueues Sent by: [email protected] My apologies. My question was a very clumsy attempt to ask if there was anything I should be aware of specific to resource allocation and retention specific to OSGi. Specifically resources acquired by a JMS provider. Looking at my question, I understand the confusion. Thanks. -S From: [email protected] [ mailto:[email protected]] On Behalf Of BJ Hargrave Sent: Friday, April 24, 2009 11:46 AM To: OSGi Developer Mail List Subject: Re: [osgi-dev] can't get rid of temporaryqueues Sorry, but I don't see any OSGi question in here? Just a bunch of discussion of JMS, MQ. etc. If you meant to send this to the osgi-dev, can you please describe your question in terms the OSGi crowd can understand? :-) -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: "Pruitt, Byron S" <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2009/04/24 10:20 Subject: [osgi-dev] can't get rid of temporaryqueues Sent by: [email protected] I have a very specific issue with JMS. If anyone has some advice it would be greatly appreciated. I implemented a component service that has message queue services. The service is implemented using standard JMS. Nothing like Spring, etc was used. The receiving end is MQ Series running on Z/OS. IBM’s libraries for MQ / JMS are used as the provider framework. TemporaryQueues are used for replies coming back from MQ by setting the message’s setJMSReplyTo property. The message send / receipt is working fine. Our problem is the temporary queues pile up on the MQ side and do not go away. When they try to delete them they get a IS CURRENTLY IN USE error message. I have tried tempq.delete() after receiving the reply message, but it doesn’t seem to have any affect. I assumed TemporaryQueues would go away on their own. My experience is limited, so I don’t know if there is something specific to OSGi and its resource management that is interfering. -S_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
