Seeing the Error "Unexpected error occurred while processing the updates" during deployment of API Proxy

Google Cloud Apigee
1

We are seeing the below error during deployment of one of our API Proxies:

The revision is deployed and traffic can flow, but flow may be impaired. Unexpected error occurred while processing the updates.

Can someone please help on this issue ?

2
  1. Checked the MP logs and found the following exception:
2016-07-21 01:22:52,551 Apigee-Main-12 ERROR MESSAGING.RUNTIME - Application.sync() : sync error for MyTestProxy and revision 7 
2016-07-21 01:22:52,552 Apigee-Main-12 ERROR MESSAGING.RUNTIME - Application.sync() : Actual Error 
com.apigee.kernel.exceptions.spi.UncheckedException: Unexpected error occurred while processing the updates 
at com.apigee.entities.AbstractConfigurator.throwUncheckedException(AbstractConfigurator.java:280) ~[config-entities-1.0.0.jar:na] 
at com.apigee.entities.AbstractConfigurator.handleUpdate(AbstractConfigurator.java:136) ~[config-entities-1.0.0.jar:na] 
at com.apigee.messaging.runtime.Application.handleUpdate(Application.java:217) ~[message-processor-1.0.0.jar:na] 
... 
Caused by: java.lang.NullPointerException: null 
at com.apigee.util.SimpleTokenizer.setText(SimpleTokenizer.java:64) ~[util-1.0.0.jar:na] 
at com.apigee.util.SimpleTokenizer.<init>(SimpleTokenizer.java:50) ~[util-1.0.0.jar:na] 
at com.apigee.accesscontrol.IP4AddressRange.<init>(IP4AddressRange.java:41) ~[access-control-1.0.0.jar:na] 
at com.apigee.steps.accesscontrol.AccessControlStepDefinition.setAccessControlRules(AccessControlStepDefinition.java:122) ~[access-control-1.0.0.jar:na] 
at com.apigee.steps.accesscontrol.AccessControlStepDefinition.handleAdd(AccessControlStepDefinition.java:88) ~[access-control-1.0.0.jar:na] 
at com.apigee.entities.AbstractConfigurator.handleUpdate(AbstractConfigurator.java:125) [config-entities-1.0.0.jar:na]
...

  1. The exception indicated that the cause for the deployment error is a NullPointerException while setting the Access Control Rule.

  2. Looking further into the stack trace, I noticed that the IP Address range initialisation seems to be failing.

  3. This gave me an idea to check if there’s an issue with Access Control Policy in the API Proxy

  4. Went through the Access Control Policy and checked each of the IP addresses and found that o ne of the IP addresses had an incorrect value as shown below:

<SourceAddress mask="32">1182.X.X.X</SourceAddress>

Modified the above line as follows:

<SourceAddress mask="32">182.X.X.X</SourceAddress>

Note: Used ‘X’ for masking the actual IP address.

Undeployed and deployed the API Proxy again. Deployment happened successfully without any issues.

1 Like
3

the error happened when deployed with below ACL. Cannot find in documentation this is wrong .

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AccessControl async="false" continueOnError="false" enabled="false" name="ACblockaccess">
    <DisplayName>AC.blockaccess</DisplayName>
    <Properties/>
    <IPRules noRuleMatchAction="Deny"/>
</AccessControl>