Closed GoogleCodeExporter closed 9 years ago
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.
Original comment by vil...@users.sourceforge.net
on 4 Apr 2014 at 1:03
Attachments:
This issue was closed by revision 7a93afabf135.
Original comment by EMMart...@gmail.com
on 1 Aug 2014 at 1:08
Original issue reported on code.google.com by
be.lietaus
on 21 Nov 2012 at 12:15Attachments: