Re: An unexpected error has been detected by Java Runtime Environment:
Some helpful info on this error here - http://www.java-forums.org/eclipse/312-exception_access_violation-0xc005.html On Sat, 2010-04-24 at 13:48 -0700, krawls35 wrote: > Thank You for letting me know. How do I take it off and report to Tomcat > forum? You are not being funny but very helpful and I appreciate that. > > awarnier wrote: > > > > Not trying to be funny here, but should you not be reporting this to Sun > > (as mentioned in the crash messages), rather than to the Tomcat forum ? > > > > krawls35 wrote: > >> I received an error also last night. I couldn't figure out how to do my > >> own > >> post so I am hoping somebody will help me with my situation also. Here it > >> go: > >> EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6d8f9dac, pid=7016, > >> tid=6844 > >> # > >> # JRE version: 6.0_19-b04 > >> # Java VM: Java HotSpot(TM) Client VM (16.2-b04 mixed mode, sharing > >> windows-x86 ) > >> # Problematic frame: > >> # V [jvm.dll+0xf9dac] > >> # > >> # If you would like to submit a bug report, please visit: > >> # http://java.sun.com/webapps/bugreport/crash.jsp > >> # > >> > >> Tsirkin Evgeny-2 wrote: > >>> environment : > >>> Apache Tomcat/6.0.18 > >>> Solaris 9 64 bit > >>> jdk1.6.0_13 > >>> > >>> On one of the servers we are today getting constantly errors: > >>> An unexpected error has been detected by Java Runtime Environment. > >>> Here are some of those: > >>> > >>> --- > >>> # > >>> # An unexpected error has been detected by Java Runtime Environment: > >>> # > >>> # SIGBUS (0xa) at pc=0x7f4008b8, pid=2380, tid=121 > >>> # > >>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode > >>> solaris-sparc) > >>> # Problematic frame: > >>> # C [libc_psr.so.1+0x8b8] > >>> # > >>> # An error report file with more information is saved as: > >>> # /tmp/hs_err_pid2380.log > >>> # > >>> # If you would like to submit a bug report, please visit: > >>> # http://java.sun.com/webapps/bugreport/crash.jsp > >>> # > >>> > >>> --- > >>> # > >>> # An unexpected error has been detected by Java Runtime Environment: > >>> # > >>> # SIGBUS (0xa) at pc=0x78c0bf44, pid=11205, tid=615 > >>> # > >>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode > >>> solaris-sparc) > >>> # Problematic frame: > >>> # j > >>> java.net.URLStreamHandler.parseURL(Ljava/net/URL;Ljava/lang/String;II)V+0 > >>> # > >>> # An error report file with more information is saved as: > >>> # /tmp/hs_err_pid11205.log > >>> # > >>> # If you would like to submit a bug report, please visit: > >>> # http://java.sun.com/webapps/bugreport/crash.jsp > >>> # > >>> --- > >>> # > >>> # An unexpected error has been detected by Java Runtime Environment: > >>> # > >>> # SIGSEGV (0xb) at pc=0x7e34c17c, pid=23223, tid=5 > >>> # > >>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode > >>> solaris-sparc) > >>> # Problematic frame: > >>> # V [libjvm.so+0x74c17c] > >>> # > >>> # An error report file with more information is saved as: > >>> # /tmp/hs_err_pid23223.log > >>> # > >>> # If you would like to submit a bug report, please visit: > >>> # http://java.sun.com/webapps/bugreport/crash.jsp > >>> # > >>> --- > >>> The file which should contain the logs/dump (i.e. > >>> /tmp/hs_err_pid23223.log) > >>> are empty. > >>> Did anybody get experienced with such a thing? > >>> Thanks > >>> Evgeny > >>> > >>> > >> > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Clustering in tomcat
For session replication to happen in a cluster, all attributes stored in the session object should be serializable - that is why you are seeing the exception you see below. On Thu, 2008-10-30 at 03:40 -0700, kashif_tomcat wrote: > Thanks Filip... > > i have got out of that problem... after adding clustering port in iptable. > > now i am getting another exception and following is detail. > > > when i add tag in web.xml of my applicatoin and start > tomcat. then after login my application crashs and i get following exception > in logs. > > > 2008-10-30 21:19:43,812 INFO [com.vopium.controller.LoginController - > handleControllerRequest] - Exception during LoginProcess setAttribute: > Non-serializable attribute > com.framework.exceptions.BaseRunTimeException > at > org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1295) > at > org.apache.catalina.ha.session.DeltaSession.setAttribute(DeltaSession.java:567) > at > org.apache.catalina.ha.session.DeltaSession.setAttribute(DeltaSession.java:551) > at > org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130) > at > com.vopium.controller.LoginController.handleControllerRequest(Unknown > Source) > at > com.framework.controllers.BaseController.handleRequestInternal(Unknown > Source) > at > org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) > at > org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) > at > org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at com.vopium.portal.utilities.URLFilter.doFilter(Unknown Source) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.ha.session.JvmRouteBinderValve.invoke(JvmRouteBinderValve.java:209) > at > org.apache.catalina.ha.tcp.ReplicationValve.invoke(ReplicationValve.java:347) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) > at java.lang.Thread.run(Thread.java:619) > 2008-10-30 21:19:43,829 INFO [com.vopium.interceptors.SecurityInterceptor - > preHandle] - request.getRemoteAddr() 192.168.0.82 request.getRemoteHost() > 192.168.0.82 /vopium/dashboard.htm > 2008-10-30 21:19:43,830 INFO [com.vopium.interceptors.SecurityInterceptor - > preHandle] - Session Not Found So Redirecting to Login and requested uri is > /vopium/dashboard.htm > > > and when i don,t add tag in web.xml of my application then > application logins successfully but when tomcat 1 is down then session > doesn't move to tomcat 2 and at that time application crash with same > behavior and throws following msg in logs of tomcat 2 (catalina.out). > > > > 2008-10-30 20:34:51,126 INFO [com.vopium.interceptors.SecurityInterceptor - > preHandle] - request.getRemoteAddr() 192.168.0.82 request.getRemoteHost() > 192.168.0.82 /vopium/balanceandpaymentshistory.htm > 2008-10-30 20:34:51,127 INFO [com.vopium.interceptors.SecurityInterceptor - > preHan
Re: Sticky Session AND session duplication?
Hi Greg: Please see below for my comments. Regards Sanjeev On Thu, 2008-10-30 at 15:58 -0700, Greg Dick wrote: > Hi, > > I know that for typical web applications one of these approaches is > generally enough to achieve load balancing across nodes in a cluster, > but we here with an ICEfaces application would find it useful to do > both. Not sure if I understand this correctly, but neither of the above (Sticky Session AND session duplication) cater to load balancing in a cluster -> for that, you need to configure a load balancer in front of tomcat, something like apache webserver for example, that will field all incoming requests and then distribute them amongst the multiple servers in your cluster. Session duplication (or replication) is more to ensure that if a node in your cluster goes down, your client app does not lose its session state since the cluster has the state replicated on other nodes. Sticky session is to ensure that once a session is established on one server, all future requests will go to the same server. This is more for the purposes of efficiency. > Session duplication to ensure the spreading around of session > information, and sticky sessions to ensure all the blocking web > connections from a single user get directed to the same node, until that > node fails. An asynchronous ICEfaces application can have two > connections to a server from a browser at the same time and it wont do > to have these load balanced to separate nodes of the cluster. Can an ICEFaces application have two SESSIONS from the same browser? I do not know ICEFaces but I do not think it can, and having two connections is different from two sessions. If it is just two (or multiple) connections, and your cluster is setup for sticky session, then the request should only go the server that the browser is sticky with. > > Various sorts of documentation hint that these operations are mutually > exclusive and > we have found that it doesn't work in practice but we just wanted to > find if someone could either confirm that this is not supported, or that we > have our configuration wrong/understanding botched, or something. > > Any help would be appreciated. HTH! > Greg > > > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
