A question on pub-sub model

Hi Guys,

In Guaranteed exactly one time processing of documents,where ( In which tables ) the system maintains an entry which it checks for evaluation …

Guaranteed documents are usually stored in a disk or File system so they can be recovered in case of power failure or server restart.

They can also be stored in a Queue storage which refers to file storage of Broker server along with non-volatile Broker metadata (like Broker definations, document type definations and client group definations )


Review the IS documentation for the details of “exactly once” delivery.

Please review the "Publish-Subscribe Developer’s User Guide - Software AG Documentation…It should cover the most of the Broker and these topics.

As a quick answer GD uses storage on the disk (persistance) vs Volatile is only once uses memory.


Hi All,

We are receiving the below error message in IS.Because of this most of the process models are in started state which is impacting a lot in production.Can any one help on this.Below is the error message what we are seeing.
let me know if you need any details

[75]2014-01-24 10:33:49 GMT [ISS.0128.0001E] Unable to get JDBC connection. Exception:Error Message: [SoftwareAG][Oracle JDBC Driver]Login has timed out.; Error Code: 0; SQLState: HYT00
[74]2014-01-24 10:33:41 GMT [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Error Queue’ failed to log event to destination ‘ErrorDBDest’; reason ‘Failed to open connection to database; reason: [SoftwareAG][Oracle JDBC Driver]Login has timed out.’; stack trace follows
[73]2014-01-24 10:33:41 GMT [WmAuditingSC.destination.1126E] Failed to open connection to database; reason: [SoftwareAG][Oracle JDBC Driver]Login has timed out.
[72]2014-01-24 10:32:41 GMT [ISS.0098.0049C] Exception:com.wm.app.b2b.server.ISRuntimeException: [98.9998] Exception --> 0 java.sql.SQLException: [SoftwareAG][Oracle JDBC Driver]Login has timed out. while executing trigger. Rejecting Document for TriggerStore:OUK_BPO_PAYM_BUSINESS_UNIT_UPDATE_V1.PaymBusinessUnitUpdate_V1.BPOSTART:subscriptionTrigger.
[71] at com.wm.app.b2b.server.i…
[70] at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:443)
[69] at java.lang.reflect.Method.invoke(Method.java:597)
[68] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[67] at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
[66] at wm.server.dispatcher.deleteExpiredUUID(dispatcher.java:732)
[65] at com.wm.app.b2b.server.indoubtresolver.jdbc.MessageHistoryJDBCHandler.deleteExpiredUUID(MessageHistoryJDBCHandler.java:499)
[64] at com.wm.app.b2b.server.indoubtresolver.jdbc.MessageHistoryJDBCHandler.getConnection(MessageHistoryJDBCHandler.java:155)
[63] at com.wm.app.b2b.server.JDBCConnectionManager.getConnection(JDBCConnectionManager.java:107)
[62] at com.wm.app.jdbc.JDBCConnPoolMgr.getConnection(JDBCConnPoolMgr.java:161)
[61] at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:127)
[60] at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:131)
[59] at com.wm.app.jdbc.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:145)
[58] at com.wm.app.jdbc.JDBCConnectionPool.getAvailConnection(JDBCConnectionPool.java:250)


Hello Viresh,

Error Msg clearly stating that is is unable to connect to DataBase.

  1. Make sure is db up and running ?
  2. Any recent db patching taken place on Prod without proper testing in testing environments ?
  3. Contact dba for quick help

And update us with your new findings.



It looks that SQL server is out of login sessions, that may reason of login timeout. Please take help of thin SQL client to login to verify the userid and password as well as sessions. Take help of DBA in investigation.




Are you sure the DB connectivity is fine in your production env?

Please check with your DBA also and verify the credentials or some thing has changed?