Giter Site home page Giter Site logo

Comments (3)

hansenmc avatar hansenmc commented on June 15, 2024

This would indicate a lower-level issue, possibly an issue with XCC, and not necessarily a CORB issue/bug. Unless you would want CORB to handle the exception differently, such as retry when the exception is thrown.

Is this a repeatable error? Does this error occur every time, or only occasionally? Have you tried with the latest XCC 8.0.5?

from corb2.

rjkennedy98 avatar rjkennedy98 commented on June 15, 2024

@hansenmc Yes, I agree its an XCC issue. I'm not able to recreate the error myself. It gets throw intermittently in all our environments, but I'm not sure if its because of a particular data condition or if its something transient like a network issue. Without being able to recreate it, its hard for us to test with another version of XCC. We run more than tens of thousand CORB jobs per day in our production environment and we see maybe 4 of these errors.

We are happy with the way CORB handles this, this issue was filed per Support's request and I am fine if you want to close it out.

from corb2.

bbandlamudi avatar bbandlamudi commented on June 15, 2024

@rjkennedy98 - we can use the statement "We run more than tens of thousand CORB jobs per day in our production" to market CoRB2.

I haven't encountered SSL handshake issues in CorB, primarily because Aetna is probably the only project using this. However, in my previous we used to run into handshake problems due to intermittent network connectivity issues. This particular issues appeared to related to stream corruption, a flavor which we see in non-SSL environments as well. We used to see this quite a bit when we were using xcc 6 with ML 7, but not much these days. XCC should automatically retry some of these transactions automatically, but if not, you can always configure CorB 2.3.1 to do the same. The retry feature has been added to handle issues similar to these (intermittent or non-reproducible).

However, please be cautions with updates. Since this is a network communication error, not necessarily a transaction failure, we need to check in the code if the update is already committed.

from corb2.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.