Getting Search registration failed Errors - After upgrade WEM from 8.5 to Latest cumulative Path

Hi All,

Recently we have upgraded WEM to Latest Cumulative Patch with SP1, After this upgrade Management Endpoint Suspending Continously with Search Registration failed errors. I tried to skip item and resume it. but agian going to suspended mode.

Please help to resolve this issue.

Thanks
Jayaram

com.vignette.as.client.exception.ApplicationException: 09/10/2015 09:00:30:385, Error 0 (Unknown), Message 026-120-0004: Search registration failed at com.vignette.as.client.exception.ApplicationException.getOne(ApplicationException.java:252) at com.vignette.as.server.event.AsSearchRegListener.consume(AsSearchRegListener.java:189) at com.vignette.as.server.event.AsEventManager.fireAsEvent(AsEventManager.java:155) at com.vignette.as.server.event.AsEventManager.fireEvent(AsEventManager.java:71) at com.vignette.as.endpoints.vctd.AppServiceHandler.fireEvent(AppServiceHandler.java:1630) at com.vignette.as.endpoints.vctd.AppServiceHandler.dispatchMOEvent(AppServiceHandler.java:611) at com.vignette.as.endpoints.vctd.AppServiceHandler.processManagedObject(AppServiceHandler.java:520) at com.vignette.as.endpoints.vctd.AppServiceHandler.processItem(AppServiceHandler.java:251) at com.vignette.cms.endpoints.vctd.DeploymentHandlerInstance.processItem(DeploymentHandlerInstance.java:49) at com.vignette.cms.endpoints.vctd.DeployerBase.callHandlerChain(DeployerBase.java:553) at com.vignette.cms.endpoints.vctd.DeployerBase.deployItem(DeployerBase.java:485) at com.vignette.cms.endpoints.vctd.RecordDeployer.deployItem(RecordDeployer.java:291) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.deployItem(JobProcessor.java:856) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.processAutoJob(JobProcessor.java:640) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.access$1100(JobProcessor.java:33) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$AutoJobProcessingThread.processWork(JobProcessor.java:158) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$ProcessingThread.run(JobProcessor.java:52) Nested exception is: com.vignette.util.VgnRuntimeException: parsing error at com.vignette.as.server.pluggable.search.solr.SolrIndex.processIndex(SolrIndex.java:380) at com.vignette.as.server.pluggable.search.solr.SolrIndex.indexItem(SolrIndex.java:170) at com.vignette.as.server.pluggable.search.AbstractSearchIndex.indexContentInstance(AbstractSearchIndex.java:1480) at com.vignette.as.server.pluggable.search.AbstractSearchIndex.registerContentInstance(AbstractSearchIndex.java:374) at com.vignette.as.server.event.AsSearchRegListener.onManagedObjectUpdate(AsSearchRegListener.java:398) at com.vignette.as.server.event.AsSearchRegListener.consume(AsSearchRegListener.java:158) at com.vignette.as.server.event.AsEventManager.fireAsEvent(AsEventManager.java:155) at com.vignette.as.server.event.AsEventManager.fireEvent(AsEventManager.java:72) at com.vignette.as.endpoints.vctd.AppServiceHandler.fireEvent(AppServiceHandler.java:1631) at com.vignette.as.endpoints.vctd.AppServiceHandler.dispatchMOEvent(AppServiceHandler.java:611) at com.vignette.as.endpoints.vctd.AppServiceHandler.processManagedObject(AppServiceHandler.java:520) at com.vignette.as.endpoints.vctd.AppServiceHandler.processItem(AppServiceHandler.java:251) at com.vignette.cms.endpoints.vctd.DeploymentHandlerInstance.processItem(DeploymentHandlerInstance.java:49) at com.vignette.cms.endpoints.vctd.DeployerBase.callHandlerChain(DeployerBase.java:553) at com.vignette.cms.endpoints.vctd.DeployerBase.deployItem(DeployerBase.java:485) at com.vignette.cms.endpoints.vctd.RecordDeployer.deployItem(RecordDeployer.java:291) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.deployItem(JobProcessor.java:856) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.processAutoJob(JobProcessor.java:640) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.access$1100(JobProcessor.java:33) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$AutoJobProcessingThread.processWork(JobProcessor.java:159) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$ProcessingThread.run(JobProcessor.java:52) Nested exception is: org.apache.solr.common.SolrException: parsing error at org.apache.solr.client.solrj.impl.XMLResponseParser.processResponse(XMLResponseParser.java:143) at org.apache.solr.client.solrj.impl.XMLResponseParser.processResponse(XMLResponseParser.java:104) at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:384) at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181) at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117) at com.vignette.as.server.pluggable.search.solr.SolrIndex.indexMetadata(SolrIndex.java:442) at com.vignette.as.server.pluggable.search.solr.SolrIndex.processIndex(SolrIndex.java:355) at com.vignette.as.server.pluggable.search.solr.SolrIndex.indexItem(SolrIndex.java:171) at com.vignette.as.server.pluggable.search.AbstractSearchIndex.indexContentInstance(AbstractSearchIndex.java:1480) at com.vignette.as.server.pluggable.search.AbstractSearchIndex.registerContentInstance(AbstractSearchIndex.java:376) at com.vignette.as.server.event.AsSearchRegListener.onManagedObjectUpdate(AsSearchRegListener.java:398) at com.vignette.as.server.event.AsSearchRegListener.consume(AsSearchRegListener.java:158) at com.vignette.as.server.event.AsEventManager.fireAsEvent(AsEventManager.java:155) at com.vignette.as.server.event.AsEventManager.fireEvent(AsEventManager.java:72) at com.vignette.as.endpoints.vctd.AppServiceHandler.fireEvent(AppServiceHandler.java:1631) at com.vignette.as.endpoints.vctd.AppServiceHandler.dispatchMOEvent(AppServiceHandler.java:611) at com.vignette.as.endpoints.vctd.AppServiceHandler.processManagedObject(AppServiceHandler.java:520) at com.vignette.as.endpoints.vctd.AppServiceHandler.processItem(AppServiceHandler.java:251) at com.vignette.cms.endpoints.vctd.DeploymentHandlerInstance.processItem(DeploymentHandlerInstance.java:49) at com.vignette.cms.endpoints.vctd.DeployerBase.callHandlerChain(DeployerBase.java:553) at com.vignette.cms.endpoints.vctd.DeployerBase.deployItem(DeployerBase.java:485) at com.vignette.cms.endpoints.vctd.RecordDeployer.deployItem(RecordDeployer.java:291) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.deployItem(JobProcessor.java:856) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.processAutoJob(JobProcessor.java:640) at com.vignette.cms.deployment.epagent.dagent.JobProcessor.access$1100(JobProcessor.java:33) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$AutoJobProcessingThread.processWork(JobProcessor.java:159) at com.vignette.cms.deployment.epagent.dagent.JobProcessor$ProcessingThread.run(JobProcessor.java:52) Caused by: java.lang.Exception: really needs to be response or result. not:html at org.apache.solr.client.solrj.impl.XMLResponseParser.processResponse(XMLResponseParser.java:134) ... 26 more

Find more posts tagged with

Comments

Qutubuddin

Most probably a communication issues between the WEM and Search.

Potential reason

<![if !supportLists]>· <![endif]>Search is Down or not respond (some issue on solar JVM). (Try restarting Solr)

<![if !supportLists]>· <![endif]>IP has changed (happens a lot to me on my local environments, if I need to get in and out of VPN) (Try restarting everything in your env).

<![if !supportLists]>· <![endif]>Port is blocked (Firewall issue)

Qutubuddin Saifuddin
Architect I America Services Organization

Phone: (732) 354 4423
Mobile: (732) 397 7951

Website: www.opentext.com

This email message is confidential, may be privileged, and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing orreproducing it. If the addressee cannot be reached or is unknown to you, please inform the sender by return email and delete this email message and all copies immediately.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Thursday, September 10, 2015 2:13 AM
To: eLink Recipient
Subject: Getting Search registration failed Errors - After upgrade WEM from 8.5 to Latest cumulative Path

Getting Search registration failed Errors - After upgrade WEM from 8.5 to Latest cumulative Path

Posted byjayaram.p@qu.edu.qa (Ponnusamy, Jayaram) On 09/10/2015 02:07 AM

Hi All,

Please help to resolve this issue.

Thanks
Jayaram

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

jponnu

Hi Qutub,

There is no connectivity issue and SOLR is running fine. We are facing this issue after installed the Latest cumulative Patch.

This issue is occuring in all Environment (DEV, STAGE & PROD) where we done the Patch install.

Management Endpoint is suspending with Search Registration Failed error

Delivery Endpoint is Not responding.

We upgraded from WEM 8.5 to WEM 8.5 SP1+Cumulative (2015-08-06 16:57:14 GMT)

Anyone have used this patch and working fine?

Seems to be some SOLR configuration is required to complete the upgradation but that is not covered in Release NOtes. Please help to resolve this issue.

Thanks

Jayaram

Daniel_Bock

Quoted Jayaram Ponnusamy on 10/06/2015 09:52 AM:

Hi Qutub,

There is no connectivity issue and SOLR is running fine. We are facing this issue after installed the Latest cumulative Patch.

This issue is occuring in all Environment (DEV, STAGE & PROD) where we done the Patch install.

Management Endpoint is suspending with Search Registration Failed error

Delivery Endpoint is Not responding.

We upgraded from WEM 8.5 to WEM 8.5 SP1+Cumulative (2015-08-06 16:57:14 GMT)

Anyone have used this patch and working fine?

Seems to be some SOLR configuration is required to complete the upgradation but that is not covered in Release NOtes. Please help to resolve this issue.

Thanks

Jayaram

Hi Jararam -

Which version were you previously on before installing the cumulative? The base WEM 8.5? We saw similar errors a few times during our WEM 8.5 upgrade however they all seem to caused by things we were doing with Motion.

Thanks,

Dan

jponnu

Hi Dan,

We upgraded from Base 8.5 to this cumulative. and We havent used Motion. Whenever content items get create/delete/update, endpoint going to suspended mode with Search registration failed error.

As of now, I have disabled search Listener in configconsole to avoid endpoint suspencen, after resolving this issue only can enable it again.

Anyone please share their experience about WEM upgradation from WEM 8.5 to this cumulative (WEM 8.5 SP1+Cumulative (2015-08-06 16:57:14 GMT))

Thanks

Jayaram

Timothy Grimes

Hi Jayaram,

I work with Dan so I'm speaking from the same experience as him. When we were having the issues, it does appear they happened when we were using Motion but I don't think it was directly related to that. I think it was more related to us either not fully configuring external Solr, messing up when configuring external Solr, or having external Solr offline. Hopefully that helps. I suggest verifying you can access your external Solr's admin page from your browser and run a query manually in there.

-Tim