TX SQE tx05 functional, Connection refused port 1527 error

TX SQE functional tx05 scenario seeing this "random" error:

/space/test4u2/xtests/netbeans-trunk/lib/harness.xml:223: The following
error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/test/build.xml:62: The
following error occurred while executing this line:
/space/test4u2/xtests/netbeans-trunk/lib/module_harness.xml:384: The following
error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/test/build-tx05.xml:32: The
following error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/functional/tx05.ent:93: The
following error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/functional/tx05.ent:169: The
following error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/functional/resources.ent:9:
The following error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/interop/database-ant.xml:38:
java.sql.SQLTransientConnectionException: java.net.ConnectException : Error
connecting to server localhost on port 1527 with message Connection refused.

after first reporting and seeing this problem as noted in wsit issue 1015,
subsequent runs :
Tango Dev (#wsit-nightly-1-4-20080929+GF-911)
Tango Dev (#wsit-nightly-1-4-20080927+GF-91_02)
Tango Dev (#wsit-nightly-1-4-20080926+GF-91_02)
Tango Dev (#wsit-nightly-1-4-20080925+TC_5.5.26)

show this problem noted above is not exhibited for jdk6 w/sjsxp.

the september 25th results Tango Dev (#wsit-nightly-1-4-20080925+GF-911) did
exhibit this error as shown above.

However the same dates results when running only jdk6 w/sjsxp show 100% pass,
see url:

[http://eas-v240-](http://eas-v240-)
12.india.sun.com:8080/test4u/composedresultsseqid=1222690815842&id=1222308001143
&testrunid=20080811131931&userid=metro

September 22nd "Tango Dev (#wsit-nightly-1-4-20080921+GF-91_02)" dashboard
results shows errors for nightly 1.4 jdk5 w/sjsxp and nightly 1.4, Woodstox,
JDK6, see url:
[http://eas-v240-](http://eas-v240-)
12.india.sun.com:8080/test4u/composedresultsseqid=1222690815842&id=1222048801235
&testrunid=20080811131931&userid=metro

September 20th "Tango Dev (#wsit-nightly-1-4-20080919+GF-91_02)" results show
100% pass for same configs:

[https://central.sun.net/http://eas-v240-](https://central.sun.net/http://eas-v240-)
12.india.sun.com:8080/test4u/composedresults?
seqid=1222691773904&id=1221876000478&testrunid=20080811131931&userid=metro

This seems to be an issue with tests/test config.

Since the original reported bug wsit issue 1015 is no longer occurring, after
Jitu put in a workaround for
[https://sjsxp.dev.java.net/issues/show_bug.cgi?id=67](https://sjsxp.dev.java.net/issues/show_bug.cgi?id=67) (he worked out the logic in
xmlstreambuffer code differently) we are now seeing this error for jdk5 w/sjsxp
and jdk6 w/woodstox; jdk6 w/sjsxp works fine. i'm closing the wsit issue 1015
bug as fixed, and i've opened this bug to track/troubleshoot this random error
in tx05 SQE funcitonal test, to see if it keeps occurring and determine why it
does so, if it occurs again.

I've open another bug under "tests" sub-category to track this "random" error:

The following error occurred while executing this line:
/space/test4u2/cvswork/sunsw/tango/qe-tests/wstx/interop/database-ant.xml:38:
java.sql.SQLTransientConnectionException: java.net.ConnectException : Error
connecting to server localhost on port 1527 with message Connection refused.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.4]

Source: [https://github.com/javaee/metro-wsit/issues/1042](https://github.com/javaee/metro-wsit/issues/1042)
Author: glassfishrobot

Start by reviewing the tx05 functional scenario in functional/tx05.ent and the database setup in interop/database-ant.xml, especially the reported failing lines. Reproduce the port 1527 connection failure across the listed JDK and parser configurations, then document the cause and confirm that the affected configurations complete successfully.

Written by the indexing model from the issue text.