SAP Knowledge Base Article - Preview

2076054 - After upgrading from Sybase Unwired Platform 2.1.3 to SAP Mobile Platform 2.3.4, Mobile Workflow receives timeout when executing - SUP/SMP

Symptom

User had a Mobile Workflow developed in Sybase Unwired Platform 2.1.3.  Due to the end of maintenance support for Sybase Unwired Platform 2.1.3 on 30 September 2014, user upgraded the Sybase Unwired Platform 2.1.3 first to Sybase Unwired Platform 2.2.x and then to SAP Mobile Platform 2.3.4.  After the upgrade was complete, the user then downloaded the Hybrid Web Container 2.3.4.7474 from the Apple App Store, connected from the Hybrid Web Container to the SAP Mobile Platform, downloaded the Workflow, and attempted to log in to the Workflow on their credentials screen and received an error "Server response time out".

Review of the SAP Mobile Platform log shows the error:

2014-10-03 19:02:40.186 DEBUG   MSG          sup.mbs.13 [com.sybase.sup.server.util.ReplySender] [] [] sending Message ( queue=[sup.mbs.412#MobileWorkflow:1SE091OBMO.exeR], cid=[412#MobileWorkflow:1], method=[replayResult])
2014-10-03 19:02:40.187 WARN    Other        sup.mbs.13 [SUP_MWF.server.SUP_MWFDB] [] [] {"_op":"C","level":5,"code":500,"eisCode":"","message":"java.lang.NumberFormatException:For input string: \"MobileWorkflow:1\"","component":"ServicesUserActivationOperation","entityKey":null,"operation":"replay","requestId":"ffffb01c857c4725b35c0c3f4102a349","timestamp":"2014-10-04 00:02:40.187","messageId":0,"_rc":0}
2014-10-03 19:02:40.195 DEBUG   MSG          sup.mbs.13 [com.sybase.sup.server.util.ReplySender] [] [] sending Message ( queue=[sup.mbs.412#MobileWorkflow:1SE091OBMO.exeR], cid=[412#MobileWorkflow:1], method=[replayFailed])
2014-10-03 19:02:40.196 DEBUG   MSG          sup.mbs.13 [com.sybase.sup.server.util.ReplySender] [] [] sending Message ( queue=[sup.mbs.412#MobileWorkflow:1SE091OBMO.exeR], cid=[412#MobileWorkflow:1], method=[replayFailed])
2014-10-03 19:02:40.197 ERROR   MMS          sup.mbs.13 [com.sybase.djc.log.SystemExceptionLog] [] [] com.sybase.djc.SystemException was thrown by method com.sybase.sup.server.mbs.MessageReceiver.process(javax.jms.Message)\ncom.sybase.djc.SystemException: com.sybase.sup.server.mbs.SubscriptionManager.replyWithFailure(com.sybase.afx.json.JsonMessage, java.lang.Object, com.sybase.afx.json.JsonArray, boolean)
 at com.sybase.sup.server.mbs.MessageReceiver.process(MessageReceiver.java:810)
 at com.sybase.sup.server.mbs.MessageReceiver_DJC.access$001(MessageReceiver_DJC.java:4)
 at com.sybase.sup.server.mbs.MessageReceiver_DJC$1.invoke(MessageReceiver_DJC.java:27)
 at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:857)
 at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:759)
 at com.sybase.sup.server.mbs.MessageReceiver_DJC.process(MessageReceiver_DJC.java:45)
 at com.sybase.sup.server.runtime.AbstractMessageReceiver.run(AbstractMessageReceiver.java:111)
Caused by: com.sybase.djc.transaction.TransactionRolledbackSystemException: com.sybase.sup.server.mbs.SubscriptionManager.replyWithFailure(com.sybase.afx.json.JsonMessage, java.lang.Object, com.sybase.afx.json.JsonArray, boolean)
 at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:1023)
 at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:759)
 at com.sybase.sup.server.mbs.SubscriptionManager_DJC.replyWithFailure(SubscriptionManager_DJC.java:29)
 at com.sybase.sup.server.mbs.SubscriptionManager.replyWithFailure(SubscriptionManager.java:776)
 at com.sybase.sup.server.mbs.MessageReceiver.processMessage(MessageReceiver.java:702)
 at com.sybase.sup.server.mbs.MessageReceiver.process(MessageReceiver.java:799)
 ... 6 more
Caused by: java.lang.NumberFormatException: For input string: "MobileWorkflow:1"
 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
 at java.lang.Integer.parseInt(Integer.java:495)
 at java.lang.Integer.parseInt(Integer.java:530)
 at com.sybase.sup.server.util.ReplySender.getClientCidAsInt(ReplySender.java:259)
 at com.sybase.sup.server.util.ReplySender.sendDirect(ReplySender.java:91)
 at com.sybase.sup.server.util.ReplySender.sendMessage(ReplySender.java:70)
 at com.sybase.sup.server.mbs.SubscriptionManager.sendMessage(SubscriptionManager.java:587)
 at com.sybase.sup.server.mbs.SubscriptionManager.replyWithFailure(SubscriptionManager.java:881)
 at com.sybase.sup.server.mbs.SubscriptionManager_DJC.access$001(SubscriptionManager_DJC.java:4)
 at com.sybase.sup.server.mbs.SubscriptionManager_DJC$1.invoke(SubscriptionManager_DJC.java:25)
 at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:857)
 ... 11 more


Read more...

Environment

  • Sybase Unwired Platform 2.1.3
  • Upgraded to Sybase Unwired Platform 2.2.4
  • Upgraded to SAP Mobile Platform 2.3.4
  • iOS 7/8 device
  • Windows 2008r2 Server

Product

SAP Mobile Platform 2.3 ; SAP Mobile Platform 3.0 ; Sybase Unwired Platform 2.1 ; Sybase Unwired Platform 2.2

Keywords

  • HWC
  • Workflow
  • server response time out
  • upgrade
  • install
, KBA , MOB-SUP-WRK , Sybase Mobile Workflow , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.