[binyan]

We use bloatsphere and for production we need to send startup and shutdown args. ME supports startup args for all the server connectors, but only shutdown args for some of them like jboss. This support needs to be expanded universally. One extra text field and the appending of that text field to the shutdown command line would allow users like myself to gracefully shut down crapshere instead of using a seperate desktop icon or just terminating the vm.

[Riyad Kalla]

lol, sounds like Websphere is giving someone some trouble.

I’ve sent your request along. It, as usual, makes a sense and we should have it.

[Scott Anderson]

binyan,

So you’re saying that our shutdown action for WebSphere isn’t working properly for you? Can you give me an example of what you’re trying to do so I can write up the enhancement request properly?

[binyan]

Actually websphere (see I can be nice) is working like it always has, I just find it annoying that everything that comes out of big blue is soooo frickin big and complicated. The company that created websphere is the same company that created a unix even a mother would try and drown at birth, AIX.

Anyhoo, what I need is a way to pass shutdown args to websphere since we have this custom authentication setup. Essentially anyone can startup the server, but only certain ones can gracefully shut it down. I encountered this previously, but it wasn’t until last night that I realized that you all include “Optional Shutdown” args for some of the app server connectors and not others. I can see no reason why this functionality would not be beneficial to all the connectors. Just look at the jboss connectors and then the websphere connectors and hopefully the defect (maybe streching it a bit here) should be clear.

[Scott Anderson]

The company that created websphere is the same company that created a unix even a mother would try and drown at birth, AIX.

😆

I realized that you all include “Optional Shutdown” args for some of the app server connectors and not others.

Yes, this is basically because some servers seem to ‘require’ optional arguments, if that makes sense, in order to shut down properly.

I can see no reason why this functionality would not be beneficial to all the connectors.

It’s not so much a matter of benefit as prioritization. Each thing we add, no matter how small, takes some amount of development resources to implement and test. That means that while we’re working on that, we’re not working on something else. Since this is the first request we’ve actually gotten to add shutdown arguments to websphere, I think you can see why it was prioritized rather lowly. 🙂

I’ll add the enhancement request.

[Scott Anderson]

I spoke with one of the devs and he said he’d add it in 2.8 beta 2.

[binyan]

I can definitely relate that time spent on one piece of functionality is time not spent on another. I’m glad to read that this issue will be addressed in the 2.8 beta 2 (and 3.8 beta 1 perhaps) releases.

[Scott Anderson]

No problem. The enhancement has already been checked into HEAD so you’ll see it in the next release for either version.

[Author]

Posts