OPSM Requesting More Than 1000 Serial Numbers At A Time Results In Session Time Out (Doc ID 1929970.1)

Last updated on APRIL 08, 2016

Applies to:

Oracle Pedigree and Serialization Manager - Version 1.2 and later
Information in this document applies to any platform.

Symptoms

On :  1.2 version, OPSM System Setup

When using SerialGenRequestServiceAMService webservice to generate serial numbers from OPSM, no issues when the request size is less than or equal to 1000, but when increasing the size beyond 1000
a timeout occurs.  

Note: Screen shots of config from EM are uploaded.
Note: Sequential serial type is used but may switch to Random serial type.


Time out

Actual Error
 in the Serial Number Cache Configuration:

line= self.fp.readline()
File "C:\Python27\Lib\socket.py", line 428, in readline
data = recv(1)
timeout: timed out


Steps
The issue can be reproduced at will with the following steps:
1. Configuration in Enterprise Manager / OPSM as per example below
2. Set Serial Commit Size to 1000 or more

General

Enpoint Enabled: Enabled
REST Enabled: False
WSDN Enabled: True
Metadata Exchange Enabled: True
Endpoint Test Enabled: True
Maximum Request Size: -1
Unit of Maximum Request Size: Bytes
JMS Request Queue Connection Factory Name: weblogic.jms.XAConnectionFactory
JMS Request Queue Name: oracle.j2ee.ws.server.async.Default

---

Maintain System Parameters

Owning Source System Default: OPSM
Source System Precedence: Owning Source System
Serial Type Default: SGTIN-96
Use Serial Ranges Default: unchecked

Generate Tab

Allow Lot Creation: unchecked
Serial Commit Size 1000

Business Impact
The issue has the following business impact:
Due to this issue, users cannot avoid timeout for OPSM serial commit size 1000 or more

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms