A lot of the same tests are failing across databases, less so with derby.

TLS Required 1, Presence 1, PubSub 2, etc.

http://build.xmpp-test.net/~tigase/files/static/tests/7.0.3-b3830/func/mysql/functional-tests.html

http://build.xmpp-test.net/~tigase/files/static/tests/7.0.3-b3830/func/pgsql/functional-tests.html

http://build.xmpp-test.net/~tigase/files/static/tests/7.0.3-b3830/func/derby/functional-tests.html

http://build.xmpp-test.net/~tigase/files/static/tests/7.0.3-b3830/func/mssql/functional-tests.html

http://build.xmpp-test.net/~tigase/files/static/tests/7.0.3-b3830/func/mongodb/functional-tests.html

everything else has been done.

Ran the tests again and results were worse.

%eric - this are results from latest TTS? If so then issue is in TTS as I worked on changes for version 7.1 I needed to add loading of new schema files which are missing in version 7.0.3.

i think this errors may be related to my change in TTS as I remember that I got similar results when loading of schema for version 7.1 failed - missing changes in TTS to load new schema files.

As %andrzej.wojcik suggested - using tigase-testsuite-2.2.1 (tagged in TTS repo) should be more appropriate - looking at the server info should give move information but probably schema version mismatch caused server to fail to start.

As for the second run - please make sure that jenkins TTS task is not running (or other Tigase instance for that matter). Couple of latest TTS jenkins runs failed with

2016-03-07 01:14:58.197 [ConnectionOpenThread]  ConnectionOpenThread.addAllWaiting()  WARNING: Error: creating connection for: {type=accept, socket=plain, ifc=[Ljava.lang.String;@3301bd9b, remote-host=l
ocalhost, required=false, port-no=5280}
java.net.BindException: Address already in use
…
2016-03-07 01:14:58.212 [ConnectionOpenThread]  ConnectionOpenThread.addAllWaiting()  WARNING: Error: creating connection for: {port-no=5678, local-host=test.test-d, remote-host=null, type=accept, socket=plain, ifc=[Ljava.lang.String;@3ee0b4f7, max-reconnects=7200000, repo-item=test.test-d:very-secret:accept:5678:null:null:tigase.server.ext.lb.ReceiverBareJidLB}
java.net.BindException: Address already in use
…
2016-03-07 01:14:58.214 [ConnectionOpenThread]  ConnectionOpenThread.addAllWaiting()  WARNING: Error: creating connection for: {type=accept, socket=plain, ifc=[Ljava.lang.String;@24014b94, remote-host=localhost, required=false, port-no=5222}
java.net.BindException: Address already in use
…

Which would indicate other Tigase instance running.

Also - as some tests tend to fail randomly (mostly bosh ones) but we are not working on TTS anymore then sometimes it may be needed to re-run the test for a particular DB if it manifested a failed single test -- this is OK.

I've checked out tigase-testsuite-2.2.1 and am getting the same results. This happened with the last release too.

http://build.xmpp-test.net/~tigase/index2.html

Eric, I think it may be related to this commit, which was included between 7.0.1 and 7.0.2:

Issue #2561 - fixed issue with sending packets to resources without presence or with negative priority

Commit:

889b4891 [889b489]

Can you try this TTS commit: bef1ad83a29b97eec22ca2eb526bd070d89fe13d [bef1ad8] ?

I think we could/should create a TTS stable branch to match the changes in the server.

Errors compiling that commit:

[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/tigase/tigase-testsuite/src/main/java/tigase/test/util/DomBuilderHandler.java:[57,7] error: DomBuilderHandler is not abstract and does not override abstract method endElement(StringBuilder) in SimpleHandler
[ERROR] /home/tigase/tigase-testsuite/src/main/java/tigase/test/util/DomBuilderHandler.java:[127,14] error: endElement(StringBuilder) in DomBuilderHandler cannot implement endElement(StringBuilder) in SimpleHandler
[ERROR]   return type void is not compatible with boolean
/home/tigase/tigase-testsuite/src/main/java/tigase/test/util/DomBuilderHandler.java:[126,1] error: method does not override or implement a method from a supertype
[INFO] 3 errors 
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.580s
[INFO] Finished at: Mon Mar 07 19:42:19 CET 2016
[INFO] Final Memory: 21M/118M
[INFO] ------------------------------------------------------------------------

Current development version was too-eagerly configured to use latest snapshots of xmltoosl and tigase-utils.

I've created a new branch stable@, cherry picked relevant commits and pushed it to remote. Please try with @origin/stable

TLS Required 1 (c2s) is the only functional test failing with stable. I am running lmem now.

lmem is the same test with less memory forget that. You can reload index2.html to see the TLS Required failures.

I've removed results for TLS Required 1 (c2s) for now, until it's fixed.

http://build.xmpp-test.net/~tigase/

There was one commit missing which was related to this test:

b28124f2 			2016-03-08 06:08 PM 	Wojciech Kapcia 	fix tls-required handling; #2859, #2997

I've included this change in the code and it solves the problem; I've included this commit in origin/stable branch but this requires re-creating builds and re-running the tests.

I've also tagged current origin/stable of TTS with @tigase-issue #7.0.3@.

Latest exe/jar build does not appear to have #3959 fixes included, installer files do not deposit required javax.servlet jar into jars directory. Archive has necessary files.

Which build exactly? Commit seems to be there.

Just tested build 3830, I think we had a similar issue previously where the installer did not include those files about 3 months ago, #3764 those fixes may need to be added as well.

We're going to be using build 3931. I'll upload the files after tests are successful.

3831 rather.

Files are uploaded https://projects.tigase.org/projects/tigase-server/files

Tests are successful http://build.xmpp-test.net/~tigase/

Maven artifacts deployed http://maven.tigase.org

b3831 still exhibits errors found in #3764 when installer is used.

Web-installer functions OK, no errors found otherwise windows or linux installs.

If possible I'd like to add commit 27fc7d5 from #3937 to this release as well.

%daniel This should have been mentioned before.

Eric, I've included those changes in the @origin/stable@. Can you checkout this branch, prepare the packages and provide them to %daniel for tests? In the meantime you could run TTS as I think those should be only changes.

Looks like we are ready to go.

Patch notes finished available in HTML ready to roll

Announcing Release of Tigase XMPP Server v7.0.3!
A new Maintenance Release has been published for Tigase with a number of fixes included below.
New Features and Changes

    HTTP Api Component has been updated to v1.1.1
    A Setup.bat file added for ease of windows installation setup from archive.

Fixes

    #2859 Fixed STARTTLS forcing required on SSL Socket.
    #3259 Fixed infinite loop error when sending data sized between 32767 and 65535 bytes through WebSocket.
    #3618 Fixed 'recipient no longer available' error when sending messages to JIDs connected to more than one cluster.
    #3959 Fixed Installer not copying necessary files for HTTP components.
    #3959 Fixed wrapper.conf file to include proper file locations.
    #3970 Fixed duplication of messages with AMP payload while running in cluster mode.

Downloads available here. 

Announcements are prepared, Artur ready for your go ahead.

Go ahead!

Announcements made, website updated.

freecode is no longer updating, wiki updated.