Initial Context response times

Hi,
What is the generally accepted timings to obtain an intial context first
time from a client app to a remote EJB Server. My timings have shown that
even on my development machine with a local Weblogic server its can take
easily take upto 5 or 6 seconds to obtain an initial context. Using an IP
Address to avoid resolving a domain name makes little difference.
Thanks,
Pete.
KB Group Ltd
http://www.kbgroup.co.nz

See:
news://www4.weblogic.com/<[email protected]>
Cheers
Mark G.
Toby Allsopp wrote:
I was just looking at this last week. What we see is that the time taken to
obtain an InitialContext is pretty much constant at about 5-6 seconds as the
number of concurrent client connections increases, until you hit the number of
socket reader threads that you have configured. At that point, the time taken
increases by about 1 seconds for each additional client connection.
This is using WL 4.0.3 under IRIX. We have seen similar results with the
server running under NT, but the situation is much better when using the
native performance pack (i.e. the times stay at about 5 or 6 seconds even for
a lot of client connections).
We have attributed the slow-down as the number of clients increases to the
lack in the java.net API of anything resembling the select(2) function. We are
assuming that this functionality is provided by the native performance packs.
However, this doesn't explain why it takes 5 or 6 seconds to get one.
Toby Allsopp.
Jerry Taylor wrote:
We experience waits of 20 -30 seconds quite regularly.....
Pete Bent <[email protected]> wrote in message
news:7um2en$3qf$[email protected]..
Hi,
What is the generally accepted timings to obtain an intial context first
time from a client app to a remote EJB Server. My timings have shown that
even on my development machine with a local Weblogic server its can take
easily take upto 5 or 6 seconds to obtain an initial context. Using an IP
Address to avoid resolving a domain name makes little difference.
Thanks,
Pete.
KB Group Ltd
http://www.kbgroup.co.nz
Toby Allsopp
Research & Development
Peace Software International Ltd
Ph +64-9-3730400--
=====================================================
Reply to the newsgroup. Don't reply to this mail
alias. This is used only for answering posts on
WebLogic Newsgroups.
=====================================================

Similar Messages

CRM_DNO_MONITOR field: initial response time

Hi,
In CRM_DNO_MONITOR we were able to see all the data except 'Initial Response time' of Service desk message.
Kindly let us know, how to configure so that 'Initial Response time' should be displayed in CRM_DNO_MONITOR.
Thank you!

Hello Jerome,
understand better... sorry. Well unfortunately this value is not available in report CRM_DNO_SERVICE_MONITOR cause when you take a look to the structure used for the display table no field was created for that.
If that's something YOU NEED to implemement: here is the procedure
- do a structure append of CRMT_DNO_SERVICE_MONITOR to add field Initial Response Time - ZINITRESPTIME
- Then Use Badi CRM_DNO_MONITOR to fill the column Initial Response Time for CRM_DNO_MONITOR Transaction
In this Badi you can use Class: CL_DSMOP_REP_CRM, method: get_first_react_time as done by SOLAR_EVAL.
You should put a breakpoint in CL_DSMOP_REP_CRM->PREPARE_SIMPLE_OUTPUTLIST to see how standard handled that. That will definitely help u or the developer you might need
Hope that helps,
Regards,
Khalil

Caching initial contexts

I have read the posts about caching initial context lookups and have
implemented the solution and seen some benefits.
I am dealing with a third party application that I cannot change.
When I put my InitialContextFactory in the architecture I also logged
how many getInitialContext() calls were being made - I was absolutely
shocked - often 4+ per user transaction. I suspect that the code gets
one, does a call and dereferences all over the place.
90% of InitialContexts had the same environment passed to the getIC()
call so it struck me that what I should do is create a pool of IC, and
in my factory just serve one from the pool.
So, the question is, what is the best way of detecting when the IC has
been dereferenced so I know I can serve it again from my pool?
I presume this is a generic pool problem when you can't guarantee that
your client's will be good citizens and call a close() method or
similar.
I've posted here as it is performance related; also, is there any
reason why what I am doing is not a good idea?
Can the client do something with the IC which means it is not suitable
for use by another client? If so, can I detect this so I may discard?
As always, many thanks in advance.
Presuming I can get it to work I will post the code so that we can all
share ;-)
Cheers
Ed

Why don't you instrument your factory then to give out your own
implementation of InitialContext that will in fact only wrap a "loaner"
InitialContext every time a method is invoked on it and before returning
the value to the caller will put the real InitialContext back to the
pool to be reused by another one.
Then your clients can do whatever they want with those ICs and still
would not cause so big performance hits.
It's just an idea that just came to mind and I haven't tested it so it
might have flaws but it looks viable.
--dejan
Ed Barrett wrote:
The application is a third-party product that cannot be changed.
By introducing the factory you gave below (thanks!) we put the application
back under the load test and saw minimal improvements (like 1% response
time).
I then instrumented the factory with a system.out on finalize and noticed
that a factory instance is created for each call to getInitialContext() - is
this the way that WLS/J2EE works? I would have hoped that factories were
shared or something. What we did see is that for one user request a number
(sometimes 5!) ICs were being created ;-( Obviously the lookup cache is a
class instance and shared across the lot.
So then I started to think about pre-creating ICs and haveing a pool for the
default ones (environment specifies URL and no security details or the
like). Trouble is how to implement such when you cannot change the client
code to call a factory return method (such as returnToPool()).
Any ideas would be appreciated
"Dimitri I. Rakitine" <[email protected]> wrote in message
news:[email protected]...
I've ran into this problem while porting 5.1 application (JNDI lookups
were
super-cheap) to 6.1 (where they are not so cheap due to
serialization/deserialization)
and did this test to see if this indeed was the problem. As you saw I
didn't bother to
cache InitialContext's - I just cached JNDI lookups and that resulted in
very significant
performance improvements.
Which application are you testing it with?
Graham <[email protected]> wrote:
Dimitri,
We did this but did not see that much improvement over the default way -
we
are using 6.1 sp2.
We put some messages in our factory and found that the client code often
created over 4 ICs for one user click - aaggghhhh!! As I say we cannot
change their code but if we could take the time to create an IC away
from
the online response we feel we would save some time.
We also observed a new instance of the IC factory being created every
time a
new IC was created - is this what you would expect?
I think this is what NamingManager.getInitialContext() is supposed to do.
Cheers
Ed
"Dimitri I. Rakitine" <[email protected]> wrote in message
news:[email protected]...
Caching InitialContext's will probably not quite solve the problem,
because lookup()'s are expensive (in 6.x), so, caching lookup results
will result in performance improvements.
If you cannot change the 3'rd party code and all it does is:
... DataSource ds = (DataSource)new InitialContext().lookup(".....");
or similar, you can add caching by implementing your own InitialContext
factory,
for example: (extremely simplistic)
Startup class :
System.setProperty("java.naming.factory.initial",
"myjndi.InitialContextFactory");
where
myjndi.InitialContextFactory is :
public class InitialContextFactory implements
javax.naming.spi.InitialContextFactory {
public Context getInitialContext(Hashtable env) throws
NamingException
Context ctx = new
weblogic.jndi.WLInitialContextFactory().getInitialContext(env);
return
(Context)Proxy.newProxyInstance(ctx.getClass().getClassLoader(),
new Class[]
{ Context.class },
new
ContextHandler(ctx));
and myjndi.ContextHandler is:
public class ContextHandler implements InvocationHandler {
Context ctx;
static Hashtable cache = new Hashtable();
public ContextHandler(Context ctx) {
this.ctx = ctx;
public Object invoke(Object proxy, Method method, Object[] args)
throws Throwable {
try {
Object retVal;
if("lookup".equals(method.getName()) && args[0] instanceof
String) {
retVal = cache.get(args[0]);
if(retVal == null) {
retVal = method.invoke(ctx, args);
cache.put(args[0], retVal);
} else {
retVal = method.invoke(ctx, args);
return retVal;
} catch(InvocationTargetException oops) {
throw oops.getTargetException();
Ed <[email protected]> wrote:
Adarsh,
We agree it is a brilliant idea - now just to work out how to do it.
As you cannot always guarantee to be able to change the client code
you cannot use normal pooling techniques:
getObjectFromPool()
// do work
returnObjectToPool()
So, the client code needs an InitialContext. We can put in our own
Factory and intercept the getInitialContext() calls. This method
must
return class javax.naming.Context - therefore the only way I can see
to spot when the class is dereferenced is to extend the class and add
a finalize() method that notifies the factory.
The trouble I believe is that the class cannot be "rescued" in the
finalize() method (i.e. "I'm dying - take me back" ;-). If it simply
told the factory to add another one to its pool this would mean that
the new IC create "hit" would be in garbage collection (i.e. the
users
will pay somewhere along the line) - is this correct?
Anyone any ideas on a solution? I have discovered out code create
HUNDREDS of contexts in an hour and discards them very quickly. Be
nice to be able to cache them!
Cheers
Ed
"Adarsh Dattani" <[email protected]> wrote in message
news:<[email protected]>...
Ed,
This a brilliant idea. We are planning something similar too. We
first
want to create a pool of LDAP connections as apps make extensive
calls
to
LDAP. Did you check-out the object pooling api at Jakarta Commons.
It
deserves a close look.
http://jakarta.apache.org/commons/pool/index.html
Thanks,
Adarsh
"Ed" <[email protected]> wrote in message
news:[email protected]...
I have read the posts about caching initial context lookups and
have
implemented the solution and seen some benefits.
I am dealing with a third party application that I cannot change.
When I put my InitialContextFactory in the architecture I also
logged
how many getInitialContext() calls were being made - I was
absolutely
shocked - often 4+ per user transaction. I suspect that the code
gets
one, does a call and dereferences all over the place.
90% of InitialContexts had the same environment passed to the
getIC()
call so it struck me that what I should do is create a pool of IC,
and
in my factory just serve one from the pool.
So, the question is, what is the best way of detecting when the IC
has
been dereferenced so I know I can serve it again from my pool?
I presume this is a generic pool problem when you can't guarantee
that
your client's will be good citizens and call a close() method or
similar.
I've posted here as it is performance related; also, is there any
reason why what I am doing is not a good idea?
Can the client do something with the IC which means it is not
suitable
for use by another client? If so, can I detect this so I may
discard?
As always, many thanks in advance.
Presuming I can get it to work I will post the code so that we can
all
share ;-)
Cheers
Ed
Dimitri
Dimitri

Response time increase in OSB

Dear all,
While performing the Load test, during initial 2 - 3 hrs performance is very good. after 2 -3 hrs response time increasing and there by throughput going down 4 times.
when i check in GC Log, i found all OC's. generally i used to find many YC's and very less OC's. but this time its deferent. not sure why this behaviour.
Below is snap shot of my gc.log.
Following are my startManagedweblogic java options.
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverbose:memory -Xmx:6144m -Xms:6144m -Xns:3072m -Xverbosetimestamp -Xgcprio:pausetime -Xverboselog:/usr/home/WEBADM/blq2gsbl/BLQRYSBDM/bin/gc.log -Xverbose:gcreport -XlargePages -XXgcThreads:8 -XXtlasize:min=2k,preferred=16k -XXnoSystemGC"
please note that i have enough memory to increase till 12 gb also. i found better performance with 6g so i kept it as 6.
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
[memory ][Mon Aug 12 12:34:11 2013][16261] Running with 32 bit heap and compressed references supporting 32GB heap.
[memory ][Mon Aug 12 12:34:11 2013][16261] Using 256MB pages for Java heap.
[memory ][Mon Aug 12 12:34:12 2013][16261] GC mode: Garbage collection optimized for short pausetimes, strategy: Generational Concurrent Mark & Sweep.
[memory ][Mon Aug 12 12:34:12 2013][16261] Heap size: 6291456KB, maximal heap size: 6291456KB, nursery size: 3145728KB.
[memory ][Mon Aug 12 12:34:12 2013][16261] <start>-<end>: <type> <before>KB-><after>KB (<heap>KB), <time> ms, sum of pauses <pause> ms.
[memory ][Mon Aug 12 12:34:12 2013][16261] <start> - start time of collection (seconds since jvm start).
[memory ][Mon Aug 12 12:34:12 2013][16261] <type>   - OC (old collection) or YC (young collection).
[memory ][Mon Aug 12 12:34:12 2013][16261] <end>    - end time of collection (seconds since jvm start).
[memory ][Mon Aug 12 12:34:12 2013][16261] <before> - memory used by objects before collection (KB).
[memory ][Mon Aug 12 12:34:12 2013][16261] <after> - memory used by objects after collection (KB).
[memory ][Mon Aug 12 12:34:12 2013][16261] <heap>   - size of heap after collection (KB).
[memory ][Mon Aug 12 12:34:12 2013][16261] <time>   - total time of collection (milliseconds).
[memory ][Mon Aug 12 12:34:12 2013][16261] <pause> - total sum of pauses during collection (milliseconds).
[memory ][Mon Aug 12 12:34:12 2013][16261]            Run with -Xverbose:gcpause to see individual phases.
[memory ][Mon Aug 12 12:49:59 2013][16261] [YC#1] 947.689-948.011: YC 3426740KB->1274833KB (6291456KB), 0.323 s, sum of pauses 322.080 ms, longest pause 322.080 ms.
[memory ][Mon Aug 12 12:50:18 2013][16261] [YC#2] 966.433-966.521: YC 3700241KB->1381022KB (6291456KB), 0.088 s, sum of pauses 87.355 ms, longest pause 87.355 ms.
[memory ][Mon Aug 12 12:50:33 2013][16261] [YC#3] 981.691-981.734: YC 3806640KB->1448962KB (6291456KB), 0.043 s, sum of pauses 42.316 ms, longest pause 42.316 ms.
[memory ][Mon Aug 12 12:50:48 2013][16261] [YC#4] 996.195-996.232: YC 3876151KB->1518729KB (6291456KB), 0.037 s, sum of pauses 36.360 ms, longest pause 36.360 ms.
[memory ][Mon Aug 12 12:51:03 2013][16261] [YC#5] 1011.797-1011.833: YC 3950327KB->1592393KB (6291456KB), 0.036 s, sum of pauses 35.004 ms, longest pause 35.004 ms.
[memory ][Mon Aug 12 12:51:19 2013][16261] [YC#6] 1027.447-1027.489: YC 4022805KB->1665479KB (6291456KB), 0.041 s, sum of pauses 40.711 ms, longest pause 40.711 ms.
[memory ][Mon Aug 12 12:51:34 2013][16261] [YC#7] 1043.090-1043.127: YC 4097355KB->1739629KB (6291456KB), 0.037 s, sum of pauses 35.984 ms, longest pause 35.984 ms.
[memory ][Mon Aug 12 12:51:50 2013][16261] [YC#8] 1058.656-1058.704: YC 4171396KB->1814054KB (6291456KB), 0.047 s, sum of pauses 46.695 ms, longest pause 46.695 ms.
[memory ][Mon Aug 12 12:52:00 2013][16261] [YC#9] 1068.490-1068.533: YC 4245475KB->1887941KB (6291456KB), 0.043 s, sum of pauses 42.002 ms, longest pause 42.002 ms.
[memory ][Mon Aug 12 12:52:09 2013][16261] [YC#10] 1077.381-1077.421: YC 4318167KB->1961481KB (6291456KB), 0.041 s, sum of pauses 39.592 ms, longest pause 39.592 ms.
[memory ][Mon Aug 12 12:52:19 2013][16261] [YC#11] 1087.366-1087.406: YC 4394185KB->2036571KB (6291456KB), 0.039 s, sum of pauses 38.757 ms
87.597 ms, longest pause 50.632 ms.
[memory ][Tue Aug 13 18:21:28 2013][16261] [OC#9822] 107234.509-107237.018: OC 893216KB->845338KB (6291456KB), 2.509 s, sum of pauses 536.399 ms, longest pause 504.274 ms.
[memory ][Tue Aug 13 18:21:31 2013][16261] [OC#9823] 107237.419-107239.864: OC 1116022KB->860547KB (6291456KB), 2.445 s, sum of pauses 414.935 ms, longest pause 354.974 ms.
[memory ][Tue Aug 13 18:21:34 2013][16261] [OC#9824] 107239.864-107242.447: OC 949080KB->878533KB (6291456KB), 2.583 s, sum of pauses 541.277 ms, longest pause 504.113 ms.
[memory ][Tue Aug 13 18:21:37 2013][16261] [OC#9825] 107242.447-107245.494: OC 953535KB->860560KB (6291456KB), 3.047 s, sum of pauses 633.955 ms, longest pause 504.806 ms.
[memory ][Tue Aug 13 18:21:39 2013][16261] [OC#9826] 107245.494-107247.971: OC 1054631KB->869654KB (6291456KB), 2.478 s, sum of pauses 541.422 ms, longest pause 504.193 ms.
[memory ][Tue Aug 13 18:21:42 2013][16261] [OC#9827] 107247.972-107250.441: OC 921210KB->857407KB (6291456KB), 2.469 s, sum of pauses 483.940 ms, longest pause 440.031 ms.
[memory ][Tue Aug 13 18:21:45 2013][16261] [OC#9828] 107250.792-107253.213: OC 1132559KB->875285KB (6291456KB), 2.422 s, sum of pauses 524.526 ms, longest pause 487.132 ms.
[memory ][Tue Aug 13 18:21:47 2013][16261] [OC#9829] 107253.213-107255.610: OC 899114KB->855957KB (6291456KB), 2.397 s, sum of pauses 481.233 ms, longest pause 451.024 ms.
[memory ][Tue Aug 13 18:21:50 2013][16261] [OC#9830] 107256.011-107258.297: OC 1127479KB->868126KB (6291456KB), 2.286 s, sum of pauses 373.648 ms, longest pause 336.646 ms.
[memory ][Tue Aug 13 18:21:52 2013][16261] [OC#9831] 107258.298-107260.847: OC 912365KB->856462KB (6291456KB), 2.550 s, sum of pauses 526.103 ms, longest pause 492.768 ms.
[memory ][Tue Aug 13 18:21:55 2013][16261] [OC#9832] 107261.098-107263.611: OC 1044068KB->863005KB (6291456KB), 2.513 s, sum of pauses 541.427 ms, longest pause 504.196 ms.
[memory ][Tue Aug 13 18:21:57 2013][16261] [OC#9833] 107263.611-107265.846: OC 902510KB->847460KB (6291456KB), 2.235 s, sum of pauses 213.535 ms, longest pause 179.799 ms.
[memory ][Tue Aug 13 18:22:00 2013][16261] [OC#9834] 107265.946-107268.356: OC 974573KB->863254KB (6291456KB), 2.409 s, sum of pauses 441.951 ms, longest pause 405.552 ms.
[memory ][Tue Aug 13 18:22:02 2013][16261] [OC#9835] 107268.556-107271.134: OC 1013772KB->856892KB (6291456KB), 2.578 s, sum of pauses 542.932 ms, longest pause 503.782 ms.
[memory ][Tue Aug 13 18:22:05 2013][16261] [OC#9836] 107271.134-107273.302: OC 946088KB->860358KB (6291456KB), 2.168 s, sum of pauses 220.883 ms, longest pause 182.948 ms.
[memory ][Tue Aug 13 18:22:07 2013][16261] [OC#9837] 107273.552-107275.500: OC 1010670KB->854399KB (6291456KB), 1.948 s, sum of pauses 120.783 ms, longest pause 56.691 ms.
[memory ][Tue Aug 13 18:22:09 2013][16261] [OC#9838] 107275.501-107277.801: OC 906839KB->850508KB (6291456KB), 2.301 s, sum of pauses 399.919 ms, longest pause 367.834 ms.
[memory ][Tue Aug 13 18:22:11 2013][16261] [OC#9839] 107278.052-107280.071: OC 1045319KB->862319KB (6291456KB), 2.019 s, sum of pauses 144.317 ms, longest pause 75.239 ms.
[memory ][Tue Aug 13 18:22:14 2013][16261] [OC#9840] 107280.071-107282.578: OC 887997KB->849438KB (6291456KB), 2.507 s, sum of pauses 537.495 ms, longest pause 504.761 ms.
[memory ][Tue Aug 13 18:22:16 2013][16261] [OC#9841] 107282.879-107284.888: OC 1061809KB->860007KB (6291456KB), 2.009 s, sum of pauses 137.893 ms, longest pause 63.667 ms.
[memory ][Tue Aug 13 18:22:19 2013][16261] [OC#9842] 107284.888-107287.367: OC 908775KB->852632KB (6291456KB), 2.479 s, sum of pauses 541.465 ms, longest pause 504.889 ms.
[memory ][Tue Aug 13 18:22:21 2013][16261] [OC#9843] 107287.517-107289.881: OC 1005267KB->849986KB (6291456KB), 2.364 s, sum of pauses 160.999 ms, longest pause 86.633 ms.
[memory ][Tue Aug 13 18:22:24 2013][16261] [OC#9844] 107289.881-107292.353: OC 907985KB->848410KB (6291456KB), 2.472 s, sum of pauses 540.357 ms, longest pause 504.985 ms.
[memory ][Tue Aug 13 18:22:26 2013][16261] [OC#9845] 107292.353-107294.314: OC 916160KB->850798KB (6291456KB), 1.961 s, sum of pauses 104.840 ms, longest pause 66.068 ms.
[memory ][Tue Aug 13 18:22:28 2013][16261] [OC#9846] 107294.364-107296.780: OC 923551KB->849834KB (6291456KB), 2.416 s, sum of pauses 440.677 ms, longest pause 403.477 ms.
[memory ][Tue Aug 13 18:22:30 2013][16261] [OC#9847] 107296.931-107299.111: OC 997464KB->858904KB (6291456KB), 2.180 s, sum of pauses 246.058 ms, longest pause 206.937 ms.
[memory ][Tue Aug 13 18:22:33 2013][16261] [OC#9848] 107299.111-107301.563: OC 903415KB->851026KB (6291456KB), 2.452 s, sum of pauses 540.845 ms, longest pause 504.318 ms.
[memory ][Tue Aug 13 18:22:35 2013][16261] [OC#9849] 107301.814-107303.861: OC 1013878KB->857614KB (6291456KB), 2.048 s, sum of pauses 94.386 ms, longest pause 53.197 ms.
[memory ][Tue Aug 13 18:22:38 2013][16261] [OC#9850] 107303.861-107306.212: OC 887706KB->860005KB (6291456KB), 2.350 s, sum of pauses 346.029 ms, longest pause 311.092 ms.
[memory ][Tue Aug 13 18:22:40 2013][16261] [OC#9851] 107306.262-107308.853: OC 937699KB->860853KB (6291456KB), 2.591 s, sum of pauses 557.007 ms, longest pause 501.625 ms.
[memory ][Tue Aug 13 18:22:43 2013][16261] [OC#9852] 107308.853-107311.426: OC 951313KB->870294KB (6291456KB), 2.573 s, sum of pauses 541.352 ms, longest pause 504.381 ms.
[memory ][Tue Aug 13 18:22:45 2013][16261] [OC#9853] 107311.426-107314.144: OC 909609KB->852710KB (6291456KB), 2.718 s, sum of pauses 583.129 ms, longest pause 504.576 ms.
[memory ][Tue Aug 13 18:22:48 2013][16261] [OC#9854] 107314.144-107316.628: OC 969124KB->858298KB (6291456KB), 2.484 s, sum of pauses 542.151 ms, longest pause 504.257 ms.
[memory ][Tue Aug 13 18:22:50 2013][16261] [OC#9855] 107316.628-107319.114: OC 915682KB->849121KB (6291456KB), 2.486 s, sum of pauses 495.272 ms, longest pause 447.599 ms.
[memory ][Tue Aug 13 18:22:53 2013][16261] [OC#9856] 107319.314-107321.936: OC 1006620KB->861443KB (6291456KB), 2.621 s, sum of pauses 544.915 ms, longest pause 504.410 ms.
[memory ][Tue Aug 13 18:22:56 2013][16261] [OC#9857] 107321.936-107324.410: OC 922270KB->852766KB (6291456KB), 2.474 s, sum of pauses 541.767 ms, longest pause 504.142 ms.
[memory ][Tue Aug 13 18:22:58 2013][16261] [OC#9858] 107324.610-107327.023: OC 1039488KB->861496KB (6291456KB), 2.413 s, sum of pauses 542.856 ms, longest pause 504.187 ms.
[memory ][Tue Aug 13 18:23:01 2013][16261] [OC#9859] 107327.023-107329.315: OC 918829KB->843657KB (6291456KB), 2.292 s, sum of pauses 321.525 ms, longest pause 286.826 ms.
[memory ][Tue Aug 13 18:23:03 2013][16261] [OC#9860] 107329.616-107332.141: OC 1069773KB->863389KB (6291456KB), 2.525 s, sum of pauses 548.231 ms, longest pause 504.177 ms.
[memory ][Tue Aug 13 18:23:06 2013][16261] [OC#9861] 107332.141-107334.343: OC 915522KB->853889KB (6291456KB), 2.202 s, sum of pauses 189.135 ms, longest pause 153.663 ms.
[memory ][Tue Aug 13 18:23:08 2013][16261] [OC#9862] 107334.644-107337.056: OC 1032066KB->868736KB (6291456KB), 2.412 s, sum of pauses 545.438 ms, longest pause 504.254 ms.
[memory ][Tue Aug 13 18:23:11 2013][16261] [OC#9863] 107337.056-107339.296: OC 915783KB->864080KB (6291456KB), 2.240 s, sum of pauses 298.272 ms, longest pause 263.347 ms.
[memory ][Tue Aug 13 18:23:13 2013][16261] [OC#9864] 107339.597-107341.923: OC 1011429KB->878520KB (6291456KB), 2.326 s, sum of pauses 456.568 ms, longest pause 419.025 ms.
[memory ][Tue Aug 13 18:23:15 2013][16261] [OC#9865] 107341.923-107343.934: OC 919359KB->840367KB (6291456KB), 2.011 s, sum of pauses 125.250 ms, longest pause 57.223 ms.
[memory ][Tue Aug 13 18:23:18 2013][16261] [OC#9866] 107344.185-107346.733: OC 1012840KB->874965KB (6291456KB), 2.548 s, sum of pauses 540.636 ms, longest pause 504.970 ms.
[memory ][Tue Aug 13 18:23:20 2013][16261] [OC#9867] 107346.750-107348.793: OC 933751KB->854858KB (6291456KB), 2.043 s, sum of pauses 156.099 ms, longest pause 82.344 ms.
[memory ][Tue Aug 13 18:23:23 2013][16261] [OC#9868] 107348.793-107351.335: OC 887450KB->867195KB (6291456KB), 2.542 s, sum of pauses 537.543 ms, longest pause 504.801 ms.
[memory ][Tue Aug 13 18:23:25 2013][16261] [OC#9869] 107351.486-107353.546: OC 996281KB->860628KB (6291456KB), 2.060 s, sum of pauses 160.157 ms, longest pause 73.442 ms.
[memory ][Tue Aug 13 18:23:27 2013][16261] [OC#9870] 107353.546-107356.073: OC 906961KB->872330KB (6291456KB), 2.527 s, sum of pauses 539.374 ms, longest pause 504.913 ms.
[memory ][Tue Aug 13 18:23:30 2013][16261] [OC#9871] 107356.273-107358.702: OC 996457KB->851473KB (6291456KB), 2.429 s, sum of pauses 166.761 ms, longest pause 86.493 ms.
[memory ][Tue Aug 13 18:23:33 2013][16261] [OC#9872] 107358.703-107361.265: OC 907359KB->863117KB (6291456KB), 2.562 s, sum of pauses 541.203 ms, longest pause 504.927 ms.
[memory ][Tue Aug 13 18:23:35 2013][16261] [OC#9873] 107361.265-107363.378: OC 912545KB->853583KB (6291456KB), 2.113 s, sum of pauses 112.867 ms, longest pause 69.906 ms.
[memory ][Tue Aug 13 18:23:37 2013][16261] [OC#9874] 107363.379-107365.933: OC 919557KB->864998KB (6291456KB), 2.554 s, sum of pauses 543.605 ms, longest pause 504.637 ms.
[memory ][Tue Aug 13 18:23:39 2013][16261] [OC#9875] 107365.983-107368.091: OC 958748KB->857127KB (6291456KB), 2.108 s, sum of pauses 252.535 ms, longest pause 215.897 ms.
[memory ][Tue Aug 13 18:23:42 2013][16261] [OC#9876] 107368.342-107370.827: OC 999403KB->865783KB (6291456KB), 2.485 s, sum of pauses 540.028 ms, longest pause 504.197 ms.
[memory ][Tue Aug 13 18:23:44 2013][16261] [OC#9877] 107370.827-107372.683: OC 923670KB->857704KB (6291456KB), 1.856 s, sum of pauses 87.595 ms, longest pause 52.619 ms.
[memory ][Tue Aug 13 18:23:47 2013][16261] [OC#9878] 107372.883-107375.283: OC 985737KB->859804KB (6291456KB), 2.399 s, sum of pauses 487.291 ms, longest pause 451.118 ms.
[memory ][Tue Aug 13 18:23:49 2013][16261] [OC#9879] 107375.283-107377.932: OC 915211KB->853184KB (6291456KB), 2.649 s, sum of pauses 555.557 ms, longest pause 504.480 ms.
[memory ][Tue Aug 13 18:23:52 2013][16261] [OC#9880] 107377.932-107380.212: OC 1009969KB->874361KB (6291456KB), 2.279 s, sum of pauses 375.384 ms, longest pause 335.326 ms.
[memory ][Tue Aug 13 18:23:54 2013][16261] [OC#9881] 107380.212-107382.461: OC 914805KB->855458KB (6291456KB), 2.249 s, sum of pauses 288.521 ms, longest pause 250.881 ms.
[memory ][Tue Aug 13 18:23:56 2013][16261] [OC#9882] 107382.562-107384.892: OC 966755KB->867614KB (6291456KB), 2.330 s, sum of pauses 500.018 ms, longest pause 463.414 ms.
[memory ][Tue Aug 13 18:23:59 2013][16261] [OC#9883] 107384.942-107387.565: OC 932206KB->853768KB (6291456KB), 2.622 s, sum of pauses 565.151 ms, longest pause 504.160 ms.
[memory ][Tue Aug 13 18:24:01 2013][16261] [OC#9884] 107387.565-107389.985: OC 958792KB->862315KB (6291456KB), 2.421 s, sum of pauses 461.570 ms, longest pause 420.545 ms.

You need to find out the error code you get in fault due to response timeout. (run a test using test console and you would get that)
In error handler of stage from where you are calling this business service, check whether status code in $fault is equal to the error code due to response timeout. If it is equal then replace content of $body with required error xml and use reply with success.
See section "37.6 Fault Variable" to know more about $fault -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/context.htm#i1051956
Regards,
Anuj

Speeding Initial Context

Our applet is taking about 2minutes to get the initial context. Does anybody have any ideas for reducing this response time considerably? Any help will be much appreciated.
Enviroment:
We're running weblogic5.1 on the Solaris 2.6 box using JDK1.2.2.

I have exactly the same problem. We are experiencing a
getInitialContext() call taking between 30 and 60 seconds. The DNS is
fine - pinging the server machine responds instantaneously. I have seen
this problem reported before but have never seen a fix posted.
Here's our code:
static public Context getInitialContext(String
userName, String password, String providerURL) throws Exception
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, providerURL);
if (userName != null)
h.put(Context.SECURITY_PRINCIPAL, userName);
if (password == null)
password = "";
h.put(Context.SECURITY_CREDENTIALS, password);
return(new InitialContext(h));
Can the WebLogic people get involved please?
Thanks,
Ken Condal
Chief Technology Officer
Dovetail Systems
[email protected]
-----Original Message-----
From:      Scott Anderson [mailto:[email protected]]
Sent:     Friday, September 22, 2000 2:22 PM
Posted To:     performance
Conversation:     Speeding Initial Context
Subject:     Re: Speeding Initial Context
That sounds like it might be a DNS time-out issue. Make sure the client
can actually find the server by name.
Regards,
-scott
Gunjan wrote:
>
Our applet is taking about 2minutes to get the initial context. Doesanybody have any ideas for reducing this response time considerably?
Any help will be much appreciated.
>
Enviroment:
We're running weblogic5.1 on the Solaris 2.6 box using JDK1.2.2.

Error in ArjunaMs Provider: Could not set up Initial Context

Hi,
I am trying to run the chatdemo example that comes with arjunams using http as the protocol and for that I have changed the file "chatdemo.properties" to this:
java.naming.factory.initial=com.arjuna.ams.client.naming.AMSInitialContextFactory
java.naming.provider.url=ams://server?web#http://localhost:8090/WebConnect/WebConnect
I have already tried running the tomcat server in port 8080 now I am trying it in 8090 and I have WebConnect.war deployed in webapps folder. When I run the chatdemo I get the following error:
Caught exception getting properties from file
javax.naming.CommunicationException: Cannot set up Initial Context : Timeout whe
n communicating with the server (ams.timeout=3000 [milliseconds]). [Root excepti
on is [TIMEOUT_EXCEPTION]com.arjuna.ams.internal.client.common.TransportExceptio
n: Timeout when communicating with the server (ams.timeout=3000 [milliseconds]).
at com.arjuna.ams.internal.client.core.AbstractInitialContext.<init>(Abs
tractInitialContext.java:171)
at com.arjuna.ams.internal.client.transport.server.InitialContext.<init>
(InitialContext.java:72)
at com.arjuna.ams.internal.client.transport.server.web.naming.InitialCon
text.<init>(InitialContext.java:40)
at com.arjuna.ams.internal.client.transport.server.web.naming.InitialCon
textFactory.getInitialContext(InitialContextFactory.java:41)
at com.arjuna.ams.client.naming.AMSInitialContextFactory.getInitialConte
xt(AMSInitialContextFactory.java:360)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.arjuna.ams.demos.chat.core.JMSChatInterface.<init>(JMSChatInterfa
ce.java:240)
at com.arjuna.ams.demos.chat.ui.text.TextClient.test(TextClient.java:163
at com.arjuna.ams.demos.chat.ui.text.TextClient.main(TextClient.java:67)
Caused by: [TIMEOUT_EXCEPTION]com.arjuna.ams.internal.client.common.TransportExc
eption: Timeout when communicating with the server (ams.timeout=3000 [millisecon
ds]).
at com.arjuna.ams.internal.client.common.MessageCarrierBuffer.get(Messag
eCarrierBuffer.java:67)
at com.arjuna.ams.internal.client.common.RPCMapper.sendRPC(RPCMapper.jav
a:102)
at com.arjuna.ams.internal.client.transport.server.TransportManager.init
(TransportManager.java:139)
at com.arjuna.ams.internal.client.transport.server.InitialContext.create
TransportLayer(InitialContext.java:102)
at com.arjuna.ams.internal.client.core.AbstractInitialContext.createComm
Chain(AbstractInitialContext.java:999)
at com.arjuna.ams.internal.client.core.AbstractInitialContext.<init>(Abs
tractInitialContext.java:165)
What can be the error? Please I need help urgently!!!
Thanks in advance!

Hi RESIDENT2,
First of all, please let me apologise for the delay in response time to your message! Unfortunately it seems as though we missed this one.
Can I suggest to you that the best place to get help with ArjunaMS is from:
http://www.arjuna.com/forum/
As far as your problem is concerned it appears as though you have performed the correct procedures to setup ArjunaMS, if your problem still exists can I ask you to post a complete description of the system as it stands.
NOTE: To check the WebConnect servlet is running you should be able to connect to http://localhost:8090/WebConnect, which should display a welcome page for the servlet. If this welcome screen cannot be seen then the servlet failed to deploy.
Once again, sorry for the delayed response!
Cheers,
Tom
Arjuna Technologies Limited

How to capture transaction response time in SQL

I need to capture Transaction response time (i.e. ping test) to calculated the peak hours and averaged
on a daily basis.
and
Page refresh time that is calculated no less than every 2 hours for peak hours and averaged on a daily basis.
Please assist
k

My best guess as to what you are looking for is something like the following (C#):
private int? Ping()
System.Data.SqlClient.SqlConnection objConnection;
System.Data.SqlClient.SqlCommand objCommand;
System.Data.SqlClient.SqlParameter objParameter;
System.Diagnostics.Stopwatch objStopWatch = new System.Diagnostics.Stopwatch();
DateTime objStartTime, objEndTime, objServerTime;
int intToServer, intFromServer;
int? intResult = null;
objConnection = new System.Data.SqlClient.SqlConnection("Data Source=myserver;Initial Catalog=master;Integrated Security=True;Connect Timeout=3;Network Library=dbmssocn;");
using (objConnection)
objConnection.Open();
using (objCommand = new System.Data.SqlClient.SqlCommand())
objCommand.Connection = objConnection;
objCommand.CommandType = CommandType.Text;
objCommand.CommandText = @"select @ServerTime = sysdatetime()";
objParameter = new System.Data.SqlClient.SqlParameter("@ServerTime", SqlDbType.DateTime2, 7);
objParameter.Direction = ParameterDirection.Output;
objCommand.Parameters.Add(objParameter);
objStopWatch.Start();
objStartTime = DateTime.Now;
objCommand.ExecuteNonQuery();
objEndTime = DateTime.Now;
objStopWatch.Stop();
objServerTime = DateTime.Parse(objCommand.Parameters["@ServerTime"].Value.ToString());
intToServer = objServerTime.Subtract(objStartTime).Milliseconds;
intFromServer = objEndTime.Subtract(objServerTime).Milliseconds;
intResult = (int?)objStopWatch.ElapsedMilliseconds;
System.Diagnostics.Debug.Print(string.Format("Milliseconds from client to server {0}, milliseconds from server back to client {1}, and milliseconds round trip {2}.", intToServer, intFromServer, intResult));
return intResult;
Now, while the round trip measurement is fairly accurate give or take 100ms, any measurement of latency to and from SQL Server is going to be subject to the accuracy of the time synchronization of the client and server. If the server's and client's
time isn't synchronized precisely then you will get odd results in the variables intToServer and intFromServer.
Since the round trip result of the test is measured entirely on the client that value isn't subject to the whims of client/server time synchronization.

How to check which RFCs causing issues in the system and RFC response times

Hi,
We have an issue with the RFC response times in CRM and need investigstion. We need to know which Which RFCs causing issues and how we can solve the problems.
Regards

Hi,
chek the below code
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_EXIST
EXPORTING
FILE = W_FILENAME
RECEIVING
RESULT = W_RESULT
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
WRONG_PARAMETER = 3
NOT_SUPPORTED_BY_GUI = 4
others = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-* MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF W_RESULT IS INITIAL.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_EXIST
EXPORTING
DIRECTORY = W_FILENAME
RECEIVING
RESULT = W_RESULT
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
WRONG_PARAMETER = 3
NOT_SUPPORTED_BY_GUI = 4
OTHERS = 5.
IF SY-SUBRC <> 0.
ENDIF.
ENDIF.
IF W_RESULT = 'X'.
RC = '1'.
ELSE.
RC = '0'.
ENDIF.
reward if helpful.
Regards,
nagaraj

Error in getting Initial Context

Hello,
I am facing the following exception while trying to get the Initial Context. Following
is the snippet of code that I use for getting the Context -
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");p.
put(Context.PROVIDER_URL, url);
if (user != null) {
p.put(Context.SECURITY_PRINCIPAL, user);
if (password == null)
password = "";
p.put(Context.SECURITY_CREDENTIALS, password);
return new InitialContext(p);
The following is the exception that I encounter -
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set
Am i missing anything. Thanks for your time.
See the attached file for the details of the exception
Thanks,
Ashutosh
[trace.txt]

Hi Tim,
If you are running within a browser, you will not have access to anything
outside the sandbox which includes making RMI calls. Try signing the applet.
You can find more information on signing applets on the sun java website.
Regards
Arjuna
"Tim" <[email protected]> wrote in message
news:3c5ab818$[email protected]..
>
I get the following eror when I try to get the Initial Context in anapplet:
>
java.lang.ExceptionInInitializerError: java.security.Acc
ess denied (java.util.PropertyPermission * read,write)
atjava.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
atjava.security.AccessController.checkPermission(AccessController.java:
399)
Does anyone have any idea what would cause this? The code works finerunning
from an application. From what I understand there might be a problem withmy
policy file. However, it seems to look ok. Any ideas?

Slow response time HTTP= XI= RFC

I have a HTTP call to XI BPM which makes a sync RFC call to another SAP system via SA bridge. The BPM is working fine. However, the time taken to process a transaction is about 6 seconds (not much data about 2 lines).
The party initiating HTTP call is not satisfied with this response time.
Their current system (C program to SAP via API/RFCs) take about a second to respond.
Heres how my response time is distributed based on the WF analysis of the steps
InfoLink_To_SAP_BPM urn:abc.com:InfoLink Workflow started            4s
Start Message: Receive XML from InfoLink
Initialize System Element
Mapping      Step completed        0s
Process control record read in XI
Send Message Synchronously Step completed    1s
Mapping      Step completed        0s
Send Message Synchronously    Step completed     0s
    Mapping       Step completed    0s
S/A Bridge: Response to Synchronous Request   1s
It seems like the first step takes 4 sec. Does it take this long for HTTP connect? Or is this to launch or initialize WF / BPM?
In SAP, the RFC look .0027 secs to complete.
Does anyone have any idea on how to improve my response time.
Thanks!

Hi,
In a BPM with sych-asych bridge we did observe a 3 -4 sec processing time, its just initialization time on the workflow.
when we approached SAP Workflow team, we were told that was the optimal time. Unless something has changed in the new SP packs!!
cheers,
naveen

Getting Initial context

Here is some debug output from a simple test I run against a WL6.1
Server. Notice the 35 secs. it takes to get Initial Context.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 35047 ms.
-- Succeeded looking up jndi name.
-- Execution time: 453 ms.
-- Succeeded casting Home interface.
-- Execution time: 94 ms.
Second time I run the test from the same machine I get this.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 1907 ms.
-- Succeeded looking up jndi name.
-- Execution time: 312 ms.
-- Succeeded casting Home interface.
-- Execution time: 31 ms.
The pattern is consistent. First attempt to get the Initial Context
from any of my client boxes will take about 30 secs more than any
consecutive attempts.
Here is the code for getting the Context:
long startTime = 0;
if (logging) {
     log("Initializing bean access.");
     startTime = System.currentTimeMillis();
try {
     //get naming context
     Context ctx = getInitialContext();
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded getting naming context.");
          log("Execution time: " + (endTime - startTime) + " ms.");
          startTime =endTime;
     //look up jndi name
     Object ref = ctx.lookup("DynamicPool");
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded looking up jndi name.");
          log("Execution time: " + (endTime - startTime) + " ms.");
          startTime =endTime;
     //cast to Home interface
     dynamicPoolHome = (DynamicPoolHome) PortableRemoteObject.narrow(ref,
DynamicPoolHome.class);
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded casting Home interface.");
          log("Execution time: " + (endTime - startTime) + " ms.");
catch(Exception e) {
     if (logging) {
          log("Failed initializing bean access.");
     e.printStackTrace();
Am I missing something here ?
Regards,
Klaus

My first guess would be a DNS problem.
Also, creating an InitialContext loads a fair amount of classes. If you're
loading them over the network, that could also account for the slow-down.
-- Rob
Klaus Preisler wrote:
Here is some debug output from a simple test I run against a WL6.1
Server. Notice the 35 secs. it takes to get Initial Context.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 35047 ms.
-- Succeeded looking up jndi name.
-- Execution time: 453 ms.
-- Succeeded casting Home interface.
-- Execution time: 94 ms.
Second time I run the test from the same machine I get this.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 1907 ms.
-- Succeeded looking up jndi name.
-- Execution time: 312 ms.
-- Succeeded casting Home interface.
-- Execution time: 31 ms.
The pattern is consistent. First attempt to get the Initial Context
from any of my client boxes will take about 30 secs more than any
consecutive attempts.
Here is the code for getting the Context:
long startTime = 0;
if (logging) {
log("Initializing bean access.");
startTime = System.currentTimeMillis();
try {
//get naming context
Context ctx = getInitialContext();
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded getting naming context.");
log("Execution time: " + (endTime - startTime) + " ms.");
startTime =endTime;
//look up jndi name
Object ref = ctx.lookup("DynamicPool");
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded looking up jndi name.");
log("Execution time: " + (endTime - startTime) + " ms.");
startTime =endTime;
//cast to Home interface
dynamicPoolHome = (DynamicPoolHome) PortableRemoteObject.narrow(ref,
DynamicPoolHome.class);
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded casting Home interface.");
log("Execution time: " + (endTime - startTime) + " ms.");
catch(Exception e) {
if (logging) {
log("Failed initializing bean access.");
e.printStackTrace();
Am I missing something here ?
Regards,
Klaus

Initial Context Security Issue

Hi, I wonder if someone can help me with this one??
The problem we are experiencing is that we have a remote client that connects
to 2 completely independent Weblogic 6.1 instances, and it appears that, under
certain circumstances, that the initial contexts actually become "confused", so
as to create a situation both initial contexts have been initialized successfully,
and after a while it appears that a connection to server B is attempted with the
principal and credential values of server A, obviously causing account lockouts
seeing as the user account does not exist on server B.
I have established through testing that this condition can be avoided by either
setting InitialContext.SECURITY_AUTHENTICATION = "none" and by not providing InitialContext.SECURITY_PRINCIPAL
and InitialContext.SECURITY_CREDENTIALS values for both client connections, or
by setting InitialContext.SECURITY_AUTHENTICATION = "simple", supplying valid
InitialContext.SECURITY_PRINCIPAL and InitialContext.SECURITY_CREDENTIALS values
for each server, and by reinitializing the InitialContext object before each and
every remote lookup.
We have decided to implement a InitialContext.SECURITY_AUTHENTICATION = "none"
policy, allowing us not to reinitialize the InitialContext objects every single
time. Obviously, this is not the preferred way!
I would appreciate any light on this, as this is causing us huge headaches, not
to mention the fact that one of the connections become completely unusable and
therefore denies any service whatsoever from one of the servers
Thanks in advance!

Hi,
This should probably have to be handled with Cisco directly or through the company that got you the license.
To my understanding there is a possibility that the you would first install one license key and the other license might be upgrade from the previous license to the next limit of the licensed feature.
I have had several occasions where I have been provided with the wrong license and have had to contact Cisco/supplier again to get the correct licenses for my device.
While I was posting this reply I checked the Licensing document for the ASA models. It would seem to me that there is no 25 Security Content License for the ASAs. The closes are 20 SC license and 50 SC license
Check this document:
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/intro_license.html#wp1230400
- Jouni

Why is Oracle Response time getting slow with time.

Hi,
     I have DB which was very fast initially with the response time for one of the query < 5 sec.
     I have been using the DB for the last 15 days. Now the same query is taking 10 minutes. In the DB there are lot of operations of additions and deletions been done on the table where the query is being made. The no. of records in the table is constant at around 3 million records from the first day.
     If I import the DB into a new setup then again the response time becomes very good in the new setup.
     What should be the problem of the DB getting slow with the time.
Thanks,
Tuhin

It all depends on several factors.
Are your tables,indexes have upto-date statistics?
I have DB which was very fast initially with the response time for one of the query < 5 sec. Initially there might be small amount of data later data might have increased,you dont have proper indexes.
It could be that your indexes got fragmented to due to heavey deletes? It might need reorg.
My suggestion would to look into your execution plan of the quries and see where your kernals are waiting.
As other suggested you, use explain plan, event 10046 and tkprof.
Jaffar

Virtual Machine - high disk response time

Hi Everyone,
Got something strange happening in our lab at the moment and was wondering if anyone had experienced the same thing (and maybe has a solution).
Our lab environment in a nutshell:
2x Windows 2012 Hyper hosts cluster connected to a "home-made" SAN based on Windows 2012 iSCSI target.
Each Hyper-V host has two 1Gbps network cards to connect to the SAN via the Microsoft iSCSI initiator, with MPIO in load-balancing mode (least queue depth).
The SAN (Windows 2012 server with iSCSI target) has 4x 1Gbps cards, teamed two by two, so presenting two IP addresses used by each hosts to connect to it (via MPIO).
The disk subsystem on the Windows 2012 SAN is an external HP storage works with 25x HP 500 SATA disks, connected to the server via an INTEL RAID controller with 2x 240GB SSD caching enabled for read/write.
The iSCSI network is on a dedicated HP switch, with flow-control and jumbo frame enabled (tested ok).
Now the problem:
I've built a few virtual machines on the two hyper-v nodes and I'm getting very bad disk response time as soon as there is an increase in the disk traffic.
When the virtual server is doing very little, I get a normal 6-8ms, but I soon as I increase the traffic (by for example copying a big file, or installing an application), this figure shoots up to 200ms, 300ms and more!
So I first thought that it was my disk subsystem (and the SAN server), but while the spikes are happening within the virtual machine, the disks on the SAN Server are sitting at about 10ms, with some spikes to about 20ms (which is pretty good and what I would
expect to see within the VM because of the SSD cache).
I then thought it could be the network, but during those times of activity, the network does not get saturated at all. Barely 150Mbps to 200Mbps per link.
I even tried to disable MPIO and run everything across one Ethernet link, but still the same result.
Am I missing something here? doing something wrong? or is this expected behaviour?
Thank you,
Stephane

Hi,
VR38DETT is right, if you want to use more ISCSI bandwidth or redundancy you must use the MPIO method, Multipath I/O (MPIO) is a feature that provides support for using multiple
data paths to a storage device. Multipathing increases the availability of storage resources by providing path failover from a server or cluster to a storage subsystem.
More information:
Multipath I/O Overview
http://technet.microsoft.com/en-us/library/cc725907.aspx
Support for Multipath I/O (MPIO)
http://technet.microsoft.com/en-us/library/cc770294.aspx
Hope this helps.
Alex Lv

Error getting initial context

Hi,
I've gotten the following exceptions reported to us by our production clients when trying to connect to our Weblogic 4.5.1 server (sp8).
CPClient with url: t3s://www.cpmarket.com:7002 Getting guest initial
context
[Root exception is java.io.IOException: Bootstrap unable to get a t3s
connection to
www.cpmarket.com/159.43.253.15]javax.naming.CommunicationException at
weblogic.jndi.toolkit.ExceptionTranslator.toNamingException(ExceptionTransla
tor.java:32) at
weblogic.jndi.WLInitialContextFactory.toNamingException(WLInitialContextFact
ory.java:513) at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java, Compiled Code) at
weblogic.jndi.Environment.getContext(Environment.java:128) at
weblogic.jndi.Environment.getInitialContext(Environment.java:111) at
com.xxxxxxx.CPClient.getGuestInitialContext(CPClient.jav
a:184) at
com.xxxxxxx.CPClient.<init>(CPClient.java:47)
Does anyone know where this could be coming from?
Thanks,
Gary Mui
[email protected]
[att1.html]

Hi Tim,
If you are running within a browser, you will not have access to anything
outside the sandbox which includes making RMI calls. Try signing the applet.
You can find more information on signing applets on the sun java website.
Regards
Arjuna
"Tim" <[email protected]> wrote in message
news:3c5ab818$[email protected]..
>
I get the following eror when I try to get the Initial Context in anapplet:
>
java.lang.ExceptionInInitializerError: java.security.Acc
ess denied (java.util.PropertyPermission * read,write)
atjava.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
atjava.security.AccessController.checkPermission(AccessController.java:
399)
Does anyone have any idea what would cause this? The code works finerunning
from an application. From what I understand there might be a problem withmy
policy file. However, it seems to look ok. Any ideas?

Initial Context response times

Similar Messages

Maybe you are looking for