glassfish
  1. glassfish
  2. GLASSFISH-17032

WARNING: StatefulContainerbuilder instantiated store

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1.1_b11
    • Fix Version/s: 3.1.1_b12
    • Component/s: logging
    • Labels:
      None

      Description

      Deployed my EAR on GFv3.1.1_b11 and got the following warning in the log:

      [#|2011-07-13T14:51:45.993+0200|WARNING|glassfish3.1.1|javax.enterprise.system.container.ejb.com.sun.ejb.containers.builder|_ThreadID=21;_ThreadName=Thread-2;|StatefulContainerbuilder instantiated store: org.glassfish.ha.store.adapter.file.FileBackingStore@1d664; ha-enabled: false ==> BackingStoreConfiguration{clusterName='null', instanceName='null', storeName='ProblemDetectionWizardBean-85888938631430210-BackingStore', shortUniqueName='85888938631430210', storeType='file', maxIdleTimeInSeconds=-1, relaxVersionCheck='null', maxLoadWaitTimeInSeconds=0, baseDirectoryName='C:\glassfish3\glassfish\domains\domain1\session-store\ProblemDetectionWizardBean-85888938631430210', keyClazz=interface java.io.Serializable, valueClazz=class org.glassfish.ha.store.util.SimpleMetadata, synchronousSave=false, typicalPayloadSizeInKiloBytes=0, vendorSpecificSettings={start.gms=false, async.replication=true, key.transformer=com.sun.ejb.base.sfsb.util.SimpleKeyGenerator@1787f9b, local.caching=true, value.class.is.thread.safe=true, broadcast.remove.expired=false}}|#]

      If this is my fault (what I do not assume) it should tell me what my fault is.

      I am reporting this as a critical bug as it is a WARNING – and WARNINGs are for critical bugs, don't they?
      If this is not my fault, it should tell me what I shall do against this problem.

      If this problem is not in any case related to my workstation, it should possibly not log as a WARNING as it might be a GF bug instead then?

        Activity

        Hide
        marina vatkina added a comment -

        It's INFO message in 3.2.

        Show
        marina vatkina added a comment - It's INFO message in 3.2.
        Hide
        mkarg added a comment -

        Why not making in FINE? I mean, what shall an administrator learn from that message?

        Show
        mkarg added a comment - Why not making in FINE? I mean, what shall an administrator learn from that message?
        Hide
        Mahesh Kannan added a comment -

        This was fixed in b12

        Show
        Mahesh Kannan added a comment - This was fixed in b12

          People

          • Assignee:
            Mahesh Kannan
            Reporter:
            mkarg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: