[OCP 11 Complete Study Guide] [OCP 11 Programmer I Book] [OCP 11 Programmer II Book] [OCP 11 Practice Tests Book] [OCA 8 Book] [OCP 8 Book] [OCP 8 Practice Tests Book] [Blog]
Omkar Puli wrote:i have similar problem and would like to get your feedback
Surely that cannot be literally true. JNDI is an essential JEE service. You cannot locate a database connection pool without it. Every JEE webapp has a distinct JNDI space.Henry Wong wrote:
Omkar Puli wrote:i have similar problem and would like to get your feedback
Basically, JNDI for Websphere is not configured by default -- so when you encounter such an error, it may be a good idea to talk to your Websphere administrator. My administrator fixed it, the last few times that this happened.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:I think that more accurately, JMS probably needs to be configured and registered properly within WAS and possibly the application deployment.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:JMS is literally Java Messaging Services, though, so I have doubts about it having non-Java interfaces. I believe that, barring product name changes, JMS on WebSphere is actually supported by WebSphere MQ. I'm way out of date on that stuff, though.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |