Re: [JBoss-user] Loging out user from webapplication -session.invalidate()doesnt destory all user data - name and password
session.invalidate() will only work if form based auth is being used. If you're using basic auth then you will need to roll your own logout method that uses a 401 response to convince the browser to forget the login details. btw - Closing the browser is/was the traditional way of logging out of basic auth. Servlet Spec 2.4 reportedly has a HttpSession.logout() method but I've not looked into it. On Mon, 3 Mar 2003, Ivan Bolcina wrote: > Hello. > I have several web applications running on jetty/jboss. All of them are > secure and require user to login. I have a problem. User gets into one > applications, then he exits. ( I call session.invalidate()) > Then, user goes to another application, he logs in again and logs out again. > BUT, when he enters the first application again, he is not prompted for > username/password. I belive jetty remembers user's data. I hoped thant when > I do session.invalidate(), everything about this user, object bound to > session as well as his credidentials, will be forgoten. This is not the > case. So how to do this? > > Thank you very much for your help, > Ivan > --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Using Apache web server - yes or no?
http://jetty.mortbay.com/jetty/doc/User80.html You want packet filtering anyway if you are security conscious. On Tue, 17 Dec 2002, Dan Christopherson wrote: > Another thing to remember is that JBoss must run as root to listen on > port 80 or 443. That would be something that security conscious people > might not want to do on a public server. > > -danch > > Larry O wrote: > > I would suggest another criteria. If your application is on an intranet > > or private network and traffic is low, by all means omit apache. > > However, many of us put apache on or outside a firewall, and keep our > > application server safely inside. The fewer services running on the > > exposed server, the better. > > > > My 2 cents. > > Larry > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On Behalf Of Pete Beck > > Sent: Tuesday, December 17, 2002 11:17 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-user] Using Apache web server - yes or no? > > > > > > Just to throw my 2 cents worth in, > > My app uses mostly dynamic content and I have tried using apache as a > > front end, tomcat 4 and Jetty. > > > > In my tests, using apache as a front end added a significant latency to > > serving the content from JBoss. > > > > So I would say yes, you may get benefits on your static content if you > > use apache, but you will also lose performance on your dynamic content. > > > > In my app I dropped apache as a front end as I was getting noticeably > > better performance with tomcat standalone. > > > > Eventually I switched to using to Jetty as it is shipped by default with > > JBoss now, and it seems snappier than tomcat. > > > > A good deciding factor therefore seems to be the ratio of static vs. > > dynamic content on your site. > > > > On Tue, 2002-12-10 at 14:18, Joao Pedro Clemente wrote: > > > >>Andreas, please explain a little bit better where will we get more > >>performance. I can be (and surely am) wrong in my reasoning, but the > >>original message says explicitly "ONLY dynamic applications". So, you > >>say apache should be used to serve images/html... as far as I know, > >>that is static content. So, if you have NO static content, what will > >>apache improve? > >> > >>Regards, > >> Joao Clemente > > > > > > > > > > --- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [jetty-discuss] Re: [JBoss-user] [Jetty] WARNING: HttpException(400,Bad Request, Missing Content)
The simple answer is that Jetty was expecting more bytes to be in the body of the POST than it actually got from the client using a persistent connection. To look much further than this you should enable more verbose Jetty logging and you should be able to inspect the full request to see if there is a problem with the content-length in the request header or whether the client has simply closed the connection unexpectedly. Brett On Thu, 25 Jul 2002, Jules Gosnell wrote: > I'm forwarding you to jetty-discuss: > > Jules > > > Alex Loubyansky wrote: > > Hello guys, > > > > sometimes I meet the following warning: > > WARN [Jetty] WARNING: POST / HTTP/1.1 HttpException(400, > > Bad Request, Missing Content) > > > > Other times this same page is processed without it. All updates are > > done correctly in both cases. > > > > What does this warning mean? > > > > TIA --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBoss 3.0 SSL Newbie Question
Steve, You will need to add a SSL listener to the ConfigurationElement in the META-INF/jboss-service.xml file found in the deploy/jetty-plugin.sar Jetty specific information on setting up SSL can be found at http://jetty.mortbay.org/jetty/JsseSSL.html loading a keystore is described in http://jetty.mortbay.org/jetty/doc/SslListener.html A sample derived from the demo.xml file used by jetty is as follows: 8443 5 255 3 1 5000 2000 ./keystore test testKeyPassword Brett On Thu, 4 Apr 2002, Dmitri Colebatch wrote: > Hi, > > I cant say for sure, but I would look in the jetty-service.sar (or is it now just >jetty-service.xml) in the deploy directory. That > file (as I understand it) is responsible for configuring jetty. Have a look at >that, and probably also the jetty site/lists > (http://sf.net/projects/jetty) should help. > > hth > dim > > - Original Message - > From: "Stephen Davidson" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, April 04, 2002 8:45 AM > Subject: [JBoss-user] JBoss 3.0 SSL Newbie Question > > > > Greetings. > > > > Ok, I have checked the JBoss Book (jboss.cml is the file to modify, not used in >3.0) > > Searched the web. > > Checked the jboss.org site. > > Searched the docs. > > > > I have been unable to find out how to configure SSL for JBoss 3.0 WebServer >(Jetty)? I am trying to configure for Browsers to > connect in SSL mode. > > 128bit mode minimum would be preferred. Don't need the EJBs in SSL, as they >will be behind the firewall. > > > > Help please? > > > > -Steve ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Cookies and Jetty...
Can you clarify what exactly the problem is? The VERSIONS.TXT file in Jetty has the following cookie related entries which might be related to your problem, they were addressed in Jetty-3.1.5 and Jetty-4.0.D releases, 3.1.3 is over three months old now: + setCookie always has equals for cookie value + cookies with maxage==0 expired 1 jan 1970 Jetty complies with the Servlet spec, as does tomcat. We'd love to help more but a bit more info would be useful. Cheers, Brett On Mon, 28 Jan 2002, [ISO-8859-2] Jarecsni János wrote: > Hi, > > today I've downloaded JBoss-2.4.4_Jetty-3.1.3-1. I've been porting my > application to this new version from a JBoss-Tomcat bundle. It seems that > Jetty does not create and send cookies as Tomcat does. Does Jetty need some > extra configuration? > > Hope someone has the answer... :) > > Cheers, > János ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Help-SSL
Jetty and Tomcat both have SSL support using the JSSE builtin. If you don't have a super high HTTPS performance requirement then check it out. Cheers, Brett On Tue, 10 Jul 2001 [EMAIL PROTECTED] wrote: > Hi all, > Thanks for the help previously.Any one has an idea how to implement SSL and > is it possible.Im using Jboss 2.2.2 with tomcat and JDK 1.3 > Thanks > Sharath > > > > > > ___ > Send a cool gift with your E-Card > http://www.bluemountain.com/giftcenter/ > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] ....Jetty.... IllegalStateException when doingjsp:include on a servlet
I'm not sure when it will be fixed - may be some time. btw Shouldn't you be going straight to the Servlet first - then just use jsp to display? On Wed, 4 Jul 2001, Jonas Tehler wrote: > Brett Sealey wrote: > > > On Tue, 3 Jul 2001, Jonas Tehler wrote: > > > > > >>Hi, > >> > >>I am trying to use to include a servlet into a jsp-page > >>resulting in: > >> > >>java.lang.IllegalStateException: Request is committed > >> > >>According to the changelog for Jetty this have been fixed: > >> > >>Jetty-3.0.2 - 13 Jan 2001 > >> + Ignore included response updates rather than IllegalStateException > >> > >>Is this a problem with JBoss+Jetty? Or have the bug somehow sneaked back > >>into 3.1.x? Or is this some other problem I'm having? > >> > >>/ Jonas > >> > > > > Jonas, > > > > The included servlet is attempting to do a forward() from within the > > jsp:include. I think this is a different problem to the one reported fixed > > in Jetty-3.0.2. > > > > Trying to use a sendRedirect instead didn't work for me either > > (java.lang.IllegalStateException: Output committed). If you can do the > > forward before you do the jsp:include then you will be able to work around > > it. > > Yes, that must be the problem. I am using Struts and want to jsp:include > the output from an Action that forwards to a JSP page... > > Is this something that will be fixed? > > / Jonas > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] ....Jetty.... IllegalStateException when doingjsp:include on a servlet
On Tue, 3 Jul 2001, Jonas Tehler wrote: > Hi, > > I am trying to use to include a servlet into a jsp-page > resulting in: > > java.lang.IllegalStateException: Request is committed > > According to the changelog for Jetty this have been fixed: > > Jetty-3.0.2 - 13 Jan 2001 > + Ignore included response updates rather than IllegalStateException > > Is this a problem with JBoss+Jetty? Or have the bug somehow sneaked back > into 3.1.x? Or is this some other problem I'm having? > > / Jonas Jonas, The included servlet is attempting to do a forward() from within the jsp:include. I think this is a different problem to the one reported fixed in Jetty-3.0.2. Trying to use a sendRedirect instead didn't work for me either (java.lang.IllegalStateException: Output committed). If you can do the forward before you do the jsp:include then you will be able to work around it. I can reproduce it using these three files: includer.jsp: -- -- includee.jsp: -- -- includee.html: -- Here I am. -- And when I hit includer.jsp I get the following Exception: 23:35:54.698 WARN!! Servlet Exception for /jetty/includer.jsp + java.lang.IllegalStateException: Request is committed + at com.mortbay.Jetty.Servlet.Dispatcher.forward(Dispatcher.java:161) + at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:421) + at +_0002fincludee_0002ejspincludee_jsp_0._jspService(_0002fincludee_0002ejspincludee_jsp_0.java:59) + at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) + at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) + at +org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:176) + at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:307) + at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) + at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) + at com.mortbay.Jetty.Servlet.ServletHolder.handle(ServletHolder.java:488) + at com.mortbay.Jetty.Servlet.Dispatcher.include(Dispatcher.java:332) + at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:414) + at +_0002fincluder_0002ejspincluder_jsp_0._jspService(_0002fincluder_0002ejspincluder_jsp_0.java:62) + at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) + at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) + at +org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:176) + at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:307) + at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) + at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) + at com.mortbay.Jetty.Servlet.ServletHolder.handle(ServletHolder.java:488) + at com.mortbay.Jetty.Servlet.ServletHandler.handle(ServletHandler.java:488) + at com.mortbay.Jetty.Servlet.ServletHandler.handle(ServletHandler.java:317) + at com.mortbay.HTTP.HandlerContext.handle(HandlerContext.java:956) + at com.mortbay.HTTP.HandlerContext.handle(HandlerContext.java:913) + at com.mortbay.HTTP.HttpServer.service(HttpServer.java:714) + at com.mortbay.HTTP.HttpConnection.service(HttpConnection.java:521) + at com.mortbay.HTTP.HttpConnection.handle(HttpConnection.java:347) + at com.mortbay.HTTP.SocketListener.handleConnection(SocketListener.java:107) + at com.mortbay.Util.ThreadedServer.handle(ThreadedServer.java:294) + at com.mortbay.Util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:613) + at java.lang.Thread.run(Thread.java:484) Cheers, Brett ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jBoss-Jetty RC5 Still Getting NULL NULL NULL
The "null null null" message is a bit of escaped debug. It is harmless despite being irritating. It was occuring when a HTTP connection with keepalive is closed, normally after a timeout. Hopefully Jules has it fixed this time round or else there goes another perfectly good hat... :-) Brett On Mon, 2 Jul 2001, Julian Gosnell wrote: > [EMAIL PROTECTED] wrote: > > > > > Me too. Even if I just let it sit there and do nothing, every so > > often I see the NULL NULL NULL msg. > > > > Kind of a nuisance, but doesn't seem to hurt anything. > > > > Robert Price > > epixtech, inc. > > (801) 223-5954 > > [EMAIL PROTECTED] > > There will be a 2.4.0BETA based release available on the binaries page > very soon now. > > Try this, and if you get the dreaded null-null-null Exception, I may > have to eat my hat. > > > Jules > > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Is SSLSocketFactory integration (port 8443) brokenas of JBoss-2.2.2_Tomcat-3.2.2.zip?
You need to specify https. e.g. https://localhost:8443/ Cheers, Brett On Sun, 10 Jun 2001, Matt Vincent wrote: > > 1st and foremost JBoss is an excellent tool! Thank you so much to all who > have built it! > > Here's my problem: > Has anyone had success with org.apache.tomcat.net.SSLSocketFactory in JBoss > 2.2.2? > > On calling http://localhost:8443/ I receive the SSL handshake error printed > below. > I used keytool, have the jsse1.0.2 jars in the jboss classpath and am using > Sun's jdk1.3 on RedHat 7.0. > > I had the 8443 port working with jboss-tomcat-2.2.zip distribution. > > server.xml: > > > value="org.apache.tomcat.service.http.HttpConnectionHandler"/> > value="8443"/> > value="org.apache.tomcat.net.SSLSocketFactory" /> > > > > > > Thanks for any help offered! > > Matt Vincent > [EMAIL PROTECTED] > > > > 2003-06-10 09:08:15 - PoolTcpConnector: Starting HttpConnectionHandler on > 8080 > 2003-06-10 09:08:46 - PoolTcpConnector: Starting HttpConnectionHandler on > 8443 > 2003-06-10 09:08:51 - PoolTcpConnector: Starting Ajp12ConnectionHandler on > 8007 > [EmbeddedTomcatSX] OK > [EmbeddedTomcatSX] Started > [JBossMQ] Starting > 2003-06-10 09:08:55 - PoolTcpConnector: Starting Ajp13ConnectionHandler on > 8009 > ... > ... > [Service Control] Started 25 services > [Default] JBoss 2.2.2 Started in 1m:15s > 2003-06-10 09:14:14 - ContextManager: IOException reading request, ignored - > javax.net.ssl.SSLException: Unrecognized SSL handshake. > at > com.sun.net.ssl.internal.ssl.InputRecord.read([DashoPro-V1.2-120198]) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198]) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198]) > at > com.sun.net.ssl.internal.ssl.AppInputStream.read([DashoPro-V1.2-120198]) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:186) > at java.io.BufferedInputStream.read(BufferedInputStream.java:204) > at > org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter. > java:115) > at > org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu > tStream.java:106) > at > org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS > tream.java:128) > at > javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138) > at > org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques > tAdapter.java:129) > at > org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC > onnectionHandler.java:198) > at > org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) > at > org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) > at java.lang.Thread.run(Thread.java:484) > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBoss 2.2.2 / Jetty 3.1RC5 package available
This is apparently caused by the Jetty HttpServer.destroy() method being called when it has a HandlerContext that is null. The Exception is probably harmless since it would have continued with the destruction of all non-null contexts etc normally. Without further investigation I'm not sure how this is happening. On Sun, 10 Jun 2001, Jim Archer wrote: > After running a perl script that loads my app for a while, I shut down > Jetty (On W2K) with CTRL-C and durin the shutdown it threw a > nullpointereception. I'll paste a log excerpt below. > > Jim > > > > [Jetty] Destroyed SecurityHandler in null > [Jetty] Destroyed WebInfProtect > [Jetty] Destroyed ResourceHandler in null > [Jetty] Destroyed NotFoundHandler in null > [Jetty] Destroyed SecurityHandler in null > [Jetty] Destroyed WebInfProtect > [Jetty] Destroy SocketListener on 0.0.0.0:8080 > [Jetty] Deregister com.mortbay.Jetty:name=Jetty,Jetty=0,SocketListener=0 > [PersistenceSPI] Destroying > [PersistenceSPI] Destroyed > [Jetty] Destroying > [Jetty] Destroying (jetty.mortbay.com) > [Jetty] java.lang.NullPointerException > [Jetty] at com.mortbay.HTTP.HttpServer.destroy(HttpServer.java:229) > [Jetty] at > org.jboss.jetty.JettyService.destroyService(JettyService.java > :317) > [Jetty] at > org.jboss.util.ServiceMBeanSupport.destroy(ServiceMBeanSuppor > t.java:147) > [Jetty] at java.lang.reflect.Method.invoke(Native Method) > [Jetty] at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl > .java:1628) > [Jetty] at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl > .java:1523) > [Jetty] at > org.jboss.util.ServiceControl.destroy(ServiceControl.java:172 > ) > [Jetty] at java.lang.reflect.Method.invoke(Native Method) > [Jetty] at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl > .java:1628) > [Jetty] at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl > .java:1523) > [Jetty] at > org.jboss.util.Shutdown.shutdownServices(Shutdown.java:96) > [Jetty] at org.jboss.util.Shutdown$1.run(Shutdown.java:56) > [Jetty] Destroyed > [Mail Service] Destroying > [Mail Service] Destroyed > [JMX RMI Connector] Destroying > [JMX RMI Connector] Destroyed > [JMX RMI Adaptor] Destroying > [JMX RMI Adaptor] Destroyed > [BlackBoxDS] Destroying > [BlackBoxDS] Destroyed > [MinervaXACMFactory] Destroying > [MinervaXACMFactory] Destroyed > [MinervaSharedLocalCMFactory] Destroying > [MinervaSharedLocalCMFactory] Destroyed > [MinervaNoTransCMFactory] Destroying > [MinervaNoTransCMFactory] Destroyed > [RARDeployer] Destroying > [RARDeployer] Destroyed > [Auto deploy] Destroying > [Auto deploy] Destroyed > [J2EE Deployer Default] Destroying > [J2EE Deployer Default] Destroyed > [StdJMSPool] Destroying > [StdJMSPool] Destroyed > [DefaultJMSProvider] Destroying > [DefaultJMSProvider] Destroyed > [JBossMQ] Destroying > [JBossMQ] Destroyed > [Container factory] Destroying > [Container factory] Destroyed > [DefaultDS] Destroying > [DefaultDS] Destroyed > [InstantDB] Destroying > [InstantDB] Destroyed > [Hypersonic] Destroying > [Hypersonic] Destroyed > [JDBC provider] Destroying > [JDBC provider] Destroyed > [JAAS Security Manager] Destroying > [JAAS Security Manager] Destroyed > [Transaction manager] Destroying > [Transaction manager] Destroyed > [JNDIView] Destroying > [JNDIView] Destroyed > [Naming] Destroying > [Naming] Destroyed > [Webserver] Destroying > [Webserver] Destroyed > [Service Control] Destroyed 35 services > [Jetty] Shutdown complete > Terminate batch job (Y/N)? > > > > > > > > > I shall be telling this with a sigh > Somewhere ages and ages hence: > Two roads diverged in a wood, and I - > I took the one less traveled by, > And that has made all the difference. > > - Robert Frost, 1916 > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
