Forum Stats

  • 3,853,853 Users
  • 2,264,287 Discussions
  • 7,905,483 Comments

Discussions

<Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is availab

2743340
2743340 Member Posts: 5
edited Sep 17, 2014 2:41AM in WebLogic Portal

I am trying to set-up a cluster, I have installed my Weblogic Portal 10.3.2 and SQL server DB on two different machines & every thing is configured properly as per my knowledge.

but when I am trying to start my managed node on remote machine, getting out of sync error continuously as shown below

<Sep 6, 2014 4:42:02 PM IST> <Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is available. Remote L2 caches will be out of sync.>

<Sep 6, 2014 4:42:07 PM IST> <Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is available. Remote L2 caches will be out of sync.>

<Sep 6, 2014 4:42:13 PM IST> <Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is available. Remote L2 caches will be out of sync.>

<Sep 6, 2014 4:42:18 PM IST> <Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is available. Remote L2 caches will be out of sync.>

<Sep 6, 2014 4:42:24 PM IST> <Error> <Security> <BEA-000000> <Commit events are not broadcast because no JMS Transport is available. Remote L2 caches will be out of sync.>

NOTE: I am able to connect my DB using java utils.dbping [MSSQLSERVER4|MSSQLSERVERB] <db username> <db user password> DB_Host:Port/Db_name on both physical machines.

is there any workaround to fix this, as I am not able to by-pass this error, and fails to start my managed node on remote machine.

Thanks

Punit

2743340

Best Answer

  • User10656774-Oracle
    User10656774-Oracle Member Posts: 52 Employee
    Answer ✓

    Hello,

    Notes from MOS :

    This is an issue which is observed due to the RDBMS security store configuration issue. In order to sync the data in RDBMS security store, WLS uses JMS topic for transport, which is not being observed in this case and thus this error. The solution is to configure the JMS topic as per the documentation reference provided above. However this message is ideally not an error message but a mere warning message. Thus as part of code fix we have delivered a patch for WLS, to change the severity of this message from "ERROR" to "WARNING". This patch can be downloaded using My Oracle Support portal using:

    Bug number : 13459424

    Patch ID : NF9G


    Emmanuel

    27433402743340

Answers

  • User10656774-Oracle
    User10656774-Oracle Member Posts: 52 Employee
    Answer ✓

    Hello,

    Notes from MOS :

    This is an issue which is observed due to the RDBMS security store configuration issue. In order to sync the data in RDBMS security store, WLS uses JMS topic for transport, which is not being observed in this case and thus this error. The solution is to configure the JMS topic as per the documentation reference provided above. However this message is ideally not an error message but a mere warning message. Thus as part of code fix we have delivered a patch for WLS, to change the severity of this message from "ERROR" to "WARNING". This patch can be downloaded using My Oracle Support portal using:

    Bug number : 13459424

    Patch ID : NF9G


    Emmanuel

    27433402743340
  • 2743340
    2743340 Member Posts: 5

    Thanks Emm

    After applying the patch NF9G, issue is resolved for me.

    Also we need to enable(check) a parameter "Anonymous Admin Lookup Enabled"

    under: Home-->Domain-->Sercurity-->Anonymous Admin Lookup Enabled

    Thanks,

    Punit

This discussion has been closed.