[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[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 yyyy-mm-dd
hh:mm:ss.fffffffff
stackTrace=java.lang.IllegalArgumentException: Timestamp format must be
yyyy-mm-dd hh:mm:ss.fffffffff
at java.sql.Timestamp.valueOf(Timestamp.java:128)
at org.xmlBlaster.util.Timestamp.valueOf(Timestamp.java:225)
at
org.xmlBlaster.protocol.corba.CorbaDriver.convert(CorbaDriver.java:539)
at
org.xmlBlaster.protocol.corba.CallbackCorbaDriver.sendUpdate(CallbackCorbaDriver.java:123)
at
org.xmlBlaster.engine.dispatch.CbDispatchConnection.doSend(CbDispatchConnection.java:147)
at
org.xmlBlaster.util.dispatch.DispatchConnection.send(DispatchConnection.java:189)
at
org.xmlBlaster.util.dispatch.DispatchConnectionsHandler.send(DispatchConnectionsHandler.java:359)
at
org.xmlBlaster.util.dispatch.DispatchWorker.run(DispatchWorker.java:166)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
at java.lang.Thread.run(Thread.java:479)
errorCode=communication.noConnection.dead message=The remote connection
is not established and we have given up to poll for it. ->
http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#communication.noConnection.dead
at
org.xmlBlaster.util.dispatch.DispatchManager.handleWorkerException(DispatchManager.java:375)
at
org.xmlBlaster.util.dispatch.DispatchWorker.run(DispatchWorker.java:196)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
at java.lang.Thread.run(Thread.java:479)
versionInfo=version=0.85e,os.name=Linux,os.version=2.4.19-4GB,java.vm.vendor=Sun
Microsystems
Inc.,java.vm.version=1.3.1_04-b02,os.arch=i386,build.timestamp=11/26/2003
09:19 AM,build.java.vendor=Sun Microsystems Inc.,build.java.version=1.3.1_04
errorCode
description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#communication.noConnection.dead
With seting the content to "empty", it was o.k.
Best regards
J.Prinz