Re: [xmlblaster] use of public I_ConnectionProblems

Thank you, that's it !! Jürgen Marcel Ruff wrote: Hi Jürgen, you are probably missing the registration for such events: connection_.initFailsafe(this); regards Marcel Jürgen Prinz wrote: I tried to employ the public I_ConnectionProblems method as shown in SubscribeDemo wi

[xmlblaster] use of public I_ConnectionProblems

asterBase::reachedDead(StatesEnum /*oldState*/, I_ConnectionsHandler* connectionsHandler) { cout << " reachedDead" << endl; } but never got called. The SubscribeDemo, using the same properties and the same xmlBlaster report the approtriate LOG_INFO's.

Re: [xmlblaster] use of setReconnectSameClientOnly

Marcel Ruff wrote: Jürgen Prinz wrote: I use this feature to assure, that only one client with this session-id is connected. i only wondered that the exception did not occure with the connect. It happens on connect, but you are notified asynchronously as you are in fail safe mode. Note

Re: [xmlblaster] use of setReconnectSameClientOnly

denticalClient" and "Only the creator of session /node/ZBAA_/client/[EMAIL PROTECTED]/99 may reconnect, access denied." The reason is most likely that a login session of "[EMAIL PROTECTED]" exists already please use the jconsole to check. best regards Marcel Jürge

[xmlblaster] use of setReconnectSameClientOnly

10:16:42 vpngateway Objserv(2007,357,ERROR,,,#3)[24414]: Sep 25 10:16:42 vpngateway Objserv(2007,357,ERROR,,,#4)[24414]: 1.6.1 #exportiert Sep 25 10:16:42 vpngateway Objserv(2007,357,ERROR,,,#5)[24414]: 1190708202357573000 Sep 25 10:16:42 vpngateway Objserv(2007,357,ERROR,,,#6)[24414]:

[xmlblaster] update in OSF/Motif application

dTimeOut or XmUpdateDisplay don't work or even "return". How can this be solved? Jürgen -- Jürgen Prinz Phone: +49 (0) 7531 / 696-355 Fax:+49 (0) 7531 / 696-315 E-mail: [EMAIL PROTECTED] - Avitech AG Principal Office: Bahnhofplatz

[xmlblaster] crash in c++ PublishDemo

Sfter a recent cvs update my program and likewise c++/../PublishDemo get segmentation fault whe calling connection_publish gdb shows Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 12440)] 0x410fde09 in org::xmlBlaster::client::XmlBlasterAccess::publish(org::xm

[xmlblaster] Communication error

Since installing Xerces xerces-c-src2_4_0 I always after successful conection when publishing a publishArr with 49OK client/prinz I get c++ client ConnectionsHandler-1070524966225133000 en 1070525012852726000 I did build.sh cpp-delete and b

[xmlblaster] contentMime text/plain

When I published MessageUnits with contentMime='text/plain', the xmlBlaster ignored this and updated with either contentMime='text/xml' or no contentMime at all. There were no errors shown on both sides. What's wrong ? Greetings Juergen

[xmlblaster] Error in XmlBlaster

After publishing a MessageUnit with an empty content (explicitly set with (string)"" using c++, the Xml-Blaster produced : java.lang.IllegalArgumentException: Timestamp format must be -mm-dd hh:mm:ss.f stackTrace=java.lang.IllegalArgumentException: Timestamp format must be -mm-d

[xmlblaster] bug or feature ?

The result of MessageUnit.toXml may not be a well-formed Xml-Document, if the content includes characters as '<' or \000. Are there "official" routines for encryption / decryption ? Out of curiosity J. Prinz

[xmlblaster] (no subject)

I encountered a problem using c++ when calling a subscribe to the xmlBlaster out of the update-callback. The callback was invoked before the "Main"-subscribe returned. Neither call to subscibe returned. This can be demonstrated by modifiing SubscribeDemo.cpp too. When using java there are no pro