Thanks, Jagadish.
I made the changes to appserv-tests/config/common.xml,
derby.properties, and devtests/ejb to enable the use of custom derby
port. I tested with QL and ejb devtests. Let me know if you see any
problem related to derby connection when running tests.
-cheng
On 12/28/10 12:28 PM, Jagadish Prasath Ramu wrote:
> Probably, some test is configured to use 1528 port in its connection
> pool settings in the appserv-tests workspace.
>
> Yes, using "db.port.2" property looks fine.
>
> Thanks,
> -Jagadish
>
> On Tue, 2010-12-28 at 10:38 -0500, Cheng Fang wrote:
>> I'm trying to replace the hard-coded derby port numbers in
>> appserv-tests/config/common.xml to the props in
>> appserv-tests/config/derby.properties. I noticed the startDerby and
>> stopDerby tasks in common.xml starts/stops 2 derby processes, on port
>> 1527 and 1528 respectively.
>>
>> Any particular reason why we need 2 derby processes?
>>
>> If we do need 2, how about adding a db.port.2 prop in derby.properties?
>>
>> <target name="startDerbyNonMac" depends="init-common" unless="darwin">
>> <echo message="StaRTing Derby DB servers in the Network Mode"/>
>> <parallel>
>> <java classname="org.apache.derby.drda.NetworkServerControl"
>> classpath="${db.classpath}" fork="true" spawn="true">
>> <arg line="-h localhost -p 1527 start"/>
>> </java>
>> <java classname="org.apache.derby.drda.NetworkServerControl"
>> classpath="${db.classpath}" fork="true" spawn="true">
>> <arg line="-h localhost -p 1528 start"/>
>> </java>
>> </parallel>
>> </target>
>>
>> Thanks,
>> -cheng