Menu

#779 FVT: Inexplicit error when op is invoked on closed client

closed-fixed
5
2007-05-29
2007-05-08
lupusalex
No

If a WBEMClient instance was closed using the close() method and afterwards an operation (e.g. enumerateInstances()) is invoked, the client throws a WBEMException "CIM_ERR_FAILED: Internal error". This is wrong because CIM_ERR_FAILED indicates a message from the CIMOM and moreover "internal error" is very inexplicit.

I suggest chaging the WBEMClientCIMXML so that it tracks the initialization and closure state. Whenever an operation is invoked on a non initialized or already closed client a specific IllegalStateException is thrown that contains a meaningful message.

Discussion

  • lupusalex

    lupusalex - 2007-05-08
    • summary: Inexplicit error when operation is involed on closed client --> Inexplicit error when operation is invoked on closed client
     
  • lupusalex

    lupusalex - 2007-05-08

    Patch

     
  • lupusalex

    lupusalex - 2007-05-08

    Logged In: YES
    user_id=1363884
    Originator: YES

    File Added: patch_1714853.txt

     
  • lupusalex

    lupusalex - 2007-05-09
    • assigned_to: lupusalex --> willi_wacker
    • status: open --> pending-fixed
     
  • lupusalex

    lupusalex - 2007-05-10
    • summary: Inexplicit error when operation is invoked on closed client --> FVT: Inexplicit error when op is invoked on closed client
    • status: pending-fixed --> open-fixed
     
  • lupusalex

    lupusalex - 2007-05-10
    • status: open-fixed --> pending-fixed
     
  • lupusalex

    lupusalex - 2007-05-29

    Logged In: YES
    user_id=1363884
    Originator: YES

    The patch was picked up by release 2.0.2 and will be closed.

     
  • lupusalex

    lupusalex - 2007-05-29
    • status: pending-fixed --> closed-fixed
     

Log in to post a comment.