Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-141

Marshaller should start before Transport

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.0.0.BETA1
    • 4.0.0.ALPHA6
    • None
    • None

      Actually, just run the tests locally with some TRACE logging and there appears to be a race condition between the @Start phases of Transport and Marshaller:

      2009-07-23 12:08:12,300 5718 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-1,Infinispan-Cluster,localhost.localdomain-45973 Problems invoking command.
      java.lang.NullPointerException
      at org.infinispan.marshall.jboss.JBossMarshaller$2.initialValue(JBossMarshaller.java:87)
      ...
      2009-07-23 12:08:12,334 5752 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (main Cache local address is localhost.localdomain-45973
      2009-07-23 12:08:12,335 5753 DEBUG [org.infinispan.marshall.jboss.JBossMarshaller] (main Using JBoss Marshalling based marshaller.

      Basically, JGroups transport is starting before Marshaller whereas it should be the other way around. Currently, both start methods where using priority=10.

      Changing marshaller's priority to 9 appears to solve the issue

              rh-ee-galder Galder Zamarreño
              rh-ee-galder Galder Zamarreño
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: