• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Do not receive notifications

Guest
May 21, 2013 May 21, 2013

Copy link to clipboard

Copied

Hi

We have ACS set up in one set of servers, running Tomcat, and the main webserver elsewhere, running Apache. We need the notifications sent to the webserver.


I have set the notifyURL to be correct and also the setting com.adobe.adept.fulfillment.customNotifyURL in fulfillment.conf

However we do not receive any notification POSTs on this URL (or anything at all, from ACS)

The Tomcat server can definitely see the URL and the URL is definitely correct. There are no firewall issues. The only thing is, it's a https URL. I have made sure that inbound and outbound port 443 is open on each set of servers. I have the URL set to log everything that hits it. I can go to the URL in a browser and this connection is logged but nothing from ACS is logged and nothing from any user's ADE either.

I can see in Tomcat's logs that the notification XML is apparently being sent (I can see the XML in the log)


However it never reaches the webserver. We really need the fulfillment XML !

Any suggestions?

Thanks

Views

1.1K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
May 22, 2013 May 22, 2013

Copy link to clipboard

Copied

LATEST

OK well thanks for the overwhelming response. I don't suppose anyone from Adobe actually reads this?

Anyway, the problem is that ACS doesn't seem able to send fulfillment notifications via https. Changing the URL to a http version solved the problem.

I eliminated a firewall as being at fault here, but what I haven't eliminated is whether Java or Tomcat are at fault rather than Adobe's completely bug-free software. In any case, using http instead of https solves the problem. Hope that's useful to anyone else who encounters this!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines