Testing Update: Contact Your System Administrator
I started perf testing one of the ESB products today and immediately discovered that it wasn't responding as expected. Okay, no problem, I'll just remove the extra message logging I put it while building an orchestration and restart the test....
January 11, 2006
![Network Computing logo Network Computing logo](https://eu-images.contentstack.com/v3/assets/bltde8121fc52c5c8f3/blt3f3d0318f746b1c2/65a530e4187606040a1d8b8c/placeholder.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
I started perf testing one of the ESB products today and immediately discovered that it wasn't responding as expected. Okay, no problem, I'll just remove the extra message logging I put it while building an orchestration and restart the test.Wait...it's still not responding. What is this? 2095 active BPEL processes? Hmmm...okay, there's a delete button. I should just be able to push the button and the process will go away...sure, I have to do it 2095 times but hey, better than nothing. What's this? A Java exception? On the console? What do you mean, "Contact your system administrator". I am the system administrator and I can assure you I have no idea what this generic exception is trying to say. Maybe the log has more information...ummm, yeah. A stack trace. Oooh, and another copy of the exception message thrown on the admin console. That's nice. But why, exactly, was this exception thrown?
Was it privileges? Is the manager not responding? Solar Flares?? Magnetized shoes??!?! What?
A general exception error that is printed out on the screen with no clue as to what really happened is less useful than just saying "Yo, that didn't work!". Ya gotta give me something more to go on here, people!Please?
You May Also Like
Maximizing cloud potential: Building and operating an effective Cloud Center of Excellence (CCoE)
September 10, 2024Radical Automation of ITSM
September 19, 2024Maximizing Manufacturing Efficiency with Real-Time Production Monitoring
September 25, 2024