[#MULE-3785] Cache queues/topics looked up from JNDI

Mule

Cache queues/topics looked up from JNDI

Created: 06/Oct/08 11:56 AM Updated: 15/Nov/08 11:42 AM

Component/s:

Transport: JMS

Affects Version/s:

2.1.0

Fix Version/s:

2.x Product Backlog

Time Tracking:

Original Estimate:

1 day

Remaining Estimate:

1 day

Time Spent:

Not Specified

Issue Links:

Related

This issue relates to:

~~MULE-3384~~ No way to look up queue/topic via JNDI for Mule 2.0

Labels:
User impact:	Medium
Effort points:	1
Affects Docs:	Yes

Description

« Hide

The current implementation looks up a queue/topic from JNDI every time a message is being dispatched or received from it. We could cache the result of JNDI lookups and expose some JMX functionality to purge that cache

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 06/Oct/08 12:29 PM

Spring's jndi lookup factories already provide caching.

[ Permlink | « Hide ]

Dirk Olmes added a comment - 07/Oct/08 02:50 AM

Spring's JNDI stuff doesn't have retry functionality, however. And we cannot use Spring in core because it has to work spring-less.

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 23/Oct/08 05:45 PM

On the other hand, I'm yet to be convinced about the benefit of such caching. Need those performance numbers from profiler, otherwise it's more troublesome than beneficial.

[ Permlink | « Hide ]

Ross Mason added a comment - 15/Nov/08 11:42 AM

I think caching would make a difference since depending on the JNDI directory we may be making a network hit for every message