[ 
https://issues.apache.org/jira/browse/OWB-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256271#comment-13256271
 ] 

Martin Grotzke commented on OWB-646:
------------------------------------

This is the stacktrace from tomcat 7.0.8:

(Trying again to get simple formatting right :-))
{{
Daemon Thread ["http-bio-8082"-exec-4] (Suspended (entry into method 
fireRequestDestroyEvent in StandardContext))       
  StandardContext.fireRequestDestroyEvent(ServletRequest) line: 5819    
  StandardContextValve.invoke(Request, Response) line: 163      
  SessionTrackerValveTC7(SessionTrackerValve).invoke(Request, Response) line: 
126       
  StandardHostValve.invoke(Request, Response) line: 164 
  ErrorReportValve.invoke(Request, Response) line: 100  
  StandardEngineValve.invoke(Request, Response) line: 118       
  CoyoteAdapter.service(Request, Response) line: 383    
  Http11Processor.process(SocketWrapper<Socket>) line: 243      
  Http11Protocol$Http11ConnectionHandler.process(SocketWrapper<Socket>, 
SocketStatus) line: 188 
  Http11Protocol$Http11ConnectionHandler.process(SocketWrapper<Socket>) line: 
166       
  JIoEndpoint$SocketProcessor.run() line: 288   
  ThreadPoolExecutor$Worker.runTask(Runnable) line: 886 
  ThreadPoolExecutor$Worker.run() line: 908     
  TaskThread(Thread).run() line: 662    
}}

So the difference is that in this version the StandardContextValve.invoke 
invokes StandardContext.fireRequestDestroyEvent and in tomcat >= 7.0.22 
StandardHostValve.invoke does this, right?
                
> Failover does not work (again)
> ------------------------------
>
>                 Key: OWB-646
>                 URL: https://issues.apache.org/jira/browse/OWB-646
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Context and Scopes
>    Affects Versions: 1.1.3
>         Environment: Tomcat 7.0.22, OWB 1.1.3, memcached-session-manager 1.6.1
> Should be unrelated: MyFaces 2.1.6, CODI 1.0.3, ExtVal 2.0.5, Hibernate 
> 3.6.9, BVAL 0.3
>            Reporter: Thomas Andraschko
>            Assignee: Mark Struberg
>              Labels: Cluster, Failover, Replication, Tomcat
>             Fix For: 1.1.4
>
>         Attachments: OWB-646.patch
>
>
> Martin (from msm) and I created an test app for this issue last year: 
> https://github.com/magro/msm-sample-webapp/tree/openwebbeans and this was 
> fixed within OWB-523.
> However, if i upgrade the Tomcat to 7.0.22 or newer, the bean replication 
> does not work again.
> As you can see in this test app, the normal failover works (right input 
> field) but the bean failover (left input field) does not work.
> I tested several Tomcat version and 7.0.21 or older works without problems, 
> so the problem occured with Tomat 7.0.22.
> I don't know exactly if the problem is related to the OWB failover mechanism 
> or Tomcat :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to