Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: Mercury
-
Fix Version/s: None
-
Component/s: API
-
Labels:None
-
Environment:
aml-distribution-service-war-1.0.1-RC1.war
aml-ui-merchant-gwt-2.9.1-RC1.war
ops-scripts-3.0.0-BETA1-bin.zip
aml-ui-reseller-gwt-2.9.1-RC2.war
smb-ear-2.9.1-RC1.ear
aml-data-tool-2.9.1.jar
bidmgr-distribution-2.9.1-RC1-bin.tar.gz
aml-sapi-2.9.0-RC2.war
merchant-api-secure-1.0.1-RC1.war
taxonomy-api-secure-1.0.1-RC1.war
budget-api-secure-1.0.1-RC1.war
deployment-api-secure-1.0.1-RC1.war
api-docs-1.0.1-RC1-yj.war
api-docs-1.0.1-RC1.war
yahoo-japan-credentials-api-secure-1.0.1-RC1.war
aml-reporting-api-secure-1.0.1-RC1.war
aml-oauth-provider-1.0.2-RC1.war
qos-service-1.0.2-RC1.war
aml-java-rsa-keygen-tool-1.0.2-RC1.jaraml-distribution-service-war-1.0.1-RC1.war aml-ui-merchant-gwt-2.9.1-RC1.war ops-scripts-3.0.0-BETA1-bin.zip aml-ui-reseller-gwt-2.9.1-RC2.war smb-ear-2.9.1-RC1.ear aml-data-tool-2.9.1.jar bidmgr-distribution-2.9.1-RC1-bin.tar.gz aml-sapi-2.9.0-RC2.war merchant-api-secure-1.0.1-RC1.war taxonomy-api-secure-1.0.1-RC1.war budget-api-secure-1.0.1-RC1.war deployment-api-secure-1.0.1-RC1.war api-docs-1.0.1-RC1-yj.war api-docs-1.0.1-RC1.war yahoo-japan-credentials-api-secure-1.0.1-RC1.war aml-reporting-api-secure-1.0.1-RC1.war aml-oauth-provider-1.0.2-RC1.war qos-service-1.0.2-RC1.war aml-java-rsa-keygen-tool-1.0.2-RC1.jar
Description
Order stuck in Processing state in case long Primary destination URL which is deployed through API
Steps
1. Create a Merchant
2. Deploy an order with long primary destination url (2048 charcters)
Expected Behavior
Order should be deployed successfully .
Actual Behavior
Order stuck in processing , exceptions observed in jboss.
1:35:24,293 DEBUG [JdbcTemplate] Executing prepared SQL statement [insert into mms_common.campaigns (accountID, advertID, businessFunctionID, locationID, customerDisplayURL, customerDestinationURL, localeName, distribution) select a.id, ?, ?, ?, ?, ?, ?, ? from mms_common.accounts a where a.bpID = ? on duplicate key update customerDisplayURL = ?, customerDestinationURL = ?]
11:35:24,296 WARN [AdMaxDeploymentServiceImpl] Error while processing Campaigns... 9525fcbc-70f0-4051-87b1-bfe979f7b511_10004_1_867
org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [insert into mms_common.campaigns (accountID, advertID, businessFunctionID, locationID, customerDisplayURL, customerDestinationURL, localeName, distribution) select a.id, ?, ?, ?, ?, ?, ?, ? from mms_common.accounts a where a.bpID = ? on duplicate key update customerDisplayURL = ?, customerDestinationURL = ?]; Data truncation: Data too long for column 'customerDestinationURL' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'customerDestinationURL' at row 1
at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:101)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:602)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:811)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:867)
Note :
Realm - qa2(orange)
Kindly find the attached jboss log.
