IBM Support

PJ41242: If a date field is left empty on a solution configured with an external data service, it returns an "Unparseable date" error.

Direct links to fixes

IBM Case Manager V5.1.1 Fix Pack 3 for Linux for System z
IBM Case Manager V5.1.1 Fix Pack 3 for Windows
IBM Case Manager V5.1.1 Fix Pack 3 for Solaris
IBM Case Manager V5.1.1 Fix Pack 3 for Linux
IBM Case Manager V5.1.1 Fix Pack 3 Client for Linux for System z
IBM Case Manager V5.1.1 Fix Pack 3 Client for Windows
IBM Case Manager V5.1.1 Fix Pack 3 Client for Solaris
IBM Case Manager V5.1.1 Fix Pack 3 Client for Linux
IBM Case Manager V5.1.1 Fix Pack 3 Client for AIX
IBM Case Manager V5.1.1 Fix Pack 3 for AIX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For a solution that has been configured with an external data
service, if a date or time field or property is left empty, it
will
result in a "java.text.ParseException: Unparseable date:" error.

This causes the following error on the client:

A system error occurred. (CDEWG1017E)
FNRPA0084E An internal server error occurred while running a
Case REST API method.

The following error can been in the application server's
SystemOut log:
===============
[5/10/13 16:09:16:372 PDT] 0000003f servlet       E
com.ibm.casemgmt.intgimpl.messages.CaseMgmtLogger error
java.text.ParseException: Unparseable date: ""

java.lang.IllegalArgumentException: java.text.ParseException:
Unparseable date: ""
	at
com.ibm.casemgmt.intgimpl.PropertyValueHolder.convertSingleValue
(PropertyValueHolder.java:231)
	at
com.ibm.casemgmt.intgimpl.PropertyValueHolder.setObjectValue(Pro
pertyValueHolder.java:133)
	at
com.ibm.casemgmt.rest.handlers.PropertiesJSONConverter.getProper
tyValueFromJSONable(PropertiesJSONConverter.java:150)
	at
com.ibm.casemgmt.rest.handlers.CaseTypeHandler.fetchPropertiesFr
omChanges(CaseTypeHandler.java:286)
	at
com.ibm.casemgmt.rest.handlers.CaseTypeHandler.startFetchingProp
ertiesFromChanges(CaseTypeHandler.java:241)
	at
com.ibm.casemgmt.rest.handlers.CaseTypeHandler.startCaseTypeOper
ation(CaseTypeHandler.java:198)
	at
com.ibm.casemgmt.rest.handlers.CaseTypeHandler.onPost(CaseTypeHa
ndler.java:74)
	at
com.ibm.casemgmt.rest.ACMRESTServlet.doMethod(ACMRESTServlet.jav
a:372)
	at
com.ibm.casemgmt.rest.ACMRESTServlet.doPost(ACMRESTServlet.java:
247)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1657)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1597)
	at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
FilterChain.java:104)
	at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAp
pFilterChain.java:77)
	at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
ppFilterManager.java:908)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:934)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:502)
	at
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest
(ServletWrapperImpl.java:181)
	at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques
t(CacheServletWrapper.java:91)
	at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
java:864)
	at
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai
ner.java:1592)
	at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
k.java:186)
	at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
imination(HttpInboundLink.java:452)
	at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe
quest(HttpInboundLink.java:511)
	at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ
est(HttpInboundLink.java:305)
	at
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet
e(HttpICLReadCallback.java:83)
	at
com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadComplet
edCallback.complete(SSLReadServiceContext.java:1784)
	at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp
leted(AioReadCompletionListener.java:165)
	at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn
cFuture.java:217)
	at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC
hannelFuture.java:161)
	at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
	at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
	at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
ler.java:775)
	at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
Caused by: java.text.ParseException: Unparseable date: ""
	at java.text.DateFormat.parse(DateFormat.java:348)
	at
com.ibm.casemgmt.intgimpl.PropertyValueHolder.convertStringToDat
e(PropertyValueHolder.java:274)
	at
com.ibm.casemgmt.intgimpl.PropertyValueHolder.convertSingleValue
(PropertyValueHolder.java:227)
	... 35 more

===============

Local fix

  • Fill in any date or time fields or properties.

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* IBM Case Manager developers who have configured their        *
* Solution to use an external data service and date/time       *
* fields.                                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to 5.1.1.2-ICM-FP002.                                 *
****************************************************************

Problem conclusion

  • Fixed in 5.1.1.2-ICM-FP002.  Solutions that use date/time fields
with an external data service will no longer get an
error/exception.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PJ41242
    • 

  • Reported component name
    CASE MGR CLIENT
    • 

  • Reported component ID
    5725A1501
    • 

  • Reported release
    511
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2013-05-16
    • 

  • Closed date
    2013-10-25
    • 

  • Last modified date
    2013-10-25
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    

  • Fixed component name
    CASE MGR CLIENT
    • 

  • Fixed component ID
    5725A1501
    • 



Applicable component levels


    

  • R511  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.1","Edition":"","Line of Business":{"code":"","label":""}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            23 July 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback