[jboss-jira] [JBoss JIRA] (WFLY-3144) Session replication doesn't work as expected

[Martin Kouba (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954640#comment-12954640 ] 

Martin Kouba commented on WFLY-3144:
------------------------------------

For the record: I was able to reproduce the problem with cURL and forged JSESSIONID.
                
> Session replication doesn't work as expected
> --------------------------------------------
>
>                 Key: WFLY-3144
>                 URL: https://issues.jboss.org/browse/WFLY-3144
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: CDI / Weld, EJB
>    Affects Versions: 8.0.0.Final
>            Reporter: Tomas Remes
>            Assignee: Stuart Douglas
>         Attachments: translator.zip
>
>
> I am experimenting with quite simple Stateful SessionScoped bean  ( see org.jboss.weld.tests.clustering.translator.TranslatorControllerBean from attached reproducer) and actually there's not any specific exception, but the behavior is at least weird. I haven't tried with plain EJB so far. Reproducible by following steps:
> 1. Run first node with "/bin/standalone.sh -c standalone-ha.xml"
> 2. Run second node with "./bin/standalone.sh -c standalone-ha.xml -Djboss.socket.binding.port-offset=100 -Djboss.node.name=second"
> 3. Build and deploy attached reproducer
> 4. Open 127.0.0.1:8080/translator in your browser and translate something.
> 5. Open 127.0.0.1:8180/translator and note that number of translated sentences is not replicated correctly. 
> This works correctly in EAP. I am running with default standalone-ha configuration on oracle's 1.7.0_45 jdk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira