Layer7 API Management

 View Only
  • 1.  Restman error when deploying api

    Posted Aug 02, 2019 10:27 AM
    We've recently installled a new gateway cluster. We publish apis on demand. When a try to deploy and api,  I get the following restman error:

    Error processing management request: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <l7:Item xmlns:l7="http://ns.l7tech.com/2010/04/gateway-management">
    <l7:Name>Bundle mappings</l7:Name>
    <l7:Type>BUNDLE MAPPINGS</l7:Type>
    <l7:TimeStamp>2019-08-02T10:05:54.040-04:00</l7:TimeStamp>
    <l7:Link rel="self" uri="https://localhost:8443/restman/1.0/bundle"/>
    <l7:Resource>
    <l7:Mappings>
    <l7:Mapping action="NewOrUpdate" errorType="InvalidResource" srcId="5b6f1a2f9d944460ad870fbd38caa99c" type="POLICY">
    <l7:Properties>
    <l7:Property key="ErrorMessage">
    <l7:StringValue>Error attempting to save or update the Policy with id = '5b6f1a2f9d944460ad870fbd38caa99c'. Message: Could not execute JDBC batch update; SQL [insert into policy (name, version, security_zone_goid, folder_goid, guid, internal_sub_tag, internal_tag, soap, policy_type, `xml`, goid) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; nested exception is org.hibernate.exception.LockAcquisitionException: Could not execute JDBC batch update</l7:StringValue>
    </l7:Property>
    </l7:Properties>
    </l7:Mapping>
    <l7:Mapping action="NewOrUpdate" errorType="InvalidResource" srcId="bf86f31b43313bf99a165a1f6d7740b4" type="SERVICE">
    <l7:Properties>
    <l7:Property key="ErrorMessage">
    <l7:StringValue>Error attempting to save or update the PublishedService with id = 'bf86f31b43313bf99a165a1f6d7740b4'. Constraint Violation: Could not execute JDBC batch update</l7:StringValue>
    </l7:Property>
    </l7:Properties>
    </l7:Mapping>
    </l7:Mappings>
    </l7:Resource>
    </l7:Item>

    Can anyone point to what we are doing wrong?

    ------------------------------
    Beth Currier
    ------------------------------


  • 2.  RE: Restman error when deploying api
    Best Answer

    Posted Aug 06, 2019 10:41 AM
    I found the problem. My setup includes dual gateway (dmz and internal) with portal option. When otk was installed on internal, under securezone - storage, the web api portal/storage was missing. When I copied that from different gateway cluster, all worked