Expand my Community achievements bar.

Proxy issue with social componentes in internal used setup

Avatar

Level 1
Level 1
11/3/16 10:00:58 AM

Hello,

we are using AEM 6.1. and facing the following issue:

Some social components are not useable - an error occures or nothing happens, when called.

For example, in the author instance calling <servername&port>/content/community-components/en/reviews.html

creates just an gray page with nothing in it. In the error-log an unbelievable long error is printed:

03.11.2016 17:37:46.160 *ERROR* [10.203.81.38 [1478191066124] GET /content/community-components/en/comments.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
java.lang.IllegalArgumentException: Expected mime type application/octet-stream but got text/html. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

...

     The Host is not resolvable.

 

...

 <b>URL: </b><script type="text/javascript">break_line("<solr-server&port>/solr/collection1/select?q=%2B%28parent_id_s%3A%22%2Fcontent%2Fcommunity-components%2Fen%2Fcomments%2Fjcr%3Acontent%2Fcontent%2Fcomments%22%29+%2Bbase_type_s%3Asocial%2Fcommons%2Fcomponents%2Fcomments%2Fcomment&amp;start=0&amp;rows=0&amp;fq=%7B%21cost%3D100%7Dreport_suite%3Amongo&amp;wt=javabin&amp;version=2");</script><br />

...

Caused by: com.fasterxml.jackson.databind.JsonMappingException: Expected mime type application/octet-stream but got text/html. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

 

 

Analyses show that the call of the components tries to use our proxy, even though the proxy-config is disabled AND the Solr-Server is on the "No Proxy For" list in OSGI (Day Commons HTTP).

The Solr and MongoDB instanz can be found in our internal network and there is no need to search them elsewhere.

This issue only occures on your author instance - the publishers are doing fine.

Does anyone have an idea who to solve this issue?

Thank you in advance.

Views

1.1K

Replies

4
Sign in to like this content

Total Likes

Translate
Translate
4 Replies

Avatar

Level 9
Level 9
11/3/16 11:45:33 AM

Hi,

We're looking into it.

In the meantime, what platform service packs and Communities feature packs are installed?

The latest is SP3 and FP5.  See Deploying Communities.

- JK

Views

1.0K

Replies

3
Sign in to like this content

Total Likes

Translate
Translate

Avatar

Level 9
Level 9
11/3/16 12:21:47 PM
In response to JK_Kendall

Hi,

If it's happening to some, but not all, components in the components guide, then it likely has nothing to do with the proxy.

Two things

  1. there was a bug early on for the Reviews component having a wrong resourceType.  This should be fixed if you install the latest feature pack (FP) on all AEM instances.
  2. posting content using Communities components is intended for the publish environment, not author. 

Let us know whether or not you have the answer you need.

 -JK

Views

1.0K

Replies

0
Sign in to like this content

Total Likes

Translate
Translate

Avatar

Level 1
Level 1
11/4/16 12:06:06 AM
In response to JK_Kendall

JK Kendall wrote...

Hi,

We're looking into it.

In the meantime, what platform service packs and Communities feature packs are installed?

The latest is SP3 and FP5.  See Deploying Communities.

- JK

 

Hi,

we are running AEM 6.1. 0 SP2 with FP3.

JK Kendall wrote...

Hi,

If it's happening to some, but not all, components in the components guide, then it likely has nothing to do with the proxy.

Two things

  1. there was a bug early on for the Reviews component having a wrong resourceType.  This should be fixed if you install the latest feature pack (FP) on all AEM instances.
  2. posting content using Communities components is intended for the publish environment, not author. 

Let us know whether or not you have the answer you need.

 -JK

 

On the Community Components Testpage (.../content/community-components/en.html) on the author, the following components are not working and delivering blank pages:

  1. Calendar
  2. Comments
  3. Forum
  4. Reviews
  5. Review summary

On our created Pages the (not-changed) comments-component prints the above decribed error on the page.

Of Course we do not want to create user generated content on the author. Creating a page with the comments-component on it and always seeing the error just drives our authors a bit crazy :)

One could create a page with comments and "blind" publish it - the comments are working on the publishers.

We are checking to possibility of deploying the latest FP. This is done rather quick and without much trouble in our experience - could you confirm this experience? 

Thanks!

Views

1.0K

Replies

1
Sign in to like this content

Total Likes

Translate
Translate

Avatar

Level 9
Level 9
11/7/16 5:16:02 PM
In response to joe_schwichow

Hi,

I apologize, I did not complete comprehend your last post.

Earlier, it was a problem with the reviews component, and there was a known bug that should be fixed if you installed the latest feature pack.

Did you try upgrading?  Did you have any problems?  I wouldn't expect that you would.

I am really surprised at the blank pages, even for FP3.  The only thing that comes to mind is if your window is below a certain threshhold in width, then the components appear below the index of components.  If you're using a desktop monitor, then make the window wider and you should see the components move up to be to the right of the index.

Please let us know how you're doing.

- JK

Views

1.0K

Replies

0
Sign in to like this content

Total Likes

Translate
Translate