Not able to connect to the API/APIC/Datapower gateway consoles from Docker Toolbox

Hello everyone,
I have installed the Docker toolbox with API Connect.
I started all the components individually and below is the output:

$ docker-compose ps

Name Command State Ports

apim /tini — /startup.sh Up

datapower /start.sh Up 443/tcp

esmaster /docker-entrypoint.sh /bin … Up 9200/tcp, 9300/tcp

ibmlogstash /bin/sh -c /startup.sh Up

ibmportal /root/tini — /root/start_ … Up

make-ssh-keys /bin/sh -c /genkey.sh Exit 0

microservice /bin/sh -c /usr/bin/app.sh … Up 8080/tcp

nginx /bin/sh -c /run.sh Up 0.0.0.0:443->443/tcp, 80/tcp

I have also edited the /etc/hosts file with the following:
192.1**.*.* apim ibmportal datapower microservice

However, I am still not able to connect to any of the the consoles (apic/apim not datapower).

which ip do I have to mention in the /etc/hosts file ? (I gave the ip v4 for the virtualbox which I got from the ipconfig command).

Please throw some light here from your experiences, not sure what am I doing wrong.

Thanks in Advance!

Related:

  • No Related Posts

Re: ACS server run error

I have problem with ACS server:

2016-06-06 08:30:48,527 ERROR [http–0.0.0.0-9080-14] acs.com.documentum.acs.sdi.servlet.ACS – [ACS_E_REQUEST_NOT_VALID] Request validation failed

com.documentum.acs.coordination.RequestValidationException: Attempt to use expired URL. URL creation date=’Wed Jun 01 09:51:45 ICT 2016′, current date=’Mon Jun 06 08:30:48 ICT 2016′, URL age=427143sec. allowed time-to-live=21600sec.

at com.documentum.acs.coordination.impl.RequestValidator.validateRequest(RequestValidator.java:82)

at com.documentum.acs.coordination.impl.ACSCoordinatorImpl.validateRequest(ACSCoordinatorImpl.java:327)

at com.documentum.acs.accessor.impl.DirectStorageService.retrieveContent(DirectStorageService.java:47)

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:113)

at com.documentum.acs.coordination.impl.ReadOrchestrator.execute(ReadOrchestrator.java:58)

at com.documentum.acs.sdi.servlet.ACS.doGet(ACS.java:229)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.documentum.osgi.http.service.impl.HttpService.service(HttpService.java:60)

at com.documentum.osgi.http.service.impl.HttpService.doGet(HttpService.java:39)

at com.documentum.osgi.servlet.BridgeServlet.doGet(BridgeServlet.java:43)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at com.documentum.osgi.filter.CORSFilter.doFilter(CORSFilter.java:31)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

2016-06-06 08:55:14,617 ERROR [http–0.0.0.0-9080-12] acs.com.documentum.acs.sdi.servlet.ACS – Failed request processing; request=ReadRequest: (acsUrl=”, signature=’utJfHm6rUsWVqGuIOn+xVhye1FmeDfBGmrfR8LhFa4NMWfkua0pD+6iNGN6m7EhrzfaEa8RPLP3u/MO5Z1xKlPuTNHmoJysIJlm+AtqzX6hSN5v/XKSw1bAWsn8YzMO+7bhM2MJI7lpy/tR/lWHxwMh7EyR/yRpf2Nw/g1r4qug=’, originationTime=1465178105, mimeType=’application/pdf’, transientDataDelimiter=’::’, transientData=’null’, isCompressionEnabled=false, isRecoveryMode=false, encryptionMode=EncryptionMode{allow}, objectId=’0902852381e3fb6c’, format=’pdf’, pageNumber=0, pageModifier=’null’, baseFilePath=’\hq-ecmfile-04ecm_fs_01DocumentumdataECM_REPO_PRODcontent_storage_040028523′, filePath=’80217987.pdf’, cacheId=’dKgEAgA==h3khgA==028523′, length=9107120, offset=0, contentId=null, is_fork=false)

com.documentum.acs.common.ACSException: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:127)

at com.documentum.acs.coordination.impl.ReadOrchestrator.execute(ReadOrchestrator.java:58)

at com.documentum.acs.sdi.servlet.ACS.doGet(ACS.java:229)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.documentum.osgi.http.service.impl.HttpService.service(HttpService.java:60)

at com.documentum.osgi.http.service.impl.HttpService.doGet(HttpService.java:39)

at com.documentum.osgi.servlet.BridgeServlet.doGet(BridgeServlet.java:43)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at com.documentum.osgi.filter.CORSFilter.doFilter(CORSFilter.java:31)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:403)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:426)

at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:415)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:83)

at com.documentum.acs.transport.impl.ContentWriterHelper.print(ContentWriterHelper.java:180)

at com.documentum.acs.transport.impl.ContentWriterHelper.println(ContentWriterHelper.java:166)

at com.documentum.acs.transport.impl.ContentWriterHelper.copy(ContentWriterHelper.java:118)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeMultipleRangeContent(DefaultContentWriter.java:220)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeRangeContent(DefaultContentWriter.java:171)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeContent(DefaultContentWriter.java:93)

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:116)

… 25 more

Caused by: java.net.SocketException: Software caused connection abort: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)

at java.net.SocketOutputStream.write(SocketOutputStream.java:159)

at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:724)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:748)

at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:127)

at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:559)

at org.apache.coyote.Response.doWrite(Response.java:594)

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:398)

… 38 more

2016-06-06 09:21:06,928 ERROR [http–0.0.0.0-9080-12] acs.com.documentum.acs.sdi.servlet.ACS – Failed request processing; request=ReadRequest: (acsUrl=”, signature=’x6RcAivmvHQVyETwLrAu+la7U0RsC3AtLS1OaxDiSrfzpOYeOns9hVqBtoYASszI6Huv9II2jplVlCsW1Y0yWHL632z/Y37YzpQUEDcxoVg2mMa5wsLCztu9OwRxzBYMxEeCYzUsVGZaZQ67IFUYsdMoQPToLH7a5WKo8qA0MRY=’, originationTime=1465179659, mimeType=’application/pdf’, transientDataDelimiter=’::’, transientData=’null’, isCompressionEnabled=false, isRecoveryMode=false, encryptionMode=EncryptionMode{allow}, objectId=’0902852381cb59f4′, format=’pdf’, pageNumber=0, pageModifier=’null’, baseFilePath=’\hq-ecmfile-04ecm_fs_01DocumentumdataECM_REPO_PRODcontent_storage_040028523′, filePath=’8017573d.pdf’, cacheId=’dKgEAgA==PVcXgA==028523′, length=6185523, offset=0, contentId=null, is_fork=false)

com.documentum.acs.common.ACSException: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:127)

at com.documentum.acs.coordination.impl.ReadOrchestrator.execute(ReadOrchestrator.java:58)

at com.documentum.acs.sdi.servlet.ACS.doGet(ACS.java:229)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.documentum.osgi.http.service.impl.HttpService.service(HttpService.java:60)

at com.documentum.osgi.http.service.impl.HttpService.doGet(HttpService.java:39)

at com.documentum.osgi.servlet.BridgeServlet.doGet(BridgeServlet.java:43)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at com.documentum.osgi.filter.CORSFilter.doFilter(CORSFilter.java:31)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:403)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:426)

at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:415)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:83)

at com.documentum.acs.transport.impl.ContentWriterHelper.print(ContentWriterHelper.java:180)

at com.documentum.acs.transport.impl.ContentWriterHelper.println(ContentWriterHelper.java:166)

at com.documentum.acs.transport.impl.ContentWriterHelper.copy(ContentWriterHelper.java:118)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeMultipleRangeContent(DefaultContentWriter.java:220)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeRangeContent(DefaultContentWriter.java:171)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeContent(DefaultContentWriter.java:93)

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:116)

… 25 more

Caused by: java.net.SocketException: Software caused connection abort: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)

at java.net.SocketOutputStream.write(SocketOutputStream.java:159)

at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:724)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:748)

at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:127)

at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:559)

at org.apache.coyote.Response.doWrite(Response.java:594)

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:398)

… 38 more

2016-06-06 09:48:41,507 ERROR [http–0.0.0.0-9080-12] acs.com.documentum.acs.sdi.servlet.ACS – Failed request processing; request=ReadRequest: (acsUrl=”, signature=’aauiAQNmd+oIqONv5fOI+YBKePO1dIohhKlcnXgpS9ve2HXBDYD+NCvmve4Avi1JCLzV7GfCHtmcOxIZZDZxhnf9uHcclQOAw6XVD0Nk7DMtrM8DNmqB2VrRNPp9GH+K3kS6TECi3KJNz753Klcg3oHLk7IPANZBZMkgwHtAFLc=’, originationTime=1465181311, mimeType=’application/pdf’, transientDataDelimiter=’::’, transientData=’null’, isCompressionEnabled=false, isRecoveryMode=false, encryptionMode=EncryptionMode{allow}, objectId=’0902852381f2d143′, format=’pdf’, pageNumber=0, pageModifier=’null’, baseFilePath=’\hq-ecmfile-05hq-ecmfile-05DocumentumdataECM_REPO_PRODcontent_storage_050028523′, filePath=’802e168.pdf’, cacheId=’dKwEAgA==aOECgA==028523′, length=9200419, offset=0, contentId=null, is_fork=false)

com.documentum.acs.common.ACSException: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:127)

at com.documentum.acs.coordination.impl.ReadOrchestrator.execute(ReadOrchestrator.java:58)

at com.documentum.acs.sdi.servlet.ACS.doGet(ACS.java:229)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.documentum.osgi.http.service.impl.HttpService.service(HttpService.java:60)

at com.documentum.osgi.http.service.impl.HttpService.doGet(HttpService.java:39)

at com.documentum.osgi.servlet.BridgeServlet.doGet(BridgeServlet.java:43)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at com.documentum.osgi.filter.CORSFilter.doFilter(CORSFilter.java:31)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:403)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:426)

at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:415)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)

at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:83)

at com.documentum.acs.transport.impl.ContentWriterHelper.print(ContentWriterHelper.java:180)

at com.documentum.acs.transport.impl.ContentWriterHelper.println(ContentWriterHelper.java:166)

at com.documentum.acs.transport.impl.ContentWriterHelper.copy(ContentWriterHelper.java:118)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeMultipleRangeContent(DefaultContentWriter.java:220)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeRangeContent(DefaultContentWriter.java:171)

at com.documentum.acs.transport.impl.DefaultContentWriter.writeContent(DefaultContentWriter.java:93)

at com.documentum.acs.coordination.impl.ReadOrchestrator.executeSimple(ReadOrchestrator.java:116)

… 25 more

Caused by: java.net.SocketException: Software caused connection abort: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)

at java.net.SocketOutputStream.write(SocketOutputStream.java:159)

at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:724)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:748)

at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:127)

at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:559)

at org.apache.coyote.Response.doWrite(Response.java:594)

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:398)

… 38 more

I is using Documentum 7.2 on window server 2008 R2

Any help would be greatly appreciated.

Thank you so much in advance!

Thai.

Related:

  • No Related Posts

SEP14RU1 – Memory Exploit Mitigation breaks IE11

I need a solution

So we are in the process of upgrading our clients from SEP12RU6MP7 to SEP14RU1.

After the initial restart when installing the new version, IE11 is not starting up anymore.
Error Message:

iexplore.exe
The application was unable to start correctly (0xc0000005). Click OK to close the application

Event Log:

Faulting application name: iexplore.exe, version: 11.0.9600.18838, time stamp: 0x59e1b492
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000004e0a8a
Faulting process id: 0x2140
Faulting application start time: 0x01d3650967e64262
Faulting application path: C:Program FilesInternet Exploreriexplore.exe
Faulting module path: unknown
Report Id: a59c52d1-d0fc-11e7-aae2-ecb1d7725227

When disabling the Memory Exploit Mitigation policy, everything works fine again.
The policy even was set to “Set the protection action for all techniques to log only”. Bummer.

So, what’s the issue here?

0

Related:

  • No Related Posts

Link to folder workflow issue

Hi Team,

I am facing below issue in a BPM Workflow using a Link to Folder auto activity.

Please help me to get resolve the issue.

2017-11-02 17:20:10,026 DEBUG [http–0.0.0.0-9080-25] [com.documentum.fc.client.impl.session.PooledSessionFactory] – Session{id=3, iid=884, serial=3, docbase=eimsdocbase, user=dmadmin, serversession=01057cb680013f41} returned to pool

2017-11-02 17:20:10,027 ERROR [http–0.0.0.0-9080-25] [com.documentum.mthdservlet.DoMethod] – Exception invoking com.documentum.bpm.method.WQInitialization.

java.lang.NullPointerException

at com.documentum.bpm.method.WQInitialization.executeJob(WQInitialization.java:112)

at com.documentum.bpm.Utils.GenericJobMethod.execute(GenericJobMethod.java:50)

at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)

at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

Related:

Re: dmc_rps_master_work_order for operation “RETAINER_PROMOTION” created by auto dmc_rps_PromotionJob can not initiate partitioning

Hi, Experts,

We are running RPS 6.7.3 patch 9 in Content server 7.1. The jobs for RPS are running well since the JMS HA setting issue was fix. However, the backlog for the documennt to be process is piled up since the object dmc_rps_master_work_order for operation “RETAINER_PROMOTION” created by auto dmc_rps_PromotionJob can not initiate partitioning therefore stuck on routed but processing forever as shoun below.

parent_id : 0000000000000000

start_process_time : nulldate

last_update_time : 9/22/2017 10:24:07

number_items_to_process : 0

number_items_processed : 0

number_items_successful : 0

number_items_failed : 0

number_child_wo_created : 0

number_child_wo_processed : 0

number_items_skipped : 0

master_workorder_id : 0800….802354fc

processing_status : ROUTED

completion_status : PROCESSING

is_complete : F

is_terminated : F

number_items_actioned : 0

operation_name : RETAINER_PROMOTION

number_items_warned : 0

run_count : 0

all_children_successful : T

start_time : 9/22/2017 10:22:57

route_time : 9/22/2017 10:24:07

wait_time : nulldate

return_time : nulldate

end_time : nulldate

route_duration : 0

process_duration : 0

wait_duration : 0

processor_host :

partitioning_status : NOT_INITIALIZED

estimated_percent_complete : 0

estimated_total_to_process : 18372

total_processed : 0

total_skipped : 0

partitioner_module_name : com.documentum.workorder.partitioner.Wor

kOrderCollectionPartitioner

total_actioned : 0

total_failed : 0

total_succeeded : 0

total_warned : 0

suboperation_names []: <none>

suboperation_details []: <none>

work_order_number : 25130

total_duration : 0

operation_origin : AUTOMATED

marked_for_delete_wo_id : 0000000000000000

STEM ATTRIBUTES

r_object_id : 0800….802354fc

r_object_type : dmc_rps_master_work_order

The Promotion job is completed successfuly as expected. However, each run created a new master work order object like above. The JMS tracing shows no error for the promotion:

10:22:57,097 INFO [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Started job at 2017/09/22 10:22:57

10:22:57,229 DEBUG [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Getting session from super for repository – docbasename…

10:22:57,229 DEBUG [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Entered doExecute() in:

10:22:57,229 DEBUG [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Entered PromotionMethod::promote at 2017/09/22 10:22:57

10:22:58,557 DEBUG [http–0.0.0.0-9080-2] com.documentum.rpm.services.RpmPromotionService – promotion query: select a.r_object_id,s.object_name, s.r_is_virtual_doc,s.r….

10:24:07,902 INFO [http–0.0.0.0-9080-2] com.documentum.rpm.services.RpmPromotionService – Master work order 0800….802354fc created and routed to promote all eligible retainers.

10:24:07,903 DEBUG [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Exiting PromotionMethod::promote at 2017/09/22 10:24:07

10:24:07,903 DEBUG [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Exiting doExecute() in:

10:24:07,903 INFO [http–0.0.0.0-9080-2] com.documentum.rps.retention.aging.PromotionMethod – Finished job at 2017/09/22 10:24:07

However, the promotion of retainers from the WDK records application works fine where we could search and select objects to promote manually (. 100 items a batch by the page maximum displayable)

I do not understand the workorder partitioning process but noticed that there are 18372 objects (retainers) to be processed. By default, that number would be divided by 1000 (as default configured) for the dmc_rps_work_order items. The workorder actually worked for once after I put the total number down and then stopped again.

So, how to push this partitioning process?

Not sure if we need to clean all the failed and processing master work order to make a new master order to work. Since the patch we are running does not include the retainer monitor job. Is there a way to clean the pending/processing promtion master orders?

Any comments and insights are appreciated.

Related:

Getting an error while running a Documentum job.

Hello All,

While running a Documentum job I am getting following error:

Error:

DfException:: THREAD: http–0.0.0.0-21367-1; MSG: [DM_GROUP_E_PROTECTED_ROLE_PRIV]error: “The requesting application is not privileged to use role (dmc_rec_escalated_write).”; ERRORCODE: 100; NEXT: DfException:: THREAD: http–0.0.0.0-21367-1; MSG: [DM_DCNFG_E_RIGHTS_NOT_AUTHORIZED]error: “Client ‘dfc_PXeaXbUbL2DLz0KhFQGXOK5yjgga’ is not authorized to use role ‘dmc_rec_escalated_write’.”; ERRORCODE: 100; NEXT: DfException:: THREAD: http–0.0.0.0-21367-1; MSG: [DM_OBJ_MGR_E_FETCH_FAIL]error: “attempt to fetch object with handle 04000000g###gA00 failed”; ERRORCODE: 100; NEXT: DfException:: THREAD: http–0.0.0.0-21367-1; MSG: [DM_DCNFG_E_RIGHTS_NOT_EXIST]error: “Could not find entry for client ‘dfc_PXeaXbUbL2DLz0KhFQGXOK5yjgga’ in the rights database.”; ERRORCODE: 100; NEXT: null

at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57

So I have done following to solve the same:

1- I added dfc.key=this above name of dfc client in dfc.properties of cs and could see while logging into DA that NO clients are there.

2- When I look to DA and go to Client right option and click on Manage clients I can’t see this mentioned client there.

3- Tried to backup dfc.keystore and it generated the new one, still the same error.

Could anyone please help me in same. Will be grateful to you.

Thanks,

R. Singh





Related:

  • No Related Posts

Re: Configuring Static Routes

Hi,

I am trying to configure a static route on an ECS appliance. I have found the following white paper: https://www.emc.com/collateral/white-paper/h15718-ecs-networking-bp-wp.pdf and created a file ifroute-public.repl:

admin@provo-blue:/etc/sysconfig/network> cat ifroute-public.repl

192.168.0.0 10.240.223.100 255.255.255.0 public.repl

I’ve also run sudo service network restart and yet the route is not in the local host routing table:

admin@provo-blue:/etc/sysconfig/network> netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

0.0.0.0 10.241.172.1 0.0.0.0 UG 0 0 0 public

10.241.172.0 0.0.0.0 255.255.255.0 U 0 0 0 public

127.12.7.0 0.0.0.0 255.255.255.0 U 0 0 0 docker0

169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 private.4

192.168.219.0 0.0.0.0 255.255.255.0 U 0 0 0 private

Could someone please let me know how I can add a persistent static route to an ECS appliance?

Related:

Configuring Static Routes

Hi,

I am trying to configure a static route on an ECS appliance. I have found the following white paper: https://www.emc.com/collateral/white-paper/h15718-ecs-networking-bp-wp.pdf and created a file ifroute-public.repl:

admin@provo-blue:/etc/sysconfig/network> cat ifroute-public.repl

192.168.0.0 10.240.223.100 255.255.255.0 public.repl

I’ve also run sudo service network restart and yet the route is not in the local host routing table:

admin@provo-blue:/etc/sysconfig/network> netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

0.0.0.0 10.241.172.1 0.0.0.0 UG 0 0 0 public

10.241.172.0 0.0.0.0 255.255.255.0 U 0 0 0 public

127.12.7.0 0.0.0.0 255.255.255.0 U 0 0 0 docker0

169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 private.4

192.168.219.0 0.0.0.0 255.255.255.0 U 0 0 0 private

Could someone please let me know how I can add a persistent static route to an ECS appliance?

Related:

Workflow task is not finished gracefully: socket write error

2017-07-05 12:08:43,063 ERROR [http-0.0.0.0-0.0.0.0-9080-2] [com.documentum.mthdservlet.DoMethod] – Exception invoking com.documentum.bpm.services.BPSIntegrationMethod.

ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:352)

at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:316)

at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)

at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)

at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)

at com.documentum.mthdservlet.MethodOutputStream.methodClose(Unknown Source)

at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.net.SocketException: Software caused connection abort: socket write error

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)

at java.net.SocketOutputStream.write(SocketOutputStream.java:159)

at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:724)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)

at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:1027)

at org.apache.coyote.Response.action(Response.java:190)

at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:347)

… 23 more

Related: