Expand my Community achievements bar.

SOLVED

Cq 5.4-Dispatcher config issues...

Avatar

Level 3

Hi ,

When i want to configure my cq5.4-dispatcher with IIS server ,i did the initial files placing(dispatcher.any and ini ..etc files).

So here i want to add my dispatcher flush to cq5 right..While hitting test connection im getting error..i mean connection has not been made with my port iis server 1020.

When i use localhost:1020/server.txt....it is showing server text info correctly but when im using this path http://localhost:1020/dispatcher/invalidate.cache getting error..

In the replication we will specify the IIS server port only right?

Can anyone help me on this..Is there any other modification required for /dispatcher/invalidate.cache detection by the url mentioned above..

Sony C.

1 Accepted Solution

Avatar

Correct answer by
Level 10

This confirms request is reaching IIS. Are you configuring IIS first time?  Can you enable debug logs & send your configuration details. 

View solution in original post

6 Replies

Avatar

Level 3

Hi Smacdonald and Sham,

Here i am getting the error while hit the test connection after i hit for dispatcher flush... http://localhost:1020/dispatcher/invalidate.cache

Replication test to http://localhost:1020/dispatcher/invalidate.cache

22.10.2013 02:28:02 - Create new HttpClient for Dispatcher Flush
22.10.2013 02:28:02 - * HTTP Version: 1.1
22.10.2013 02:28:02 - adding header: CQ-Action:Test
22.10.2013 02:28:02 - adding header: CQ-Handle:/content
22.10.2013 02:28:02 - adding header: CQ-Path:/content
22.10.2013 02:28:02 - deserialize content for delivery
22.10.2013 02:28:02 - No message body: Content ReplicationContent.VOID is empty
22.10.2013 02:28:02 - Sending GET request to http://localhost:1020/dispatcher/invalidate.cache
22.10.2013 02:28:02 - sent. Response: 400 Bad Request
22.10.2013 02:28:02 - Replication (TEST) of /content not successful. Conversation follows
22.10.2013 02:28:02 - ------------------------------------------------
22.10.2013 02:28:02 - Sending message to localhost:1020
22.10.2013 02:28:02 - >> GET /dispatcher/invalidate.cache HTTP/1.0
22.10.2013 02:28:02 - >> CQ-Action: Test
22.10.2013 02:28:02 - >> CQ-Handle: /content
22.10.2013 02:28:02 - >> CQ-Path: /content
22.10.2013 02:28:02 - >> Content-Length: 0
22.10.2013 02:28:02 - >> Content-Type: application/octet-stream
22.10.2013 02:28:02 - --
22.10.2013 02:28:02 - << HTTP/1.1 400 Bad Request
22.10.2013 02:28:02 - << Content-Type: text/html; charset=us-ascii
22.10.2013 02:28:02 - << Server: Microsoft-HTTPAPI/2.0
22.10.2013 02:28:02 - << Date: Mon, 21 Oct 2013 20:58:02 GMT
22.10.2013 02:28:02 - << Connection: close
22.10.2013 02:28:02 - << Content-Length: 334
22.10.2013 02:28:02 - << 
22.10.2013 02:28:02 - << <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
22.10.2013 02:28:02 - << <HTML><HEAD><TITLE>Bad Request</TITLE>
22.10.2013 02:28:02 - << <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
22.10.2013 02:28:02 - << <BODY><h2>Bad Request - Invalid Hostname</h2>
22.10.2013 02:28:02 - << <hr><p>HTTP Error 400. The request hostname is invalid.</p>
22.10.2013 02:28:02 - << </BODY></HTML>
22.10.2013 02:28:02 - Message sent.
22.10.2013 02:28:02 - ------------------------------------------------
22.10.2013 02:28:02 - Replication (TEST) of /content not successful.


Replication test failed
Bad Request

Before hitting do we need to create any folder structure in application server??

If yes, can you pls elaborate..

Sony C

Avatar

Level 10

Also provide dispatcher.log details at the time of test connection

Avatar

Level 3

Hi,

Please find the dispatcher logs when i hit the test connection.....

2013-10-28 05:30:45 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 2
2013-10-28 05:31:21 ::1 POST /ajax/bz - 1020 - ::1 Mozilla/5.0+(Windows+NT+6.1;+rv:23.0)+Gecko/20100101+Firefox/23.0 404 0 2 2
2013-10-28 05:31:45 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 3
2013-10-28 05:32:45 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 2
2013-10-28 05:33:45 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 3
2013-10-28 05:33:51 ::1 POST /ajax/bz - 1020 - ::1 Mozilla/5.0+(Windows+NT+6.1;+rv:23.0)+Gecko/20100101+Firefox/23.0 404 0 2 2
2013-10-28 05:34:46 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 3
2013-10-28 05:35:46 127.0.0.1 GET /dispatcher/invalidate.cache - 1020 - 127.0.0.1 Jakarta+Commons-HttpClient/3.1 404 0 2 2
2013-10-28 05:36:21 ::1 POST /ajax/bz - 1020 - ::1 Mozilla/5.0+(Windows+NT+6.1;+rv:23.0)+Gecko/20100101+Firefox/23.0 404 0 2 3

 

Please review it.

Thanks,

Sony C

Avatar

Correct answer by
Level 10

This confirms request is reaching IIS. Are you configuring IIS first time?  Can you enable debug logs & send your configuration details. 

Avatar

Level 10

This is all discussed in this AEM topic in detail:

http://dev.day.com/docs/en/cq/5-4/deploying/dispatcher.html

Be sure to read this topic in this AEM link:

"INVALIDATING DISPATCHER CACHE FROM THE AUTHORING ENVIRONMENT"

Hope this helps...

Avatar

Level 10

What is the error you are getting?