Path is DEAD between Branch SDWAN devices

Virtual Path is showing DEAD between the Branch SDWAN devices after adding a device as Secondary MCN and pushed the configuration.

You will see the following highlighted message getting incremented in ( SDWAN_Diagnostic logs ) :

Command: drop_counts

*****************************************************************************************************************************************

Index Count File Name Function Name Line # Reason text

————————————————————————————————————————————————————————-

1 3711 forward/virtual_path_service/crypto.c decrypted_receive_packet 1258 Failed to decrypt because path check fails

2 3205053 forward/hosted/ip_host_api.c iph_icmp_ttl_exceeded_handler 933 Received ICMP TTL exceeded, but not running trace route

3 10957819 forward/virtual_path_service/path.c store_reliable 3550 Free reliable packets on dead Virtual_Path

4 20108355 forward/virtual_path_service/path.c valid_receive_index 4344 Packet rwl and lwl does not match the Virtual_Path_id and path_num of the TRP packet

In the SDWAN_Diagnostic logs, you will also see that, the same IP address X.X.X.138 is mapped on both WANLLINK 1 and WANLINK 2:

*****************************************************************************************************************************************

Command: mcn_wl_table

*****************************************************************************************************************************************

Number of entries in table: 12

Number of entries in tree: 12

* Wan Link Wan Link Proxy IP UDP

ID Name Address Port

————————————————————————-

1 10 WANLINK 1 X.X..X.138 4980

1 11 WANLINK 2 0.0.0.0 4980

Paths dump:

—————————————————————-

Azure-France-Central-Slovakia-2-Barca-KB 0 X.X.X.4 X.X.X.138 4980 4980 Defau 172.16.2.1 0.0.0.0 READY NOT_READY 15 10 XXXX-WL-1 WANLINK 1 50 50 aes128 TRUE 0

Azure-France-Central-Slovakia-2-Barca-KB 1 X.X.X.4 X.X.X.138 4980 4980 Defau 172.16.2.1 0.0.0.0 READY NOT_READY 15 11 XXXX-WL-1 WANLINK 2 50 50 aes128 TRUE 0

**

Related:

  • No Related Posts

FAQ: NetScaler SD-WAN Installation and Upgrade

Q: Can I downgrade a NetScaler SD-WAN 4000/5000 appliance to an earlier software release?

A: A NetScaler SD-WAN 4000/5000 appliance cannot be downgraded to an earlier release. The appliance should have to be factory reset and provisioned again from scratch.

For example, if an appliance is running:

Version 7.3.1 it will have the following files for each component:

SD-WAN 4000/5000 7.3.1-48.418829

  • SD-WAN version: 7.3.1-48.418829;
  • SVM version: 10.1.120.1105.e;
  • NS version: 10.1.129.1105.e;
  • XS 6.0 build 50762 with Hotfixes XS60E001, 003, 010, 014, 018, 020, 023, 024, 026, 028, 029, 031, 033, 034, 035, 037, 39, 40
  • Supplemental Pack version 1.6.2, build 1002

Version 7.2.2 has different files for each SD-WAN, SVM, NS and Supplemental Pack components:

SD-WAN 4000/5000 7.2.2-24

  • SD-WAN version 7.2.2-24;
  • SVM version 10.1.124.1353.e;
  • NS version 10.1.124.1353.e;
  • XS 6.0 build 50762 with Hotfixes XS60E001, 003, 010, 014, 018, 020, 023, 024, 026, 028, 031
  • Supplemental Pack version 1.6, build 1010

Currently there is no option to downgrade the SVM version (The update software option only applies for the upgrade bundle, not the SVM).

Q: What precaution should be taken while upgrading NetScaler SD-WAN 4000-1000 from version 7.2.2 to version 7.3.4?

A: When upgrading the appliance, if you use the single bundle upgrade (.upg) file then the upgrade gets stuck at step 1/6 and continues to be there unless we go to the CLI and execute a perl command to proceed to next step.

To resolve this issue:

  1. Navigate to cd /var/mps/log and then run

    tail –f bundleupgrade.log

    When you see the following message, proceed to next step:

    Upgrade Status: In progress, doing upgrade.

  2. Navigate to cd /var/mps/cb_sb_images/install and run the following command:

    perl upgradebundle.pl –us nsroot –pas <password of SVM>

    You might have to run this command multiple times to get the upgrade done as it involves 6 steps and can hang at any point.

Q: How can I re-start the setup wizard of a NetScaler SD-WAN VPX appliance?

A: You can remove (set to 0.0.0.0) all hosted IP addresses of NetScaler SD-WAN VPX appliance (both apA and primary IP addresses if it exist)

The following is a sample session:

Login: adminPassword: passwordadmin> set adapter apa -ip 0.0.0.0 -netmask 0.0.0.0 -gateway 0.0.0.0admin> set adapter primary -ip 0.0.0.0 -netmask 0.0.0.0 -gateway 0.0.0.0admin> restart

Q: Why is the upgrade bundle of NetScaler SD-WAN version 7.4.1 displayed as release 7.4.1a?

User-added image

A: On a previous NetScaler SD-WAN 7.4.0 version there was an issue (#0583172). It was due to a problem with glibc library included in supplemental pack and only occurs during upgrade. System reboot actually fix it.

NetScaler SD-WAN 7.4.1.a includes a new supplemental pack, rest of others components remains the same.

Q: Why did MAPI application identifier change on NetScaler SD-WAN version 7.3.0 and later?

A: A default MAPI application identifier rule has been changed from “Port 64999” to “Dynamic TCP” from version 7.3.0 and later.

Connection to exchange are initiated to End-Point Mapper (EPMAP) service running in port 135, and then the MAPI connections are initiated to EMSMDB port (a non-standard port) returned by the EPMAP service. Port was modified to 64999/TCP just to indicate that the EMSMDB port is a non-standard port that is dynamically chosen on every server.

From version 7.3 onwards, MAPI applications are indicated properly as Dynamic TCP. There is no change/difference in the MAPI acceleration behavior.

Changing back to port 64999 is not be required as the port selection is dynamic.

Q: How can I shutdown a NetScaler SD-WAN appliance remotely via the CLI?

A:There is no option to shutdown (only restart) a NetScaler SD-WAN appliance remotely via the CLI when logged in as the “admin” user.

User-added image

Related:

How to force DPA Agent to listen to IPv4?

The dafault installation of DPA Agent makes it listen to :::3741 (that is, all IPv6 addresses, port 3741), but I need 0.0.0.0:3741 (all IPv4 addresses, port 3741).

The dpaagent_config.xml reads:

<AGENTCONFIG> <VERSION>600</VERSION> <AGENTVERSION>6.4.0.102986</AGENTVERSION> <SERVERNAME>172.31.1.98</SERVERNAME> <SERVERPORT>9002</SERVERPORT> <SERVERSSL>true</SERVERSSL> <LOGFILE>/appl/dpa/agent/logs/dpaagent.log</LOGFILE> <LOGLEVEL>Info</LOGLEVEL> <JREDIR>/appl/dpa/services/_jre</JREDIR></AGENTCONFIG>

How to modify this to achieve IPv4 listening?

At this moment, I can’t reach my agent via IPv4.

Thanks

Related:

  • No Related Posts

ECS: Unable to connect to hosts on a subnet with 172.17.x.x

Article Number: 479579 Article Version: 2 Article Type: Break Fix



ECS Appliance,ECS Appliance Software with Encryption,ECS Appliance Software without Encryption,ECS Appliance Software with Encryption 2.2,ECS Appliance Software without Encryption 2.2

The ECS nodes are using an internal docker bridge interface of 172.17.42.1 with an interface name of docker0. This interface has a subnet mask of 255.255.0.0. This subnet mask means that if a customer attempts to access a host in their environment on the subnet 172.17.x.x, the ECS will not be able to route to the host by default.

ecs1-n1:~ # ifconfig docker0

docker0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX

inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

To work around this issue a static route will need to be added to the host on the ECS nodes to allow the ECS to route to the host.

To work around this issue, a static route will need to be added for the host on the ECS nodes to allow the ECS to route to the host.

Edit the following file on all ECS nodes.

vi /etc/sysconfig/network/routes

Under the default route, add the IP address of the host in question followed by the IP of the default gateway of the public interface, followed by the subnet mask of 255.255.255.255 with a – at the end of the line.

Example:

<HOST IP> <PUBLIC DEFAULT GATEWAY> 255.255.255.255 –

172.17.10.5 10.213.1.1 255.255.255.255 –

In the example above, the host IP is 172.17.10.5, use the public default gateway 10.213.1.1. If you are not sure of the public interface default gateway, use the command netstat -rn and identify the gateway with the flag UG for the public interface.

ecs1-n1:~ # netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

0.0.0.0 10.213.1.1 0.0.0.0 UG 0 0 0 public

10.213.1.0 0.0.0.0 255.255.255.0 U 0 0 0 public

169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 private.4

172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0

192.168.219.0 0.0.0.0 255.255.255.0 U 0 0 0 private

After the /etc/sysconfig/network/routes file has been edited on all nodes, reload the network configuration on all nodes with the command service network reload.

Attempt to ping the host to confirm you are now able to route to the host.

Related:

VNX : Data mover sees wrong IP address of SP when inquiring via SCSI (like caminquiry)

Article Number: 482718 Article Version: 2 Article Type: Break Fix



VNX1 Series,VNX2 Series,VNX OE for Block,VNX OE for File

– nas_storage -check -all fails

– Unable to add luns to NASDB (Rescan Storage from Unisphere or server_devconfig/nas_diskmark fails)

Error:

storage API code=3593; SYMAPI_C_CLARIION_LOAD_ERROR An error occurred while data was being loaded from a clariion

From symapi.log:

2016-04-14 23:40:55.664 28104 1 EMC:Celerra CS emcClarLoadSanCopy Loading of San Copy Settings failed on Clar ‘CKM123’ with error code ‘3593’ [SYMAPI_C_CLARIION_LOAD_ERROR][SIL error -16000]

# .server_config server_2 -v "caminquiry c0t0l0" ....0x088|0136: 00 00 00 00 00 00 00 00 ........ <<== SP IP address is 0.0.0.0 

…….

one of the SP IP is set at 1.1.1.1

This IP setting is reserved and not supported for File configurations.

Change the SP IP addresses to anything other than 1.1.1.1.

Example: Setting SPA IP to 1.1.1.4/SPB IP to 1.1.1.5 will work.

Best practice however is to use private IP addresses like 10.x.x.x is better than using 1.x.x.x.

Related:

After a power outage SD-WAN 410 displays LOM/SuperMicro login page

Assign an unreachable IP address to the LOM port and upgrade to version 9.3.3 or later


These are the steps to assign an unreachable IP address to the LOM:

a. Login to the appliance using the following credentials:

Username: ADMIN

Password: ADMIN

User-added image


b. Navigate to Configuration > Network

User-added image


c. Select “Use the following IP address” and Change the network values to 0.0.0.0

User-added image


d. Scroll down to the end of the page and click Save

User-added image


e. Access to the LOM/SuperMicro won’t be available anymore

User-added image

Related:

  • No Related Posts

CAS-200-A1 Setup. SSH OK!! WEB-management Error

I need a solution

Hi All,

I’m trying to setup a CAS-200-A1 from SSH it’s working ok. 

SSH login

Copyright (c) 2015, Blue Coat Systems, Inc.
Welcome to the CAS CLI

   Version: 1.3.7.1 Release id: 190497

——————–MENU——————–

1) Command Line Interface
2) Setup

——————————————–

——————————————————————————————–

CAS# show setupinfo
Network settings:
 Interface 0:0
  IP address:              xxx.xxx.xxx.xxx
  Subnet mask:             255.255.255.224
  NIC media setting:       1000Mb/s Full(auto)
 Interface 1:0
  IP address:              0.0.0.0
  Subnet mask:             255.255.255.0
  NIC media setting:       Disconnected
 Interface 2:0
  IP address:              0.0.0.0
  Subnet mask:             255.255.255.0
  NIC media setting:       Disconnected
 Interface 2:1
  IP address:              0.0.0.0
  Subnet mask:             255.255.255.0
  NIC media setting:       Disconnected
 IP gateway:              xxx.xxx.xxx.xxx
 DNS server:              xxx.xxx.xxx.xxx
 DNS server:              xxx.xxx.xxx.xxx
Access settings:
 Command Line Interface and Web Interface:
  HTTP port:              <disabled>
  HTTPS port:             8082
  Credentials required:   <yes>
  Enable password:        <set>
  Allowed Web clients:
   <any>

 Allowed ICAP clients:
  <any>

But When I try to login through web “Error: Web Management Services are not available. Please contact administrator.”

https://127.0.0.1:50010/

I must say. I’m connecting through portforwarding. The ip of the cas can only be access through a Linux with the port forwarding. (that’s why 127.0.0.1)

Any thoughts?

0

1515080905

Related:

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:

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