Problem activating changes to JDI (SP16)

Question

<b>Environment</b>
My environment consists of a NWDS (Version: 2.0.9, Build id: 200411030238, I applied SP16 to it) and NWDI SP16.
<b>Application</b>
I have the following DC in my NWDS;
1) Java DC (containing external libraries i.e. struts)
2) J2EE Server lib DC (wraps Java DC for runtime, buildtime dependecies)
3) J2EE web DC (uses 2 and houses my app)
4) J2EE ear DC (wraps the entire app for deployment to the server)
In addition to the above details I added a build.vm to the /cfg/ folder in my Java DC above..
Contents of the build.vm
********************start
<!--
This script copies all *.jar files below src/packages
to the folders generated by every public part of the DC.
-->
<project name="Copy jar" basedir="." default="build">
<target name="build" depends="copy" />
<target name="copy">
#foreach($pp in $dc_public_parts)
<echo message="Public Part: $pp.Name"/>
#set( $ppdir = "$/${pp.Name}" )
<mkdir dir="$ppdir/lib/java" />
<copy todir="$ppdir/lib/java" >
<fileset dir="$/src/packages/" >
<include name="*.jar"/>
</fileset>
</copy>
#end
</target>
</project>
********************end
<b>Problem</b>
While I can successfully build and deploy to my local J2EE server when I attempt to activate all of my activities to NWDI.  My activities get stuck in a "queued" state and don't go anywhere.  I have tried to re-build my compartment and re-activate but that didn't work.
Is anyone else having problems with external libraries and SP16?
Any help would be appreciated.
Thanks,
Jarrod

Answer 1

Hi Jarrod
Queing usually occurs when the SDM is not available for deployment. You should be able to monitor to your queue with the url
http://<JDI host>:<port>/TCS/Deployer
Some of the reasons for queing which I have seen
->SDM Connection with the Server broke
->There is an administrator logged into the SDM via gui or api.
You can check if it is any of the above conditions or anything else by monitoring the latest log in the following path within JDI
/usr/sap/<instance name>/SYS/global/TCS/Log/ (although I am bit fuzzy about the path , please recheck)
Regards
Pran