Every side of my window is filled with pine-tree and the beautiful vision of snow. But I have to struggle with Jax-RS in weblogic instead of snowball.

I used to be in an infrastructure maintenance team, and I worked with an old guy. We had a jump box we all used. This guy would work weekend maintenance windows and still be trying to get changes done at 7am, three hours after the end of the window. He was glacially slow. I remember watching him login to a prod weblogic server. He would open the Windows start menu, move his fucking mouse through two or three submenus, and finally click putty. Then, he would type out the FQDN of the jump server, and move his mouse to the connect/ok button. Then it would prompt him for his username and password, both of which took him about 90 seconds to single-finger type. Then, once loved into the jump box, he would then type ssh user@server.fqdn, rather than copying and pasting the server name.

It took him fully five minutes to get logged into the weblogic server. I could not take it. It would have taken me about ten seconds.

Me: there seems to be a problem in the Web Sphere app server...I would recommend u change it to weblogic

Client( IT division head of his company): is it compatible with websphere soap..??

Me: soap is generic, websphere is just an app server

Client: no but we have been told to use only websphere soap, is weblogic having that..??

Me: soap is protocol, app server is changeable..

Client: no we want only websphere soap.

Me:....(trying to find the nearest exit)

Weblogic Server won't start, broken build was auto-deployed. How does a broken build even get deployed? 🙄

Told "till the server is fixed work on your next-release bugs". Sure, can investigate, maybe even code fixes, but with a broken dev environment how do we test anything?

" Hmm..Oh yeah, right" 🤔

Why is it so f*cking difficult to get an application deployed locally with IntelliJ on a Weblogic <ancient version> application server in debug mode... thank you Oracle!

Forgot about a System.Exit();
Was wondering for 2h why my Weblogic Server shuts down immediately after deploying my Webservice...

I never felt so bad at Programming..

Co-worker: My local Weblogic instance doesn't work when my IP changes :c
Me: Lemme help you with that.
Me: *tries bunch of stuff and nothing* Weird...
Me: *checks his hosts file, localhost is mapped to old IP* KILL YOURSELF OR I WILL.

- Eclipse (especially when plugged in with any SCM, excluding Che)
- RichFaces / PrimeFaces (from the pre SPA era)
- WebLogic (how many times do you need to be restarted in a day? )
- SOAP (not a dev technology, but even as a protocol. Thank You Microsoft !!!)
- Struts (what were you doing at the same time as Spring ??? )
- GWT (how did this even find its place inside Google? )

Need more time a deeper retrospective of each dev tech I've come across :(

Firs time using WebLogic. 20 clicks later and I still haven't been able to deploy!

All hail the mighty Weblogic Server!!

Weblogic

Why? It takes forever to start up and shut down.

!rant
Yoo fellow devs... And sysAdmins??
We're tasked with migrating our apps from current HP UX server to RHEL...
Most of our apps run on Tomcat 7 and weblogic...
We also have Oracle DB Enterprise Edition...
Just wondering if any of you out there from the stone age have done this recently... Any tips.. Warnings... Advice on the matter??