Hi All,
Please assist on below error.
We tried creating Demo or sample BPM model in WM 8.2. Single Receive task and service task. It got build and uploaded successfully. In MWS we were able to see the business process enabled for execution.
When we test it by publishing a doc to Broker it is throwing below error.
2013-07-12 19:49:58 EST wm.prt.dispatch:handlePublishedInput wm.prt.dispatch:handlePublishedInput
[Exception: Unable to connect to database!] not found in “com.wm.resources.CoreExcpMsgs”.
Stack trace data … adff1480-ec6a-11e2-857b-82dbf70d0edf adff1480-ec6a-11e2-857b-82dbf70d0edf b880e640-ec6a-11e2-85e7-c400a9537dfb
2013-07-12 19:49:48 EST wm.prt.dispatch:handlePublishedInput [sag-cjdbc42-0011][Oracle JDBC Driver][Oracle]ORA-00904: “RETRYCOUNT”: invalid identifier
Stack trace data … adff1480-ec6a-11e2-857b-82dbf70d0edf adff1480-ec6a-11e2-857b-82dbf70d0edf b880e640-ec6a-11e2-85e7-c400a9537dfb
2013-07-12 19:38:58 EST wm.prt.dispatch:handlePublishedInput [sag-cjdbc42-0011][Oracle JDBC Driver][Oracle]ORA-00904: “RETRYCOUNT”: invalid identifier
Stack trace data … 2b770dc0-ec69-11e2-bb3a-90fe9b03042f 2b770dc0-ec69-11e2-bb3a-90fe9b03042f 351906d0-ec69-11e2-bbd8-8cd698d05801
2013-07-12 19:36:39 EST wm.prt.admin:startup java.lang.RuntimeException: property jms.provider.url in JNDI properties must be set in the format of broker://host:port/broker_name/client_group
Stack trace data … e254fa30-ec68-11e2-b5fb-9d09eef472bf NULL e254fa30-ec68-11e2-b5fb-9d09eef472bf
2013-07-12 19:26:26 EST wm.prt.dispatch:handlePublishedInput wm.prt.dispatch:handlePublishedInput
[Exception: Unable to connect to database!] not found in “com.wm.resources.CoreExcpMsgs”.
Stack trace data … 6b221ac0-ec67-11e2-a949-fb6e945f0323 6b221ac0-ec67-11e2-a949-fb6e945f0323 6f2d69d0-ec67-11e2-a96c-8bf5b6444c5b
2013-07-12 19:26:16 EST wm.prt.dispatch:handlePublishedInput [sag-cjdbc42-0011][Oracle JDBC Driver][Oracle]ORA-00904: “RETRYCOUNT”: invalid identifier
Stack trace data … 6b221ac0-ec67-11e2-a949-fb6e945f0323 6b221ac0-ec67-11e2-a949-fb6e945f0323 6f2d69d0-ec67-11e2-a96c-8bf5b6444c5b
2013-07-12 19:19:06 EST wm.server.ns:getACLInfo wm.server.ns:getACLInfo
[ISS.0085.9055] Node ProcessProject1.process2.process2_1.SSMTIS:Task1_InputMapService does not exist
Stack trace data … 582957e0-ec66-11e2-a0c1-ec3d60c466ab NULL 582957e0-ec66-11e2-a0c1-ec3d60c466ab
2013-07-12 19:15:44 EST wm.prt.dispatch:handlePublishedInput wm.prt.dispatch:handlePublishedInput
[Exception: Unable to connect to database!] not found in “com.wm.resources.CoreExcpMsgs”.
Stack trace data … ee276f30-ec65-11e2-9dc9-fe08888ed049 ee276f30-ec65-11e2-9dc9-fe08888ed049 f021dfa0-ec65-11e2-9de2-f98acac084b6
2013-07-12 19:15:43 EST wm.prt.dispatch:handlePublishedInput wm.prt.dispatch:handlePublishedInput
[Exception: Unable to connect to database!] not found in “com.wm.resources.CoreExcpMsgs”.
We tested all JDBC Pools & Broker getting local documents also published successfully.
Please Help us in getting this issue resolve.
#webMethods-BPMS#webMethods#BPM