Daniel Elkington

Wim, i had some similar issues during our initial v6 testing, one particularly annoying 'feature' of the new client is the fact that there are two sets of properties, session and default. You'd think that setting the session properties would be enough to control all aspects of a particular session, but i found that it is also necessary to set some of the properties in the default settings in order to get the client to behave reliably.
We raised this with Northgate support, but our v6 testing has been on hold for a while so i haven't followed it up with them.

Some of your issues may also be caused by registry problems. Did you have any of the earlier v6 clients installed on that machine? It's often necessary to to a full registry cleanup removing all references to proiv, before installing the 6.1 client.

You've answered my question then, if you don't have a config.xml file then you're not using the java bus. The config.xml file controls all the settings like number of simultaneous connections, timeouts for starting new kernels, etc. I haven't used the standard bus much, so i don't know if you can control those parameters some other way.
In the situation i was referring to before, the timeout limit for starting a new kernel was too low, which meant that when the server was busy and a task call was made, the server was taking too long to start up a new kernel process. I think there are significant differences between the standard bus and the java version though, so i'm not sure whether that situation would be applicable.

Just to clarify, do you mean you're using the java API, or the java bus, or both? We have a customer running the java bus, and they had what we initially thought were licencing problems, but turned out to be caused by heavy network traffic and server load, these were fixed by tweaking the settings in the config.xml file that controls the bus parameters.

Are you using v5.5 or v6? I've come across that same error message caused by a wide variety of issues, the error reporting on the 5.5 Java bus really is pretty useless. Was told at the time that this should be improved in v6 but i don't know if that's actually happened.

I think that the connection to the java bus is left open, which is why the program doesn't terminate naturally. It may be necessary to manually close the connection if you want this to happen. For us it isn't really an issue since we are using the API within a web application which is always connected to the same instance of the bus, so there is no need to keep closing and re-opening the connection.