Order gets stuck in processing state

If we are trying to deploy the order having Business Location who has the location aliases are more than group limit, it gets stuck in processing.

Steps:

1. Update the file, changes the AdGroup Limit to 50
~/apps/jboss-5.1.0.GA/server/tsa_messaging_node1/deploy/properties-service.xml

o com.thesearchagency.mms.admax.AdGroup.Limit=50

2.Re-bounce the jboss server.

3.Create order with Business location which have location alias more than 50 (QA 5 - State: California => Los Angeles County)

Actual result:

Snippet of JBoss log:

Order gets stuck in processing state and the Jboss log shows exception!

12:16:29,018 DEBUG [KeywordServiceImpl] Multi-lang support is: true and path for templates is :/usr/local/tsa/languageTemplates
12:16:29,018 DEBUG [LanguageTemplate] Geo-mod Broad keyword-location value: +discount +campground +Los +Angeles +County
12:16:29,018 DEBUG [KeywordServiceImpl] Multi-lang support is: true and path for templates is :/usr/local/tsa/languageTemplates
12:16:29,018 DEBUG [LanguageTemplate] Geo-mod Broad keyword-location value: +discount +campgrounds +Los +Angeles +County
12:16:29,138 WARN [AdMaxDeploymentServiceImpl] Error while processing Campaigns... cdb2f1ae-c758-4e6f-9c47-d3d39fc239db_10006_3108_3442
com.thesearchagency.core.smb.service.admaxdeployment.AdMaxDeploymentException: Number of adGroups exceeds limit: 50
at com.thesearchagency.core.smb.service.admaxdeployment.component.AdMaxDeploymentServiceImpl.processCampaign(AdMaxDeploymentServiceImpl.java:1222)
at com.thesearchagency.core.smb.service.admaxdeployment.component.AdMaxDeploymentServiceImpl.processCampaigns(AdMaxDeploymentServiceImpl.java:1046)
at com.thesearchagency.core.smb.service.admaxdeployment.component.AdMaxDeploymentServiceImpl.convertDeploymentRequest(AdMaxDeploymentServiceImpl.java:445)
at com.thesearchagency.core.smb.service.admaxdeployment.component.AdMaxDeploymentRequestMDB.handleDeployCampaignRequest(AdMaxDeploymentRequestMDB.java:178)
at com.thesearchagency.core.smb.service.admaxdeployment.component.AdMaxDeploymentRequestMDB.onMessage(AdMaxDeploymentRequestMDB.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
at sun.reflect.GeneratedMethodAccessor403.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Expected : Order shouldn't be deployed which is happening but as the order remains in processing state, it keeps on filling up the log. Instead we can ERROR it out after few retires.