[JBoss-dev] RH, Jetty, testsuite, Exceptions...
It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) [Default] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) [Default] at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) [Default] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) [Default] at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) [Default] at java.lang.Thread.run(Thread.java:484) [Jetty] Servlet Exception for /jbosstest/ENCServlet javax.naming.NameNotFoundException: QueueConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getObject(Unknown Source) at org.jnp.server.NamingServer.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) getRootCause(): I have a few more exceptions after this one, but they may be as a result of this failing. If any kind soul knows about this test, and whether it is new, and expecting me to do something that I am not doing, I would appreciate your letting me know. It is possible, that the testsuite is in a state of flux at the moment (refreshed an hour or so ago) and that this won't work anyway ? Cheers, Jules
RE: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) [Default] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) [Default] at org.mortbay.http.SocketListener.handleConnection(SocketListene r.java:146) [Default] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) [Default] at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool. java:613) [Default] at java.lang.Thread.run(Thread.java:484) [Jetty] Servlet Exception for /jbosstest/ENCServlet javax.naming.NameNotFoundException: QueueConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getBinding(Unknown Source) at org.jnp.server.NamingServer.getObject(Unknown Source) at org.jnp.server.NamingServer.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListene r.java:146
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) [Default] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler .java:390) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) [Default] at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) [Default] at org.mortbay.http.HttpServer.service(HttpServer.java:674) [Default] at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) [Default] at org.mortbay.http.HttpConnection.handleNext
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Hmm.. you sure the auth.conf file is available in your classpath for the client? -- Juha On Mon, 17 Sep 2001, Julian Gosnell wrote: Date: Mon, 17 Sep 2001 21:49:05 +0100 From: Julian Gosnell [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
Security is broken in RH as the security setup code has been commented out in org.jboss.Main. Until I look into restoring this all security tests are pointless. - Original Message - From: Julian Gosnell [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, September 17, 2001 1:49 PM Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.j ava:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) [Default] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) [Default] at org.mortbay.jetty.servlet.ServletHolder.handle
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
HaHa! OK, Thanks, Scott, I'll move on Cheers, Jules Scott M Stark wrote: Security is broken in RH as the security setup code has been commented out in org.jboss.Main. Until I look into restoring this all security tests are pointless. - Original Message - From: Julian Gosnell [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, September 17, 2001 1:49 PM Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.j ava:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.processRequest(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.doGet(Unknown Source) [Default
Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions...
I'm running the testsuite, so I assume that it is, or it would never have run. I've checked in all my changes. So if anyone wants to refresh their RH tree and run the web test module, I would be interested to hear their thoughts. Thanks, Jules Juha-P Lindfors wrote: Hmm.. you sure the auth.conf file is available in your classpath for the client? -- Juha On Mon, 17 Sep 2001, Julian Gosnell wrote: Date: Mon, 17 Sep 2001 21:49:05 +0100 From: Julian Gosnell [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RH, Jetty, testsuite, Exceptions... Thanks David that's one more cleared up: I had to change resource-ref res-ref-namejms/QueFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type jndi-nameConnectionFactory/jndi-name /resource-ref The JNDI name was wrong. I shall check this in soon - so if i am wrong, let me know pronto ! I only appear to have one problem left, it just repeats a few times. I would appreciate any pointers : [Jetty] Servlet Exception for /jbosstest/ClientLoginServlet java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) at javax.security.auth.login.LoginContext.init(Unknown Source) at javax.security.auth.login.LoginContext.init(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doLogin(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.processRequest(Unknown Source) at org.jboss.test.web.servlets.ClientLoginServlet.doGet(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:488) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:1027) at org.mortbay.http.HandlerContext.handle(HandlerContext.java:982) at org.mortbay.http.HttpServer.service(HttpServer.java:674) at org.mortbay.http.HttpConnection.service(HttpConnection.java:732) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:889) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:746) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:146) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) at java.lang.Thread.run(Thread.java:484) If anyone knows anything about this exception, I would appreciate a few pointers. Cheer, Jules David Maplesden wrote: I don't know anything about this test, but I can see one problem straight away, JBossMQ no longer uses the name QueueConnectionFactory in its default setup so unless you have changed the MQ configuration (which is unlikely, yes?) then the name that should be looked up by the test is just ConnectionFactory. Cheers David. -Original Message- From: Julian Gosnell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 18, 2001 8:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] RH, Jetty, testsuite, Exceptions... It looks like some new tests may have gone into the web test module. I am trying to get RH/Jetty to pass and have come up against the following : [Jetty] ENCServlet: init [Default] ejb/bean0 = ENCBean0Home [Default] ejb/bean1 = ENCBean1Home [Default] ejb/bean2 = ENCBean1Home [Default] ejb/UnsecuredEJB = jbosstest/ejbs/UnsecuredEJBHome [Default] ejb/SecuredEJB = jbosstest/ejbs/SecuredEJBHome [Default] jdbc/DefaultDS = org.jboss.resource.adapter.jdbc.JDBCDataSource@661fd1 [Default] mail/DefaultMail = javax.mail.Session@4ab2f [Default] javax.naming.NameNotFoundException: QueueConnectionFactory not bound [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getBinding(Unknown Source) [Default] at org.jnp.server.NamingServer.getObject(Unknown Source) [Default] at org.jnp.server.NamingServer.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at javax.naming.InitialContext.lookup(InitialContext.java:350) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jnp.interfaces.NamingContext.lookup(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testJMS(Unknown Source) [Default] at org.jboss.test.web.servlets.ENCServlet.testENC(Unknown Source) [Default
