This content has been marked as final.
Show 5 replies
-
1. Re: Why do we get connection factory warnings when starting the server?
ataylor Jan 11, 2010 4:39 AM (in response to timfox)This is because we bind to /ConnectionFactory and java:/ConnectionFactory and we dont need to. I removed these from the config files some time ago but it looks like they have creeped back in. I will remove them again. -
2. Re: Why do we get connection factory warnings when starting the server?
ataylor Jan 11, 2010 9:30 AM (in response to ataylor)Ive also noticed that the AS configs have an invm connection factory configured and bound to the same names as the netty connection factory.
1. do we actually need the invm connectors as users should use the jca connection factory not the invm one.
2. if we do want it, what names should we bind it to.
-
3. Re: Why do we get connection factory warnings when starting the server?
timfox Jan 11, 2010 9:51 AM (in response to ataylor)In the app server the "java:" prefix means "in the same invm" (it's a JNDI convention).
Therefore the one bound at java:/ConnectionFactory should use the invm transport, whereas the one bound at /ConnectionFactory should use netty since this is accessible from outside the AS vm.
-
4. Re: Why do we get connection factory warnings when starting the server?
ataylor Jan 11, 2010 9:56 AM (in response to timfox)I dont think that is the case, i know java: prefix means "in same vm" but that doesn't mean you can use the same path for an object. Start up the AS and you will see the warnings because of this. -
5. Re: Why do we get connection factory warnings when starting the server?
ataylor Jan 11, 2010 10:14 AM (in response to ataylor)ignore my last post, you are right, i was using dodgy configs.