ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Stirling" <>
Subject RE: starteam problems.
Date Fri, 08 Nov 2002 06:30:01 GMT

This turns out to be an interesting problem.  I cc'ed the authors of
these tasks, which incidentally were just improved with some other
really cool new features this week (see the latest WHATSNEW in the
source dist or CVS).  Try the suggested work-around below (configuring
the default encryption setting on the server connection via the StarTeam
GUI), but I think the longer term and better "solution" and
(orthogonally) *enhancement* would be to enhance all the Ant StarTeam
tasks so that they take attributes for an encryption setting on the
server connection.  Ditto for compression and protocol settings, but
this is besides the point.

What follows is couched in terms of the StarTeam Java SDK:
- The way the StarTeam tasks connect to StarTeam is by getting an SDK
View object using a static method of the SDK utility class
StarTeamFinder to lookup the View based on a starteam:// URL created
from the attribute values you set in, e.g., your <stcheckout> target.
The Server object, which is a wrapper for the connection to StarTeam
server's database, is retrieved from the View that was looked up.

- So, what's wrong with that?  The problem is that the only way the SDK
API allows you to specify the encryption algorithm (and compression
level and protocol) to use when creating a Server object is if you use
one of two Server() constructors and explicitly pass
EncryptionAlgorithm.NULL in the constructor.  This information cannot be
passed in a StarTeam URL.  

- Therefore, the StarTeam tasks could allow users more of the
flexibility that the command line and GUI clients allow.  So, the new
way to do this in the tasks themselves would be to create the Server
object based on all the user-defined attributes in the task (defaults
should allow users to not have to specify encryption, protocol or
compression if they don't care) and *then* open the Project and then the

Anyway, the error below is saying that there's a bug in a native
encryption library called by StarTeam's (not Ant's) Java code:

> An unexpected exception has been detected in native code 
> outside the VM. Unexpected Signal : 
> Current Java thread:
>         at 
> com.starbase.starteam.vts.comm.CAPIEncryptContext.nativeGetBlockLengt
> h(Native Method)
>         at 
> com.starbase.starteam.vts.comm.CAPIEncryptContext.getBlockLength(CAPI

I've never seen this happen with StarTeam myself (which we use at work),
but it's probably because I have encryption off by default on my
StarTeam client.  Try selecting "No encryption" on your GUI client's
"Server Properties" for the StarTeam server you connect to for this
project.  Hopefully this might affect the default encryption level that
the Java SDK uses and hopefully your company's server allows you to
connect with no encryption.  But, there's also a great possibility (for
all I can tell) that the SDK pays no attention to any setting made
through the GUI client.  In which case my other suggestion is to make
sure you upgrade your StarTeam client and your copy of the SDK libraries
to the latest versions to see if the problem with the native encryption
code has been fixed.

Scott Stirling

> -----Original Message-----
> From: Vikas Malla [] 
> Sent: Thursday, November 07, 2002 12:05 PM
> To:
> Subject: starteam problems.
> I use this to check out code from starteam:
> <stcheckout URL="starteam:49201/TEST/TEST" 
>               username="<username>"
>               password="<password>"
>               label="build 1"
>               forced="true"
>   />
> This is what happens:
> [stcheckout] Checking Out: C:\dir1\dir2\weather\package 
 cache\w eather.dep2 [stcheckout] Checking Out: 
> C:\dir1\dir2\weather\weather\Current
> WeatherBean.class
>      [java] Java Result: 1
> An unexpected exception has been detected in native code 
> outside the VM. Unexpected Signal : 
> EXCEPTION_ACCESS_VIOLATION occurred at PC=0x100031e4 Function 
> name=(N/A)
> Library=(N/A)
> NOTE: We are unable to locate the function name symbol for the error
>       just occurred. Please refer to release documentation 
> for possible
>       reason and solutions.
> Current Java thread:
>         at 
> com.starbase.starteam.vts.comm.CAPIEncryptContext.nativeGetBlockLengt
> h(Native Method)
>         at 
> com.starbase.starteam.vts.comm.CAPIEncryptContext.getBlockLength(CAPI
>         at 
> com.starbase.starteam.vts.comm.CommandFile.setCipher(
> :82)
>         at 
> com.starbase.starteam.vts.comm.Command.enableEncryption(
> 199)
>         at 
> com.starbase.starteam.vts.comm.Command.resetForNewCommand(Command.jav
> a:158)
>         at 
> com.starbase.starteam.vts.comm.TcpIpConnection.prepareCommand(TcpIpCo
>         at 
> com.starbase.starteam.vts.comm.CommandMacro.prepare(
> :132)
>         at 
> com.starbase.starteam.vts.comm.CommandMacro.execute(
> :77)
>         at 
> com.starbase.starteam.ViewSession.terminate(
>         at com.starbase.starteam.Server.terminate(
>         at com.starbase.starteam.Server.disconnect(
>         at com.starbase.starteam.Server.finalize(
>         at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
>         at java.lang.ref.Finalizer.runFinalizer(
>         at java.lang.ref.Finalizer.access$100(
>         at java.lang.ref.Finalizer$
>         at
> Dynamic libraries:
> 0x00400000 - 0x00405000         C:\jdk1.3.1_03\bin\java.exe
> Local Time = Thu Nov 07 11:47:33 2002
> Elapsed Time = 27
> #
> # The exception above was detected in native code outside the 
> VM # # Java VM: Java HotSpot(TM) Client VM (1.3.1_03-b03 
> mixed mode) # # An error report file has been saved as 
> hs_err_pid3316.log. # Please refer to the file for further 
> information. #
> I have no idea why this is happening. any suggestions......

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message