IBM Support

JR59874: YOU SEE THE URISYNTAXEXCEPTION DURING ONLINE SNAPSHOT DEPLOYMENT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

workflow.18002.delta.repository

 

APAR status

  • Closed as program error.

Error description

  • After you enable "AUTHENTICATE WHEN ANY URI IS ACCESSED" in IBM
Process Server's admininistrative console, you see the
URISYNTAXEXCEPTION in the SystemOut.log file while deploying
snapshots:

[7/4/18 17:24:06:338 CEST] 000001a3 wle           E
CWLLG2229E: An exception occurred in an EJB call.  Error: The
following error occurred when attempting to retrieve messages
from the Process Server using address: null

com.lombardisoftware.core.TeamWorksException: The following
error occurred when attempting to retrieve messages from the
Process Server using address: null
    at
com.lombardisoftware.server.ejb.repositoryservices.InstallMessag
esSupport.getInstallMessages(InstallMessagesSupport.java:205)
    at
com.lombardisoftware.server.ejb.repositoryservices.RepositorySer
vicesCore.getInstallMessages(RepositoryServicesCore.java:425)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
...


Caused by: java.net.URISyntaxException: Illegal character in
path at index 0: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

...
</html>
/installMessages
    at java.net.URI$Parser.fail(URI.java:2859)
    at java.net.URI$Parser.checkChars(URI.java:3032)
    at java.net.URI$Parser.parseHierarchical(URI.java:3116)
    at java.net.URI$Parser.parse(URI.java:3074)
    at java.net.URI.<init>(URI.java:599)
    at
com.lombardisoftware.server.ejb.repositoryservices.InstallMessag
esSupport.getInstallMessages(InstallMessagesSupport.java:178)
    ... 82 more

Local fix

  • 



Problem summary


    

  • When IBM Process Center tries to call Process Server's Teamworks
 application to get the endpoint of the deployment servlet, it
fails with the URISYNTAXEXCEPTION because the Teamworks app does
 not support basic authentication.

PRODUCTS AFFECTED:
IBM Business Process Manager (BPM) Advanced
IBM BPM Standard
IBM BPM Express
IBM BPM

    



Problem conclusion


    

  • A fix that directly calls the deployment servlet with basic
authentication instead of the Teamworks application will be
included in a future release of IBM Business Automation
Workflow.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR59874
    • 

  • Reported component name
    BPM
    • 

  • Reported component ID
    5737A5700
    • 

  • Reported release
    860
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2018-08-09
    • 

  • Closed date
    2018-09-13
    • 

  • Last modified date
    2018-09-13
    • 





    

  • 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
    BPM
    • 

  • Fixed component ID
    5737A5700
    • 



Applicable component levels


    








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            14 September 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback