2 Replies Latest reply: Mar 26, 2012 7:50 AM by 905535 RSS

    Error after OSM upgrade from 7.0.0 to 7.0.3

    905535
      Hi,

      We have recently upgraded OSM version from 7.0.0 to 7.0.3.

      From xslt we are calling createOrderBySpecification service over JMS(posting message on quequ : oracle/communications/ordermanagement/WebServiceQueue) .
      This is working functinality but after OSM upgrade this is not working for few orders(nothing is changed in code) and throwing following exception on weblogic server log:

      ####<21-03-2012 12:11:37 CET> <Error> <oms> <xxx> <osm_stcurr> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <oms-internal> <> <> <1332328297098> <BEA-000000> <ws.WebserviceJMSTransportSubstitute: Received message for unknown web service URI: [osm/wsapi]>


      In XSLT we are seeting URI as per follows:

      <xsl:variable name="void1" select="java:setStringProperty($outboundMessage, '_wls_mimehdrContent_Type', 'text/xml; charset=UTF-8')" />
      <xsl:variable name="void1" select="java:setStringProperty($outboundMessage, 'URI', 'osm/wsapi')" />

      Any idea how to resolve this issue?

      Regards,
      UJ
        • 1. Re: Error after OSM upgrade from 7.0.0 to 7.0.3
          user491422 - oracle
          In 7.0.0 there was a limitation on the number of requests to create orders that could be processed concurrently through the OSM WS JMS interface. This limit was imposed by internal limitations within WebLogic server.

          In 7.0.2 we introduced an enhancement to improve the concurrency of order creation requests submitted through the OSM WS JMS interface, that enhancement was largely transparent to clients submitting requests however there was a small problem with clients submitting wlsmimehdrContent_type and URI values if they were not formatted 100% correctly.

          This problem was corrected in patchsets available on 7.0.2 and 7.0.3 - the latest version of either releases' patchset should have this fix incorporated.

          So bottom line, if you are using a recent version of 7.0.3 (e.g. 7.0.3.5) then this problem should be resolved so if you are still hitting it then you should contact Oracle support.

          If you are not using a recent version of 7.0.3 then I suggest you use a recent one and retest.


          Brian.
          • 2. Re: Error after OSM upgrade from 7.0.0 to 7.0.3
            905535
            Hi Brian,

            Thanks for reply.

            We are using latest version of OSM but issue is not resolve.
            Now Oracle SR is raised for the same.
            Regards,
            UJ