Announcement

Collapse
No announcement yet.

How bad is CU04

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ianlo
    replied
    Re: How bad is CU04

    Hi Caleb,

    Thanks for the encouragement! Because it is so close to my go-live (25 lanes, 10 customers) and the users need to go through the UAT, I had no choice but to revert back to CU3 RU5.

    The main show stopper was when I was not able to execute a stored procedure from and Order Base Created action. The funny thing was that the stored procedure was actually being called (from the logs) but somehow any DML statements in the stored procedure was either not executed or not committed.

    Also the problem with agents not raising exceptions (intermittent occurance) was a huge issue as it was working in CU3 and I have several funky "recursive" agent flows that depend on this...

    Hope you have a smoother time with CU4 than I did and Good Luck!

    Ian

    Leave a comment:


  • ianlo
    replied
    Re: How bad is CU04

    Originally posted by chrisplough View Post
    Ian,

    Just to check - have you applied the RU01 patch for CU04? Since CU04 was such a big release - many issues are resolved within this patch.

    --Chris
    Hi Chris,

    Yep I did install CU4 RU1 for my testing. It was quite unfortunate that I was encountering these issues. I had to revert back to CU3 RU5 so that my UAT can proceed and am trying to reduce the go-live risk.

    Ian

    Leave a comment:


  • cwarner
    replied
    Re: How bad is CU04

    Ian,

    We found many problems when we started CU4 testing as well.

    One of the points that I remember specifcally was that we had some issues that were apparently caused by having a carriage return in our SQL statement. While this should not have caused any issue in the statement, OTM was unable to handle it, and it needed to be removed (This statement was working just fine in CU2)

    We also had an issue about the number of rate records associated with a given lane. Because of how this had been coded, OTM was allocating resources exponentially for each additional carrier (We found this issue in CU2). This issue was supposed to be fixed in CU4, but the new coding actually caused the system to crash repeatedly (talk about it going wrong). It took us over 50 days with an active SR to get this issue resolved and Keith had to work directly with Development.

    Since resolving these issues, we have been moving fairly smoothly through our testing. So while just a few weeks ago I would have suggested that you abandon all hope in CU4, I now am more willing to suggest working through the issues if possible.

    Leave a comment:


  • chrisplough
    replied
    Re: How bad is CU04

    Ian,

    Just to check - have you applied the RU01 patch for CU04? Since CU04 was such a big release - many issues are resolved within this patch.

    --Chris

    Leave a comment:


  • ianlo
    started a topic How bad is CU04

    How bad is CU04

    Hi everyone,

    I am having a nightmare with CU04. The installation of CU04 was tricky enough but I managed to get it installed. Then I began to encounter many issues.

    Is it worth migrating to CU04? Is anyone else facing application issues or is it just me? - I am stuck in CU03 until the issues are fixed. My issues with CU04 are as follows:

    1) Order Base Agent Event (Order Base - Created) not working for stored procedures. y stored procedures are executing but any update statements are not being persisted - (and yes I have tried it with a simple SQL that CANNOT go wrong)

    2) ERU Planning is not being applied when planning across domains

    3) Order Movement - Move To Shipment returns java.lang.NullPointer exception

    4) Agents that encounter exceptions sometimes continue on and do not report an error

    Is anyone else encountering application issues?

    Ian
Working...
X