FILENET CONTENT NAVIGATOR ISSUES

Get random jiServerException in viewer when trying to open a tif file

Mar 11, 2014 | Tags: none

This question has not been answered yet.

Randomly when opening a tif file I get an error in ICN Daeja viewer

Unable top open <https://ecm.........

Error:ji.net.jiServerException:

Server did not respond with OK

Error: IO error: null

When I try to open a 2nd time it will open.

Thanks,

Tom Larson

Costco ECM

• Log in to reply.

• 
  

  

  JI P8AE

  39 Posts

  Re: Get random jiServerException in viewer when trying to open a tif file

  Mar 12, 2014  in response to Tom Larson

  Hi Tom,

  Are you running a cluster or through any firewalls there?

  If there are no problems opening image type documents, other than TIFF and PDF, it might have something to do with streaming.

  • Log in to reply.
  • 
    

    

    Tom Larson

    9 Posts

    Re: Get random jiServerException in viewer when trying to open a tif file

    Mar 12, 2014  in response to JI P8AE

    Hi James,

    
    

    It is on our test system.  It runs through a firewall but a single ICN instance.

    
    

    I have also scene the following error.

    
    

    Unable to open <.......

    
    

    Error:Annotation Exception

    
    

    Annotations failed to load

    (java.io.IOException:

    
    

    Server returns HTTP response code: 408 for URL: https.....  getDocument.dl?docid=....

    
    

    This is hit or miss.  It will open 15 tiff's fine then will throw an error on one.  When I open it a second time it may or may not load correctly.

    • Log in to reply.
    • 
      

      

      JI P8AE

      39 Posts

      Re: Get random jiServerException in viewer when trying to open a tif file

      Mar 12, 2014  in response to Tom Larson

      For those kinds of errors, I would normally expect it to either consistently succeed or consistently fail. 

      Signed into ICN from Firefox, with firebug installed, or from google Chrome browser (do you have either of these?), can you hit the F12 key to open the debugger, and get a listing of the cookies?  One or more of them might be flagged HttpOnly.

      • Log in to reply.
      • 
        

        

        Tom Larson

        9 Posts

        Re: Get random jiServerException in viewer when trying to open a tif file

        Mar 13, 2014  in response to JI P8AE

        Anything specific I should be looking at?  Nothing is obviously wrong here.

        
        

        
        

        Attachments

        • •  
          • Capture.JPG 
          • 197 KB 
          • Download

        • Log in to reply.
        • 
          

          

          konapalligopi

          62 Posts

          Re: Get random jiServerException in viewer when trying to open a tif file

          Mar 17, 2014  in response to Tom Larson

          Even me toooo facing the same issue. Can you help me how resolve this kind of issue.  Thank you.

          Attachments

          • •  
            • FileNetViewerIssue.jpg 
            • 128 KB 
            • Download

          • Log in to reply.
          • 
            

            

            Diotima

            6 Posts

            Re: Get random jiServerException in viewer when trying to open a tif file

            Jun 10, 2014  in response to konapalligopi

            We have the same problem. Does anybody found a solution of this issue?

            • Log in to reply.
            • 
              

              

              Diotima

              6 Posts

              Re: Get random jiServerException in viewer when trying to open a tif file

              Jun 10, 2014  in response to Diotima

              We have sold this problem. Here the response:

              http://www-01.ibm.com/support/knowledgecenter/SSEUEX_2.0.1/com.ibm.installingeuc.doc/eucin019.dita?lang=en

              • Log in to reply.
• 
  

  

  fedila

  1 Post

  Re: Get random jiServerException in viewer when trying to open a tif file

  Apr 10  in response to Tom Larson

  Thanks Diotima,

  I have applied the IBM solution and working properly

  Regards

  • Log in to reply.

  Updated on Apr 10, 2015 at 5:36 AM by fedila

Disabling HTTPOnly settings for Java applets

WebSphere® Application Server Version 8 or later only. you must disable the HTTPOnly settings in WebSphere Application Server to enable IBM® Content Navigator to function properly. If you do not disable the HTTPOnly settings, features that use Java applets do not work.

About this task

When HTTPOnly settings are enabled in WebSphere Application Server, you cannot use the following features of IBM Content Navigator:

• Sending links or attachments from the web client
• Viewing documents in some viewers

If you do not want to disable the HTTPOnly settings in WebSphere Application Server, you must take the following actions:

• Use the administration tool to remove the options to send links or attachments from the menus in the web client.
• Use the administration tool to configure a viewer map that does not use any viewers that require a Java applet, such as the FileNet® Viewer and the Applet Viewer.

Procedure

To disable the HTTPOnly settings in WebSphere Application Server:

1. Log in to the WebSphere Application Server administrative console.
2. Navigate to Servers > Server Types > Websphere Application servers and select the server where you want to deploy IBM Content Navigator.
3. Select Session Management > Enable cookies and then clear the Set session cookies to HTTPOnly to help prevent cross-site scripting attacks option.
4. Save the changes to the master configuration.
5. If you use IBM Content Navigator to access IBM FileNet P8 repositories or an IBM Content Manager repository that is configured to use LTPA keys for authentication, you must also disable the HTTPOnly settings in the global settings:
   1. Navigate to Security > Global secuirty > Authentication > Web and SIP security > Single sign-on (SSO).
   2. Under General properties, clear the Set security cookies to HTTPOnly to help prevent cross-site scripting attacks option and click Apply.
   3. Save the changes to the master configuration.
6. Restart the web application server for your changes to take effect.

Parent topic: Preparing WebSphere Application Server for IBM Content Navigator

Related tasks:

Copying JDBC drivers to the web application server

Exporting the LTPA key from the Content Engine server (FileNet P8 only)