Comment #1 on issue 13 by [email protected]: Wrong RA entity
bound to same object name
http://code.google.com/p/jain-slee/issues/detail?id=13
It is actually worse than originally reported: distinct SBBs of separate
services are also affected by this issue. This means that one service can
corrupt the component environment of SBBs of another service in the case of
Resource Adaptor object name collision. I see this as an even worse
instance of the issue as it is a lot more likely for developers of separate
services to not know details of another service than it is to not know
details of another SBB in the same service. It is not uncommon to encounter
services developed by different vendors in the same deployment.
Even though the workaround is trivial (ensure all SBBs use unique RA object
names), this issue can lead to subtle and difficult to troubleshoot issues.
Find attached two trivial services to demo the issue, deploy-config.xml for
JDBC RA (also needed for the demonstration) and a server log fragment.
Scenario:
1. Deploy first service. Observe that first JDBC RA entity is bound to its
environment.
2. Deploy second service. Observe that both services now have second JDBC
RA entity bound to their environments, which means both services would
start using the same DS, the same connection pool, etc.
The issue does not seem to affect env-entries.
Attachments:
issue_13_demo.tbz 5.5 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
