Learn about known issues and apply workarounds for Unwired Platform runtime components.
Issue # | Description |
---|---|
RTC-361 | Clear domain logs before 2.1.3 upgrade Explanation: Upgrade to SUP 2.1 ESD#3 will change the DB schema for the domain log DB. If there are too many log entries, the time to complete the upgrade is greatly increased. Workaround: Clear all domain log entries before performing the upgrade. |
RTC-360 | Backing up the Sybase Unwired Platform Runtime installation fails
because the Sybase Control Center path is too
long. Explanation: The path to the Embedded Web Container in the SCC-3_2 folder is too long for Windows to process. Workaround: Before backing up the Sybase Unwired Platform Runtime installation, you must delete the contents of SUP_HOME\services\EmbeddedWebContainer\container\Jetty-6.1.22\work. You must delete the contents of this folder from the command prompt, and not from Windows Explorer. |
RTC-359 | Upgrade cannot proceed because GWC.war cannot be
deployed. When running the 2.1.3 upgrade from a command prompt window with a path that has a lowercase drive letter, the update may produce an error that indicates that it was unable to undeploy GWC.war. This only affects the listed updates with the specific circumstance where the drive letter is lowercase. Workaround: To recover, perform the following steps:
|
CR 729104 | DCN JSON parsing error Explanation: When trying to push an upsert to the CDB, where a string has a special value (such as % or &) a parsing error is thrown. According to World Wide Web Consortium (W3C) and Internet Engineering Task Force (IETF) specifications, url and form data must be encoded before being sent to the server. Only alphanumerics [0-9, a-z, A-Z], the special characters contained in the parentheses ($ - . ! * ' () , ), and reserved characters used for specific reserved purposes may be used unencoded within a URL. Please refer to http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#h-17.13.4.1 and http://www.ietf.org/rfc/rfc2045.txt for details. Workaround: The Unwired Server takes uft-8 as a URL encoded charset. So, if the client sends a request using either the GET or POST method, the request content must be encoded by utf-8 according to the URL encoding rules. For example, the URL http://serverhost:8000/dcn/DCNServlet?cmd=dcn&username=supAdmin&password=s3pAdmin&domain=default&package=sup101:1.0&dcn_request={"pkg":"dummy","messages":[{"id":"4","mbo":"Customer","op":":upsert","cols":{"id":"10004","fname":"B%B"}}]} has reserved and special characters {} [] : " %. These chars should be encoded. If you use java to make the DCN request, use
URLEncoder.encode(parameter,"UTF-8") to encode your
URL query parameter or post form data before you make the request. For
example, if you construct the URL listed in the previous example, you would
use the following
code:
String url="http://serverhost:8000/dcn/DCNServlet?cmd=dcn&username=supAdmin&password=s3pAdmin&domain=default"; url+="&package="+URLEncoder.encode("sup101:1.0","UTF-8"); url+="&dcn_request="+URLEncoder.encode("sup101:1.0","{\"pkg\":\"dummy\",\"messages\":[{\"id\":\"4\",\"mbo\":\"Customer\",\"op":\":upsert\",\"cols\":{\"id\":\"10004\",\"fname\":\"B%B\"}}]}"); |