as-utils.w Cancel The title field is required!

1. Roger Blanchard

   

   434 posts
   Registered:
   29 Jun 2018
   6 hours ago

   Link to this post

   Have there been any recent changes to the reconnect logic? It was just reported that they reconnect dialog no longer appears and just an error message informing the user that they are disconnected. This error will appear over and over as the KeepAlive service fires. 
   
   I have confirmed that we are using the as-utils.w distributed by CW. 
   
   Before we spend too much time trying to track this dow,n I just wanted to make sure there was not any recent changes that would require us to modify our code.
   
   Thank you.
   
   
   
   appServerConnect adecomm/as-utils.w at line 390  (.\adecomm\as-utils.r)
   ConnectService Consultingwerk.Framework.AppServerServiceManager at line 724  (Consultingwerk/Framework/AppServerServiceManager.r)
   ConnectService Consultingwerk.OERA.ServiceAdapter at line 896  (Consultingwerk/OERA/ServiceAdapter.r)
   ConnectService Consultingwerk.OERA.ServiceAdapter at line 846  (Consultingwerk/OERA/ServiceAdapter.r)
   RetrieveData2 Consultingwerk.OERA.ServiceAdapter at line 19251  (Consultingwerk/OERA/ServiceAdapter.r)
   RetrieveData Consultingwerk.SmartComponents.Implementation.SmartBusinessEntityAdapter at line 4715  (Consultingwerk/SmartComponents/Implementation/SmartBusinessEntityAdapter.r)
   RetrieveData Consultingwerk.SmartComponents.Implementation.SmartBusinessEntityAdapter at line 5413  (Consultingwerk/SmartComponents/Implementation/SmartBusinessEntityAdapter.r)
   RetrieveData Osprey.CustomClasses.SmartComponents.OspreyBusinessEntityAdapter at line 142  (Osprey/CustomClasses/SmartComponents/OspreyBusinessEntityAdapter.r)
   PriceToolbar_ToolClick Osprey.Host.Price.PriceMaintForm at line 318  (Osprey/Host/Price/PriceMaintForm.r)
   OnToolClick Consultingwerk.SmartComponents.Implementation.SmartToolbarController at line 2737  (Consultingwerk/SmartComponents/Implementation/SmartToolbarController.r)
   OnToolClick Osprey.CustomClasses.SmartComponents.OspreyToolbarController at line 806  (Osprey/CustomClasses/SmartComponents/OspreyToolbarController.r)
   SetupApp.p at line 193  (SetupApp.r)
   OspreyHost at line 586  (OspreyHost.r)
   
   Shown by:
   ShowErrorMessage Consultingwerk.Util.ErrorHelper at line 3381  (Consultingwerk/Util/ErrorHelper.r)
   ShowErrorMessage Consultingwerk.Util.ErrorHelper at line 3259  (Consultingwerk/Util/ErrorHelper.r)
   RetrieveData Consultingwerk.SmartComponents.Implementation.SmartBusinessEntityAdapter at line 5601  (Consultingwerk/SmartComponents/Implementation/SmartBusinessEntityAdapter.r)
   RetrieveData Osprey.CustomClasses.SmartComponents.OspreyBusinessEntityAdapter at line 142  (Osprey/CustomClasses/SmartComponents/OspreyBusinessEntityAdapter.r)
   PriceToolbar_ToolClick Osprey.Host.Price.PriceMaintForm at line 318  (Osprey/Host/Price/PriceMaintForm.r)
   OnToolClick Consultingwerk.SmartComponents.Implementation.SmartToolbarController at line 2737  (Consultingwerk/SmartComponents/Implementation/SmartToolbarController.r)
   OnToolClick Osprey.CustomClasses.SmartComponents.OspreyToolbarController at line 806  (Osprey/CustomClasses/SmartComponents/OspreyToolbarController.r)
   SetupApp.p at line 193  (SetupApp.r)
   OspreyHost at line 586  (OspreyHost.r)
2. Mike Fechner

   

   365 posts
   Registered:
   14 Sep 2016
   47 minutes ago in reply to Roger Blanchard

   Link to this post

   I have just tested the re-connect behavior and it's still working. We have switched from ROUTINE-LEVEL to BLOCK-LEVEL error handling there a few weeks back (16.11.2025). The most recent change before that was from 2013. 
   
   The AppServerServiceManager - the wrapper to as-utils.w was modified in September this year with BLOCK-LEVEL. And the change before that was from 2022.
   
   But adding BLOCK-LEVEL would only strengthen the error handling at all.
   
   Please double-check that those customers are really using _our_ as-utils.w.
   
   If that does not help, please log a support ticket and we'll investigate this. The
   
   "just an error message informing the user that they are disconnected."
   
   Is that _our_ message dialog - or the default Progress/Windows dialog?
3. Roger Blanchard

   

   434 posts
   Registered:
   29 Jun 2018
   35 minutes ago in reply to Mike Fechner

   Link to this post

   >> just an error message informing the user that they are disconnected.
   >> Is that _our_ message dialog - or the default Progress/Windows dialog
   
   It is your message dialog. 
   
   >> Please double-check that those customers are really using _our_ as-utils.w.
   I did verify as I can see the AppServerConnectionException being thrown.
   
   I do have a question.
   
   Let's day the application is sitting at the Main Menu and the Keep Alive process is firing every 120 seconds. If the client gets disconnected should an error be displayed every 120 seconds from the TimerTickHandler in the KeepAliveService? This particular user left for lunch for an hour and when they came back, they had 30 messages to click through.
4. Mike Fechner

   

   365 posts
   Registered:
   14 Sep 2016
   11 minutes ago in reply to Roger Blanchard

   Link to this post

   Looks like it's working fine for "regular" calls - but something's wrong with the keep alive calls. And once we were in the issue with the KA calls it's not working for regular calls as well. We need to get that into JIRA and investigate that. 
   
   If you want to keep in the loop, please log a support desk ticket.
5. Roger Blanchard

   

   434 posts
   Registered:
   29 Jun 2018
   7 minutes ago in reply to Mike Fechner

   Link to this post

   Will do. Thanks Mike and Merry Christmas to you and everyone at CW!
6. Mike Fechner

   

   365 posts
   Registered:
   14 Sep 2016
   5 minutes ago in reply to Roger Blanchard

   Link to this post

   Same to you!