Win a copy of Rust Web Development this week in the Other Languages forum!

Vijaya Patil

+ Follow
since Sep 02, 2011
Vijaya likes ...
IBM DB2 Spring Java
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Vijaya Patil

I am seeing this warning in our production websphere application server (WAS 7) system out logs -

[8/31/14 9:14:50:455 EDT] 0000001f ThreadMonitor W WSVR0605W: Thread "WebContainer : 974" (0000040d) has been active for 623003 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.

The application server transaction timeout is set to 120 second
DB2 time out is -1 (wait forever until lock is granted or deadlocks happens)
Thread monitor configurations are not known and I am trying to get that information.

I am also in process of getting the db2 logs and javacore logs to analyse the issue further but I have one question as why would the thread hung for so long.
In situation where the transaction is unable to get the lock and waits for it beyond 120 second, application server should rollback the transaction after 120 second and the thread should also be released.
But this isn't happening here. Please help me understand why do we see web container thread hung for such a long time (623003 milliseconds)?

7 years ago
Thanks Jimmy I will take note of that.

I was busy with different priority in project so coming back to this I have another question -

After going through your links and some other stuff I know of following approaches which can be implemented.
I want to know which one is better

1. Configure username/password for each web service operation invocation.
2. Configure username/password to invoke authenticate() operation first which will generate a token and send it back to client.
Client to use this token to call subsequent web services operation.

or let me know if there is any better approach other than these.

10 years ago

Ulf Dittmer wrote:Sounds like the service does not use authentication. A username/password scheme would be a good start. If I may point to something I've written, start reading at and then Those articles assume that you are using the Apache Axis SOAP stack and its Rampart WS-Security module.

Thank you Ulf!!
I could implement WS-Security using Axis 1.5.x successfully using your doc. I will try to use Axis2 now.
10 years ago

I have written a web service for new user enrollment which will be used by our trusted 3rd party services but i found that anybody who come to know the web service url can enroll the user. Can you please let know what do i need to do to make sure that the request coming is coming from a valid party?

10 years ago

Ulf Dittmer wrote:You're in luck - The JavaIoFaq talks about this very problem!

Thanks Ulf for your quick reply

I am using a client app in which we need to make a SSL connection to the HOST. This code is written in a class and called from struts action class.

Now when the host is down for some reason the connect call keeps trying for 5 minutes blocking the underlying socket resources. The sockets getting blocked are more in number so this results in db connections getting queued. Once 5 min is over the queued request are processed and there is DB spike happening.

Since the code base uses JDK 1.4 I cannot use the setConnectTimeout() method.
I will really appreciate your help in knowing how can i stop blocking my resource for 5 minutes? Or Can I use any time counter of my own to forcefully avoid waiting for more time and refuse connecting?

Thanks a lot