[infinispan-issues] [JBoss JIRA] Commented: (ISPN-937) hotrod server state transfer problem during startup
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Thu Feb 24 05:28:41 EST 2011
[ https://issues.jboss.org/browse/ISPN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584360#comment-12584360 ]
Galder Zamarreño commented on ISPN-937:
---------------------------------------
Michal, just saw this and sounds a lot like what you're encountering - http://lists.jboss.org/pipermail/infinispan-dev/2011-February/007456.html
It seems like the root cause is the removal of FLUSH in the JGroups stacks (ISPN-83).
Can you take you use this https://github.com/infinispan/infinispan/blob/4.2.1.CR1/core/src/main/resources/jgroups-udp.xml file instead of the one shipped with Infinispan for the transport config? Just download it and point to it via -Djboss.infinispan.jgroups.config=
> hotrod server state transfer problem during startup
> ---------------------------------------------------
>
> Key: ISPN-937
> URL: https://issues.jboss.org/browse/ISPN-937
> Project: Infinispan
> Issue Type: Bug
> Components: Cache Server
> Affects Versions: 4.2.1.CR2
> Reporter: Michal Linhard
> Assignee: Galder Zamarreño
> Fix For: 4.2.1.FINAL
>
> Attachments: hotrod-server-stdout.txt, hotrodconsole-0.0.1-SNAPSHOT-bin.zip, infinispan.xml, server1.log, server2-stdout.log, server2.log
>
>
> This is something that happend to me when playing with hotrod servers.
> I've built infinispan distribution from source (mvn install -P distribution -DskipTests=true)
> unzipped infinispan-4.2.1.CR2-all.zip 2x to folders
> distro1
> distro2
> created 2 virtual ifaces
> 192.168.11.101 test1
> 192.168.11.102 test2
> ran
> distro1/bin/startServer.sh -r hotrod -l test1 -c /home/mlinhard/dev/projects/infinispan/issues/infinispan.xml
> distro2/bin/startServer.sh -r hotrod -l test2 -c /home/mlinhard/dev/projects/infinispan/issues/infinispan.xml
> ran demo-hotrod-console
> hotrodconsole-0.0.1-SNAPSHOT/bin/console.sh test1
> entered
> >put a a (which means put value "a" under key "a")
> the servers waited a bit and then server 2 wrote some errors to stdout (I guess after some timeout expired)
> client was still blocked, after some time produced
> ERROR: Invalid magic number. Expected a1 and received 50
> attaching
> - binary version of demo-hotrod-console (source: https://github.com/mlinhard/demo-hotrod-console)
> - server 2 stdout
> - infinispan.xml
> I tried this with 4.2.1.CR1 and it worked.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list