Looking for best practice with profiles and many naming subsystem bindings
Issue
-
We have a domain set up with multiple server groups using a single profile (full). Each server group serves a separate application. We have a new application that requires numerous naming subsystem bindings (more than 50). We're wondering if it would be better to create a separate profile just for that one application. Are there any penalties for loading all those bindings for all the server groups that do not need them?
-
Or is there no real reason to create a separate profile for the one application?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.2.4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.