Nikhil Joshi

Greenhorn
+ Follow
since Jun 28, 2008
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Nikhil Joshi

Hi,

We are using a Logging Utility much similar to LOG4j.

We are logging some information at DEBUG,INFO,ERROR levels.

However, I observed that in case of multiple concurrent requests, DEBUG and INFO logs degrades performance significantly.
Is it common behavior of every loggers?

Is it advisable to keep DEBUG/INFO level logs enabled in the Production Environment ?

As a requirement we need to log some critical information into production environment, but not with a cost of performance.

~Please Advice in this situation.

Thanks,
Nikhil


15 years ago
Thanks Jeanne,
That solved my problem.
15 years ago
Hi,

I want to write an Ant task,for an EJB project to deploy on WebSphere 6.1v
Got few doubts regarding this:

1. I found multiple tasks to generate stubs, Like:

a] <ejbjar ...> <websphere....>

I faced problem using this, it was dificult for me to identify , Which jars to be in classpah. JARs mentioned in the Ant manual were not enough. Also I could not find boot.jar with my websphere 6.1 (EJBs are getting deployed fine using RAD).

b] <ejbDeploy>


My questions are:

1. Which one is easier and better to use?

2. <ejbDeploy> --- does it require RAD to be installed ? As build machine won't have that.

3. Do I need to write task to compile bean, home, remote java files, ---package them into JAR before calling any above [a]/[b] deployment task ?
Or above tasks will do all these things.

4. Any working example will be much helpful.

Thanks,
Nikhil
15 years ago
Hi,

I am calling Stored procedure from my application.
Data base is DB2, server is Websphere 6.1 and driver type is DB2 JDBC Type 4 driver.

Most of the time SP gets executed properly from Java but sometimes it gives following exception:

[ibm][db2][jcc][t4][2055][11259] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
The command requested could not be completed because of a permanent error condition detected at the target system.

Does anybody have any idea about this?

Thanks
Nikhil
Ok..you are right..

So here is my understanding of entire scenario , please correct me if i goes wrong...

So Lets say I set bean pool size min to 20 and max to 200.....

1. Till 20 concurrent requests will be served directly without any pooling.
[ that many instances of bean create, right? ]

2. In case of say 50 concurrent requests ....... 30 requests/bean instances will be pooled while serving 20 directly.

3. what will happen if more than 200 concurrent requests occurs?

Sorry for too many questions javascript: x()
Smile

Thanks
Nikhil
Thanks Jeanne !

I thought on your suggestion.

Actually, I need to maintain the client's identity/state, as service need to send a PDF back to respective client. I guess that won't be possible the stateless bean, Isn't it?
We have one service which takes xml as input and returns pdf as output.
we want to throttle the requests to this service and queue up the subsequent request(In short we'll limit number of concurrent requests).

What can be the best approach for this solution? we are using websphere 6.ov application server.

we are thinking to use JMS with Websphere's default messaging service Queues (we don't want to use MQ)but challenge is to send the returned PDF to the respective requests. (To send response like we do in synchronous communication).

can some expert give any better suggestion/solution?

Thanks