Read timed out while doing check out of DC


I have an unique error.

In our project, we have installed NetWeaver 7.0 EHP1 SP4 as the Portal Devlopment Server.

I have done all the steps for Post Installation Steps of NWDI.

Now, there is an SAP SRS Compnent being deployed in Portal and functional consultant are

also using it.

Component Name : ISRSRS05_0-20002510.SCA

Version: SP05 for IS-R-SRS 602.

Now, this component is already being deployed in our Portal Server SAP NetWeaver 7.0 EHP1 SP4.

I was able to import this component in our NWDI track.

The dependent components of this .SCA are EP-BUILDT 7.0, SAP-JEE 7.0, SAP-BUILDT 7.0 and SAP_JTECHS 7.0

All the mandatory steps in Landscape Configurator and Transport Studio in CMS were done without error.

Then, I imported the NWDI track Configuration in NWDS 7.01 SP4.

I am able to import the inactive dcs of IS-R-SRS but when checking out, I am getting

Checkout failed: Checkout file failed (server response: Communication error [cause: Read timed out]):/TST/sap.com_IS-R-SRS/dev/inactive/DCs/ /

The error in NWDS .metadata log is

!MESSAGE Feb 2, 2010 5:48:46 PM     [Thread[main,5,main]] Error: Read timed out
	at Method)

But I can create activities successfully in NWDS (DTR).

I am able to write code in Compnent Controller of my custom SC VIN_PRD.

Now, my question is whether this is or incompatibility of software.

My delivery manager told me to get the older version of NWDS ie., NWDS 6.40 but I am sure

that will not work with SAP NetWeaver 7.0 EHP1 SP4.

There is an error in DTR log server but on earlier date:

com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask#Java#background.outOfDBConnections#com.tssap.dtr.server.deltav.resources.log_messages#Service unavailable, running background task {0} failed. Database connection pool is out of connections. Check connection pool and database settings.#1#com.tssap.dtr.server.deltav.runtimeconfig.impl.ConfigParamsCheckerTas


Kaushik Banerjee

  • SAP Employee


Can you change 'fullyMaterialzeLobData=false' to

'fullyMaterialzeLobData=true' in the jdbc/pool/DJ1/Url.

Please also refer to note 784568 on this problem



0 View this answer in context

Helpful Answer