Thank for the response,
I've opened up a new thread with the Wowza and Kaltura Cluster deployment issues.
I've also made some progress. The exception was from a missing lib, which the kaltura tutorial does not include so in the libs you need to have KalturaMediaServer.jar and KalturaStreamingEngine.jar, after adding the two, wowza started just fine, now when trying to connect from the encoder it says that the streaming address is not correct, or that the server cannot be contacted. I've deduced this is a step ahead from starting wowza with each of the .jars separatly. With one of the i get the issue where the stream name is busy but it connects with whatsoever stream name I use which is clearly not correct as it should only connect to the dynamically generated one, and with the other wowza does not start at all, with both of them wowza starts correctly and no warnings but it does not connect to kLive, but it does connect to any other live application now what I've found out is that there is a mysql connector .jar, which for me atleast indicates that wowa should have some interraction with the mysql server.
I've also tryed deploying it on the same server as the the front node, and i get the exact same results.
Sorry for the long post.
Regards,
Jacob R.