AEM servlet not render in publisher instance

Avatar

Avatar
Level 1
sajithv
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
sajithv
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
sajithv
Level 1

10-06-2020

I have followed this tutorial to create a form to submit data to SlingAllMethodsServlet . It works fine with the author instance. Once I published the page It shows the blank page in publisher instance.

 

aem-01.png

 

aem-2.png

I have installed the AEM 6.2 in ubuntu 14.04 machine. To create the above form I have used the templates & components. This is the error logs print when render the publisher instance.

10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse sent. Response: 200 OK10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse ------------------------------------------------
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse Sending message to localhost:4503
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse >> GET /bin/receive?sling:authRequestLogin=1 HTTP/1.0
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse >> Action: Internal Poll
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse >> Path: 
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse >> Handle: 
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse --
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse << HTTP/1.1 200 OK10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse << Date: Wed, 10 Jun 2020 17:30:55 GMT10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse << X-Content-Type-Options: nosniff10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse << Content-Type: application/octet-stream10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse << Content-Length: 32
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse Message sent.
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse ------------------------------------------------
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse Reverse replication successful.
10.06.2020 23:00:55.463 *INFO* [sling-default-1297-com.day.cq.replication.impl.ReverseReplicator.2114] com.day.cq.replication.Agent.publish_reverse Fetched 0 contents from http://localhost:4503/bin/receive?sling:authRequestLogin=1 since null

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
Ravi_Pampana
MVP

Likes

202 likes

Total Posts

247 posts

Correct reply

77 solutions
Top badges earned
Establish
Contributor
Shape 1
Ignite 5
Ignite 3
View profile

Avatar
Establish
MVP
Ravi_Pampana
MVP

Likes

202 likes

Total Posts

247 posts

Correct reply

77 solutions
Top badges earned
Establish
Contributor
Shape 1
Ignite 5
Ignite 3
View profile
Ravi_Pampana
MVP

10-06-2020

Hi,

 

As above said please check whether all the required code is installed and bundles are active in publisher. Also, the logs which you are shared are not having details they are just replication info logs. 

 

Check the view source if there are any exceptions and also check the if there are any permissions need to be granted in publisher as author you will login with admin and will have full access but accessing via publisher we will access with anonymous user.

 

Hope this helps !

Answers (8)

Answers (8)

Avatar

Avatar
Boost 50
Employee
surabhikatiyar
Employee

Likes

68 likes

Total Posts

46 posts

Correct reply

18 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Boost 50
Employee
surabhikatiyar
Employee

Likes

68 likes

Total Posts

46 posts

Correct reply

18 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile
surabhikatiyar
Employee

11-06-2020

Please check if the template & component are present on the publisher instance or not. The page has the sling:resourceType which maps to the template.

For making the template & component available over the publish instance, either

1. package from the author and deploy on publish or 

2. maven build deploy on publish instance or

3. replicate the template & component from author crx/de

 

If either the template or component is not present on the publisher instance, you will get the blank page.

Once you get all of the above, please check the system user and the permission for the respective servlet bundle, if you are using it.

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

487 likes

Total Posts

1,049 posts

Correct reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

10-06-2020

Agree with all, I think you have missed installing the packages in publish. 

Avatar

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile
ArpitVarshney
MVP

10-06-2020

Hi @sajithv 

 

  • You might have missed publishing or deploy all the custom code written for this component which contains your java, JSP, client lib. Just validate your changes by logging as admin in publish instance.
  • Just validate if the content got successfully replicated after authoring this component.

Regards,

Arpit

Avatar

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile

Avatar
Boost 5
Level 3
manising
Level 3

Likes

20 likes

Total Posts

19 posts

Correct reply

7 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile
manising
Level 3

11-06-2020

Hello @sajithv 

 

The most probable cause is that your servlet bundle is not installed on the publisher. Please ensure the following:

 

1. The node you created has sling:resourceType defined. It should have the value you mentioned in the servelt

2. Ensure your bundle is installed in the publisher and is in Active state

Avatar

Avatar
Boost 5
Level 2
vishakhav2
Level 2

Likes

10 likes

Total Posts

11 posts

Correct reply

4 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 3
View profile

Avatar
Boost 5
Level 2
vishakhav2
Level 2

Likes

10 likes

Total Posts

11 posts

Correct reply

4 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 3
View profile
vishakhav2
Level 2

10-06-2020

Hi,

Looks like you are checking reverse replication logs instead of replication.

Check your replication queue and do a dry run.

Post that you can check if your bundles are active and error.logs for system user error or component, servlet related.

 

Thanks

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

648 likes

Total Posts

608 posts

Correct reply

240 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

648 likes

Total Posts

608 posts

Correct reply

240 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

10-06-2020

@sajithv, this might be either a system user not set up correctly or scripts and content packages are not deployed to your publish instance. Before jumping straight to conclusions, let's have a look at your /crx-quickstart/logs/error.log file. 

Most of the time the /crx-quickstart/logs/error.log file will provide you will supportively stack traces that explains to you what the problem is. Whether this is a user not set up, a servlet throwing errors, or maybe templates and components cannot be resolved, the /crx-quickstart/logs/error.log usually provides you with great information. 

Once you found your issue, you can work on the fix. I hope my tip helped. 

Avatar

Avatar
Boost 1
Level 1
vasuk71036062
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
vasuk71036062
Level 1

Like

1 like

Total Posts

1 post

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
vasuk71036062
Level 1

10-06-2020

May be You may miss creating service user or check permission for service user which you are using to retrieve data .

Avatar

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
berliant
Employee

10-06-2020

From the author package manager, you need to replicate packages that were deployed via maven.