com.roving.RovingServerException: Unexpected ContactServiceFailed

Member

com.roving.RovingServerException: Unexpected ContactServiceFailed

Hi,

      Below is the error i am getting from an activity  after  doing bulk add contacts ...Every thing was fine till last week..now suddenly it started giving us Error in the Response what could be the reason...?

 

com.roving.RovingServerException: Unexpected ContactServiceFailedToRespondException in RestClient.run. User Data:

42 REPLIES 42

We recently published an update on this in our last set of release notes in our TechBlog (http://techblog.constantcontact.com).  We are hopeful to have a full fix for this out in the next week or so.  You'll see updated release notes there when we get the fix to production.

Dave Berard
Senior Product Manager, Constant Contact

I have a client getting this error (slightly different from OP) when doing bulk upload of contacts:

 

com.roving.RovingServerException: Undexpected ContactServiceBadResponseException in ContactsAPIServicelmpl.processBadResponseEntity. User Data:

 

We are using the v1 API. They may be on the new version of the web. Is this error related, or is this something completely different? Has a fix been implemented yet?

Regular Participant

Dave,

 

We are experiencing the same error:  Received unhandled error from CC
com.roving.RovingServerException: Unexpected ContactServiceBadResponseException in ContactsAPIServiceImpl.processBadResponseEntity. User Data:

 

Do you have an expected date when this fix will be ran?  We are at a stand still until this is fixed.

 

Thank you.

All of these issues, if you're getting that error message, are related to our new Contact Management platform.  Internally, our API relies on a bulk import service which was designed for our old Contact Management system.  When we migrate an account to our new Contact Management platform, we occasionally are seeing performance issues which cause the imports to fail.  In full transparency, we're seeing a just under 1% error rate on imports.

 

We have been working hard to rewrite our entire batch processing service for imports.  We believe we are about 2-4 weeks from finishing that and rolling it out to resolve this issue for 100% of our developers.  Our initial performance testing has showed an over 600% increase in performance as well as 0% error rates. 

 

I know the 2-4 week timeline is very frustrating for accounts which are seeing failed imports.  We are trying to be very careful in rolling this out as we don't want to make the problem worse than the current one is.  For a good portion of our customers using the API, this is either a sporadic issue or a non-issue.  We don't want to roll out a fixt that isn't ready and increase that error rate from >1% to something larger.  We will post information as soon as we roll this fix out to production and confirm that it is both stable and resolves all these issues.

 

Thanks again for your patience and continued reporting of the issue.  We use the level of reporting we get to gauge priority like any software company and this has helped us to raise this up and get a solution moving quicker by getting this level of reporting. 

Dave Berard
Senior Product Manager, Constant Contact
Regular Participant

Thanks for the update. Does this affect importing contacts into Constant Contact using a CSV file?  Our work around is importing contacts using a CSV file. A large number of the contacts in the file are not added in Constant Contact.The file has all of the required information.  Is anyone else experiencing this problem that has RovingServerException error?  Thanks.

Regular Participant

Our client was able to upload via CSV without issue.

This issue only impacts imports through the API.  If your customers import through our UI, they should see no issues.  As mentioned earlier, the majority of API imports don't see any issues either with the error rate we're seeing being >1% now.  We are in the process of finishing up our last tests on our new rewrite of our import tools and we expect to have those rolled out to production in 2-4 weeks depending on final testing.  This should completely eliminate any of these issues you're seeing.

Dave Berard
Senior Product Manager, Constant Contact

Our own account is now experiencing this issue.

 

So when this fix is released, will it be contained in the v1 API code, or will it be all on your end? Will we have to do any rewrites of our integration, or will all of our existing code continue to function?

Fix is completely contained in our backend and will be transparent to developers.  Shouldn't have to make any changes.

Dave Berard
Senior Product Manager, Constant Contact

I got this error

com.roving.RovingServerException: Unexpected ContactServiceBadResponseException in ContactsAPIServiceImpl.processBadResponseEntity. User Data:

twice in a row for the same set of contacts. This does not seem like a coincidental occurence of hitting a 1% error. There must be a specific problem.

The error I see in the UI is "One contact was un-subscribed and could not be added to a list."

I didn't think adding a contact with an unsubscribed email address caused an issue in the past. Even so, I doubled checked the contacts and made sure none of them was unsubscribed. None of them were.

What's up with this?

I'm getting this exact same issue today. Need help. We were supposed to push out an email campaign today, and because of this failure, most of our contacts ended up getting removed from lists. I can't add them back now...

 

If it helps, it's not every bulk activity. I can't seem to find a link between the ones that do encounter this issue, though.

Hi,

 

I just replied to another, similar, thread, but this is also being caused by the issues we're having with the bulk upload service failing sometimes. We are hoping that changes we are releasing next Friday, in one week, will resolve most or all of these cases. I am truly sorry for the frustration this has caused.

 

Best Regards,

Shannon Wallace

Partner API Support Engineer

Regular Participant

In the post Shannon mentioned: "We are hoping that changes we are releasing next Friday, in one week, will resolve most or all of these cases".  I did not see that an update was done.  Was the fixed released on Friday 5/9 or was it delayed.  Thanks.

We ran into some delays while doing our final stage testing.  This is a big change and we didn't want to have any issues released which could be worse than the ones we were facing.  We got through our tests and cleared the release, but it was unfortunately very late on Friday night when we completed this and didn't want to release this over the weekend without anyone watching things real time. 

 

We are in the process of rolling this release out now.  Should see this completely in production and importing bulk activities correctly again by early afternoon EST.

Dave Berard
Senior Product Manager, Constant Contact
Regular Participant

We tried this morning to upload Contacts into Constant Contact via the API and it errored out. We did not recieve the RovingServer Exception error. The error we have is: "Error on sync: Error in sending request to Constant Contact (HTTP Status Code: 500"). Was the release finalized yesterday or is it still in progress? Still not able to upload contacts. Thanks.

Hi Terri,

 

We'd like to investigate this further. Could you send us your username, api key, and the data you sent over when the error occurred to webservices@constantcontact.com?

 

Thanks in advance.

 

Best Regards,

Shannon Wallace

Partner API Support Engineer

Regular Participant

Shannon,

 

We have multiple constant contact accounts for three different states. I sent an email to webservices this morning referencing the error we got concerning this problem for one of other constant contacts account where we are having the biggest problem. 

 

KH

Regular Participant

We now have multiple clients reporting the 500 internal server error. You guys need to get this fixed ASAP. They are at a standstill until this gets fixed. This is completely unacceptable now.

Hi Dave,

 

We have identified the problem and prioritized this issue to be fixed so that we can have it deployed as quickly as possible. This fix will be deployed as a Hotfix so that we can have it available as soon as it is ready rather than being required to wait for the next release. We should have an update tomorrow on the status of this issue for you.

 

I do want to offer my sincere apologies for this issue and I definitely understand that this is a major interruption for integrations and causing a significantly degraded experience for users of affected integrations. We are working to get it resolved as quickly as we can, and implementing additional advanced logging to allow us to address issues of this type more quickly in the future.

 

If you do have any questions for us, please feel free to reply to this post.

 

Sincerely,

Elijah G.
API Support Engineer

We released a Hot Fix late last night.  500 errors have dropped off to a very small amount, consistent with our normal volumes which are generally caused by very strange request payloads.  Also, we're now seeing 100% completion of jobs imported. 

 

Developers and customers should no longer be seeing jobs get partially completed, 500 errors on POST or any other strange behavior.  If you do see anything like this, please email us directly at webservices@constantcontact.com with your request payload and account username so we can look into your specific issue. 

 

Thanks again for your patience while we did these upgrades and rewrites.  Our apologies for all of the inconveniences and outages which came about as a result of this.

Dave Berard
Senior Product Manager, Constant Contact
Regular Participant

Error is still happening for me, I sent an email to webservices, activity id was a07e9bg4u81hv9bn4v6  

Developer Portal

View API documentation, code samples, get your API key.

Visit Page