If this clientProperty is send with ConnectQos the clientProperties are
copied to the SessionInfo.remoteProperty map (which are manipulatable by jconsole and EventPlugin)
This client tests the method subscribe() with a later publish() with XPath query.
The subscribe() should be recognized for this later arriving publish().
The SOCKET protocol can support zlib compression with streaming compression
A partial flush means that all data will be output,
but the next packet will continue using compression tables from the end of the previous packet.
If throwable is of type XmlBlasterException it is just casted (and location/message are ignored)
else if throwable is one if IllegalArgumentException, NullpointerException or OutOfMemoryError
it is converted to an XmlBlasterException with corresponding ErrorCode
otherwise the ErrorCode is INTERNAL_UNKNOWN
Send message to subscriber even the content is the same as the previous?
Default is that xmlBlaster does send messages to subscribed clients, even the content didn't change.
2008-02-11 10:37:41.710 SEVERE 97-pool-1-thread-65 RL10 org.xmlBlaster.Main newException: PANIC: Doing immediate shutdown caused by exception: XmlBlasterException errorCode=[resource.db.unknown] serverSideException=true location=[JdbcManagerCommonTable.deleteEntries] message=[#16564M An unknown error with the backend database using JDBC occurred -> http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#resource.db.unknown : com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 76) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.
If there are new messages available in the queue, you get invoked
here and are asked if you want to start a worker thread (from the thread pool)
to start taking messages from the queue and send them over the remote connection.
When you compare two methodName with == and they are
loaded by different Classloaders it will fail (return false even
if they are the same method), using
this equals() method is safe under such circumstances
When you compare two methodName with == and they are
loaded by different Classloaders it will fail (return false even
if they are the same method), using
this equals() method is safe under such circumstances
Use reflection to access a URL[] getURLs or URL[] getClasspath method so
that non-URLClassLoader class loaders, or class loaders that override
getURLs to return null or empty, can provide the true classpath info.