Re: intermittent SocketException on startup tomcat 5.5.28 and under JBOSS 4.2.3GA
Thanks for response. The first server on I install tomcat 5.5.28 is win2003 server and after I install jboss on win2008 server . All server have 32bit SO and i don't have a firewall . I disenable all firewall, all antivirus. I suppose that two different errors regard different JVM and/or Application server (first Tomct 5.5.28 on win2003 and after Jboss4.2.3GA on win2008) At any rate i have now only log by Tomcat 5.5.28 under win2003: The log is: 19-apr-2010 7.14.40 org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\tomcat6\Tomcat 6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C: \Windows;C:\oracle\product\10.2.0\client_3\bin;C:\oracle\product\10.2.0 \client_1;C:\oracle\product\10.2.0\client_2;C:\Windows\system32;C:\Windows;C: \Windows\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C: \Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ 19-apr-2010 7.14.40 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-80 19-apr-2010 7.14.40 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 334 ms 19-apr-2010 7.14.40 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 19-apr-2010 7.14.40 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.26 19-apr-2010 7.14.40 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor manager.xml 19-apr-2010 7.14.40 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor probe.xml 19-apr-2010 7.14.40 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory docs 19-apr-2010 7.14.40 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory SIT 19-apr-2010 7.14.40 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory SVILUPPO 19-apr-2010 7.14.40 org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-80 19-apr-2010 7.14.40 org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 19-apr-2010 7.14.40 org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/16 config=null 19-apr-2010 7.14.40 org.apache.catalina.startup.Catalina start INFO: Server startup in 641 ms 19-apr-2010 7.23.01 org.apache.tomcat.util.net.JIoEndpoint$Acceptor run GRAVE: Socket accept failed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket (DefaultServerSocketFactory.java:61) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:352) at java.lang.Thread.run(Unknown Source) 19-apr-2010 7.23.01 org.apache.tomcat.util.net.JIoEndpoint$Acceptor run GRAVE: Socket accept failed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket (DefaultServerSocketFactory.java:61) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:352) at java.lang.Thread.run(Unknown Source) 19-apr-2010 7.26.48 org.apache.tomcat.util.net.JIoEndpoint$Acceptor run GRAVE: Socket accept failed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket (DefaultServerSocketFactory.java:61) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:352) at java.lang.Thread.run(Unknown Source) 19-apr-2010 7.35.29 org.apache.tomcat.util.net.JIoEndpoint$Acceptor run GRAVE: Socket accept failed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at org.apache.tomcat.util.net
RE: set-cookie
Hi Chuck,
i have found out who is generating that in my code:
dispatcher.forward(request, response);
the response contains also the set cookie header...it is automatically done
by tomcat...
n828cl wrote:
>
>> From: banto [mailto:banto...@gmail.com]
>> Subject: RE: set-cookie
>>
>> ..then where the
>>
>> set-cookie come from if not from the line
>> getServletContext().setAttribute("products", products);?
>
> That's part of the init() method, called when the servlet initializes, not
> when it's processing a request. There's no request or response involved
> at that time, so it's impossible for that code to have any relationship
> with cookie generation or evaluation (or session creation).
>
> See my previous response - you're creating a session somewhere, so Tomcat
> generates the appropriate cookie when that happens.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
>
--
View this message in context:
http://old.nabble.com/set-cookie-tp28639362p28644188.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: set-cookie
> From: banto [mailto:banto...@gmail.com]
> Subject: RE: set-cookie
>
> ..then where the
>
> set-cookie come from if not from the line
> getServletContext().setAttribute("products", products);?
That's part of the init() method, called when the servlet initializes, not when
it's processing a request. There's no request or response involved at that
time, so it's impossible for that code to have any relationship with cookie
generation or evaluation (or session creation).
See my previous response - you're creating a session somewhere, so Tomcat
generates the appropriate cookie when that happens.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
Re: Way to record what URL an error originated from in my localhost file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave, On 5/21/2010 4:41 PM, laredotornado wrote: > Thanks for this suggestion. Just to be sure I'm understanding correctly, > the procedure would be > > 1. Add an error-page element to my xml doc that will be visited whenever an > exception is generated from my JSP or servlet. > 2. Configure valve to output a stack trace and the original request URI that > generated the error. > > Is that right? I would choose one or the other: AccessLogValve /might/ be able to meet your needs, depending on what they are. If not, implement your own error page that logs whatever information you want to wherever you want it to go. > Also is valve smart enough to understand that I don't want > to see "500.jsp" in my log file but rather something like > "search_results.jsp?category=1" ? I think the AccessLogValve only logs original requests -- that is, it won't log included or forwarded files like error pages. I must admit, though, that I don't really use the AccessLogValve -- I have Apache httpd doing my logging for me. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv3zjAACgkQ9CaO5/Lv0PAotACgwgcboVKDnFhtN6N/QRCxOKFR yAcAoJFQ+ARwsJ43xGbJfvS3xVlnF5sw =BNo0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: set-cookie
//if we reached here, no exception, cookie is valid the header name is
Set-Cookie for both "old" and v.1 ( RFC2109 )
//RFC2965 is not supported by browsers and the Servlet spec asks for 2109.
//in any case the cookie is added to the response header with Set-Cookie
keyword as seen here
Response.addHeader("Set-Cookie", string);
?
Martin--
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Sat, 22 May 2010 01:15:15 -0700
> From: banto...@gmail.com
> To: users@tomcat.apache.org
> Subject: RE: set-cookie
>
>
> ..then where the
>
> set-cookie come from if not from the line
> getServletContext().setAttribute("products", products);?
>
> actually i added this line to another servlet but no
> set-cookie header is sent?
>
> thanks
>
> n828cl wrote:
> >
> >> From: André Warnier [mailto:a...@ice-sa.com]
> >> Subject: Re: set-cookie
> >>
> >> // Store products in the ServletContext
> >> getServletContext().setAttribute("products", products);
> >>
> >> Presumably, if you store something in the context, it is because you
> >> want to retrieve it later (or else, what's the point he ?).
> >> Now, Tomcat has no way to know when you'll come back to retrieve it, so
> >> it has to create a session to store this.
> >
> > Nope, that's not it (but I don't know what is, yet). Attributes stored in
> > a ServletContext have a webapp, not session, scope; no session is needed
> > here, and nothing needs to be communicated between the client and server
> > to retrieve them.
> >
> > - Chuck
> >
> >
> > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> > MATERIAL and is thus for use only by the intended recipient. If you
> > received this in error, please contact the sender and delete the e-mail
> > and its attachments from all computers.
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/set-cookie-tp28639362p28641797.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
_
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
Re: intermittent SocketException on startup tomcat 5.5.28 and under JBOSS 4.2.3GA
On 22/05/2010 09:28, ago...@libero.it wrote: > Good Morning > > Excuse for my poor english > > I have a strange error that occours on startup and after some minutes this > cause the block of my appliction, only stop webserver from lot minutes or > restart server sometime resolve the problem. But often the problem persist. > > In Short: > I have a web appliction deployed initially under tomcat 5.5.28 (with jre- > 1_5_0_22 and SO win2003 Server 32 bit) that sometimes cause specially on > startup the follow error: > > 17-apr-2010 7.00.49 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] > ignored exception: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) > at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket > (JSSESocketFactory.java:117) > at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. > java:408) > at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt > (LeaderFollowerWorkerThread.java:71) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. > java:689) > at java.lang.Thread.run(Unknown Source) > 17-apr-2010 7.01.10 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > AVVERTENZA: Reinitializing ServerSocket > 17-apr-2010 7.52.33 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] > ignored exception: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) > at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket > (JSSESocketFactory.java:117) > at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. > java:408) > at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt > (LeaderFollowerWorkerThread.java:71) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. > java:689) > at java.lang.Thread.run(Unknown Source) > 17-apr-2010 7.52.54 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > AVVERTENZA: Reinitializing ServerSocket > 17-apr-2010 7.52.55 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] > ignored exception: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) > at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket > (JSSESocketFactory.java:117) > at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. > java:408) > at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt > (LeaderFollowerWorkerThread.java:71) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. > java:689) > at java.lang.Thread.run(Unknown Source) > 17-apr-2010 7.53.16 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > AVVERTENZA: Reinitializing ServerSocket > 17-apr-2010 7.53.17 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] > ignored exception: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.PlainSocketImpl.accept(Unknown Source) > at java.net.ServerSocket.implAccept(Unknown Source) > at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) > at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket > (JSSESocketFactory.java:117) > at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. > java:408) > at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt > (LeaderFollowerWorkerThread.java:71) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. > java:689) > at java.lang.Thread.run(Unknown Source) > 17-apr-2010 7.53.38 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > AVVERTENZA: Reinitializing ServerSocket > 17-apr-2010 7.53.39 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket > GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] > ignored exception: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at jav
Re: Way to record what URL an error originated from in my localhost file?
2010/5/22 laredotornado : > > Thanks for this suggestion. Just to be sure I'm understanding correctly, > the procedure would be > In general your understanding is correct, but _read_ the servlet spec, chapter SRV.9.9 "Error Handling", as you were told already. That there is a valve somewhere is just implementation details. Specifications for Tomcat 6: Servlet spec: http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html JSP spec: http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: question for singlesignon for vertical cluster
On 21/05/2010 22:31, Okubo, Yasushi (TSD) wrote: > Hi > > I would like to enable singlesignon on vertical cluster environment > [multi-nodes on multiple hosts]. > > We are using clustersinglesignon under host element, and this works in > horizontal cluster, but does not work in vertical cluster environment. > > Is there any way to make this work as part of tomcat configuration? > When the node goes down, and a user may be routed to the node located in > a different host, it will ask a user to relogin again under the current > setup. We would like to avoid a user for relogging to the application. > > Thanks, > yasushi Please start a new thread, rather than replying to, and editing the body & subject line (called "thread hijacking"). Make sure you include exact OS, JVM and Tomcat versions. p > unpackWARs="true" autoDeploy="true" > xmlValidation="false" xmlNamespaceAware="false"> > > className="org.apache.catalina.ha.authenticator.ClusterSingleSignOn" /> > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > signature.asc Description: OpenPGP digital signature
intermittent SocketException on startup tomcat 5.5.28 and under JBOSS 4.2.3GA
Good Morning Excuse for my poor english I have a strange error that occours on startup and after some minutes this cause the block of my appliction, only stop webserver from lot minutes or restart server sometime resolve the problem. But often the problem persist. In Short: I have a web appliction deployed initially under tomcat 5.5.28 (with jre- 1_5_0_22 and SO win2003 Server 32 bit) that sometimes cause specially on startup the follow error: 17-apr-2010 7.00.49 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket (JSSESocketFactory.java:117) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. java:408) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:71) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. java:689) at java.lang.Thread.run(Unknown Source) 17-apr-2010 7.01.10 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket AVVERTENZA: Reinitializing ServerSocket 17-apr-2010 7.52.33 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket (JSSESocketFactory.java:117) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. java:408) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:71) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. java:689) at java.lang.Thread.run(Unknown Source) 17-apr-2010 7.52.54 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket AVVERTENZA: Reinitializing ServerSocket 17-apr-2010 7.52.55 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket (JSSESocketFactory.java:117) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. java:408) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:71) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. java:689) at java.lang.Thread.run(Unknown Source) 17-apr-2010 7.53.16 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket AVVERTENZA: Reinitializing ServerSocket 17-apr-2010 7.53.17 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket (JSSESocketFactory.java:117) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. java:408) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:71) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. java:689) at java.lang.Thread.run(Unknown Source) 17-apr-2010 7.53.38 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket AVVERTENZA: Reinitializing ServerSocket 17-apr-2010 7.53.39 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) . in tomcat server.xml i have configured 2 connector: one su port 80 and other on port 443, The connectors configuration is: Connector port="80" maxHttpHeaderSize="8192"
RE: set-cookie
..then where the
set-cookie come from if not from the line
getServletContext().setAttribute("products", products);?
actually i added this line to another servlet but no
set-cookie header is sent?
thanks
n828cl wrote:
>
>> From: André Warnier [mailto:a...@ice-sa.com]
>> Subject: Re: set-cookie
>>
>> // Store products in the ServletContext
>> getServletContext().setAttribute("products", products);
>>
>> Presumably, if you store something in the context, it is because you
>> want to retrieve it later (or else, what's the point he ?).
>> Now, Tomcat has no way to know when you'll come back to retrieve it, so
>> it has to create a session to store this.
>
> Nope, that's not it (but I don't know what is, yet). Attributes stored in
> a ServletContext have a webapp, not session, scope; no session is needed
> here, and nothing needs to be communicated between the client and server
> to retrieve them.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
>
--
View this message in context:
http://old.nabble.com/set-cookie-tp28639362p28641797.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
