6 Replies Latest reply on Aug 27, 2013 12:20 PM by 996510

    "Current MDS session does not define correct transaction key" problem

    Veronica
      Hi,

      I have a brand new done-by-the-book installation of 11.1.1.7 SOA Suite and OSB.

      Now everytime the Admin Server wakes up, and when I try to make changes in the EM (say, security->credentials->oracle.wsm.security->sign-csf-key) I get this message in the logs:
      <2013-04-10 20:06:23 CEST> <Warning> <oracle.mds> <BEA-000000>
      <Invocation of flushChanges in the current 
      MDS session does not define correct transaction key>
      Broke lines for readibility. It may not be a 100% accurate translation since I get it as localized message.

      I sometimes also get this:
      m_connection-jpss null
      Have anyone encounter this? How should I debug this problem?
        • 1. Re: "Current MDS session does not define correct transaction key" problem
          remmer
          Same here - did you have any resolution?
          • 2. Re: "Current MDS session does not define correct transaction key" problem
            1003623
            Same here with Oracle WebCenter 11.1.1.7 :
            <Warning> <oracle.mds> <BEA-000000> <Un appel à flushChange sur la session MDS en cours n'indique pas la clé de transaction appropriée>
            • 3. Re: "Current MDS session does not define correct transaction key" problem
              Peter Flies-Oracle

              I'm also seeing this issue. I see this bug open, but no resolution yet.

               

              • 4. Re: "Current MDS session does not define correct transaction key" problem
                M.Fevzi Korkutata

                I am facing with the same problem. But this problem is not major.

                 

                <Jul 9, 2013 7:03:54 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:03:55 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:03:56 PM EEST> <Warning> <oracle.adf.view.rich.render.RichRenderer> <ADF_FACES-00007> <Attempt to synchronized unknown key: viewportSize.>

                <Jul 9, 2013 7:03:56 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:03:56 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:03:58 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:03:58 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:03 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:03 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:03 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:04 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:06 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:07 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:08 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:08 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:08 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                <Jul 9, 2013 7:04:11 PM EEST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>

                • 5. Re: "Current MDS session does not define correct transaction key" problem
                  User595592-Oracle

                  Facing the same problem.

                  Do you think reverting to 11.1.1.6 or 11.1.1.5 will help ?

                  • 6. Re: "Current MDS session does not define correct transaction key" problem
                    996510

                    This issue was not in 11.1.1.6 but its there in 11.1.1.7, In development environment SOA server, first deploy from Jdev, its works after that deployment itself hanging and not deploying beacuse of this issue, Please techies help this out ....