Reasons for poor performance of Forms Application(s)....

Hi ,
Very often , i bump to questions like...:
Why is my Forms App slow...????
What can I do for it....????
e.t.c.
You can now take a look at Metalink Doc.Id: Note:242495.1...
Greetings....
Sim

Similar Messages

Reasons for poor performance

I am trying to find out why the performance of my queries is so slow and
found this interesting points:
1.) my SQL trace shows many "select count(*) from mytable ..." statements.
2.) query.compile() seems to be ignored, my SQL trace shows SQLExecDirect
calls for each "select"
I am using GenericDictionary and 2.3.1
Any hint appreciated.
Regards,
Bernhard

Bernhard Mandl <b.mandl@_NOSPAM_eunet.at> wrote:
Marc,
the additional SELECT statements were caused by multiple calls to
jdoPostLoad() for the same record on the database. With enough VM heap the
problem also disappears.
com.solarmetric.kodo.DefaultFetchBatchSize = 1 seems to be the best solution
for my large objects for now.
What is the best way if I want com.solarmetric.kodo.DefaultFetchBatchSize
different for different queries (1 for my large objects, 10 or more for
small objects) ? Must I use different PersistentManagerFactories or is it
possible to set it per Query ?This will be possible in a future release of Kodo JDO.
I do not agree that commands like this would necessarily exaust the VM's
memory:
for (Iterator i = pm.getExtent (Foo.class, true).iterator (); i.hasNext ();
i.next ());
I think it would be a good idea to allow the GC to release objects from the
cache only if one of the following conditions is true (at least as an
option):
- the object has been accessed at least once
- the next batch of rows is about to be fetched
In other words: hold a strong referece to all objects of the last pre-fetch
and change it into a weak reference when the next batch of rows is fetched
or when it is referenced by the app.
By following these rules you force the VM only to keep a maximum of
com.solarmetric.kodo.DefaultFetchBatchSize rows at a time in memory, but you
can be sure that fetch/drop/refetch does not happen.We're actually probably going to swap out our current weak reference map
with a LRU map that holds a fixed number of hard references and keeps
others in a weak map.
-Fred
Regards,
Bernhard
"Marc Prudhommeaux" <[email protected]> wrote in message
news:[email protected]...
Do you have an idea how to avoid the pre-load / getting dropped /
reload
problem? Maybe you should not allow objects to get dropped from the
cache
before certain criteria are met (accessed at least once)Well, the problem is that in that case, a simple command like:
for (Iterator i = pm.getExtent (Foo.class, true).iterator ();
i.hasNext (); i.next ());
would exaust the VM's memory, which is exactly with large result set
suport is supposed to avoid.
The best thing you can do for now is to either:
1. Set the com.solarmetric.kodo.DefaultFetchBatchSize to 1 so there is
no read-ahead, or
2. Figure out what is causing the additional SELECT statementes to be
issued, as I outlined in my last message.
In article <[email protected]>, Bernhard Mandl wrote:
Marc,
it's definitely a memory issue, when I run my program with
"java -Xms64M"
then it behaves as expected (as you describe).
Do you have an idea how to avoid the pre-load / getting dropped / reload
problem? Maybe you should not allow objects to get dropped from thecache
before certain criteria are met (accessed at least once)
Regards,
Bernhard
"Marc Prudhommeaux" <[email protected]> wrote in message
news:[email protected]...
Dear Bernhard,
What is your com.solarmetric.kodo.DefaultFetchBatchSize set to? This is
the size of the window of objects that Kodo will pre-load when fetching
a batch of objects. For example, if you have
com.solarmetric.kodo.DefaultFetchBatchSize=5, then when you iterate
through a list of 11 objects, Kodo will do the following when iterating
through the list:
Object 1: Load object 1-5
Object 2: already pre-loaded from Object 1
Object 3: already pre-loaded from Object 1
Object 4: already pre-loaded from Object 1
Object 5: already pre-loaded from Object 1
Object 6: Load object 6-10
Object 7: already pre-loaded from Object 6
Object 8: already pre-loaded from Object 6
Object 9: already pre-loaded from Object 6
Object 10: already pre-loaded from Object 6
Object 11: Load object 11
It is possible that your objects are getting pre-loaded and then
dropped
from the cache (due to memory limitations), which would cause these
re-selects to continue happening. Can you set the value to 1 or 0, and
see if the behavior persists?
Also, note that Kodo implements the lazy loading through a scrollable
ResultSet, so the additional SELECT statements you are seeing must be
due to loading inherited fields from another table, a blob field, or a
privately loaded Collection or Map being loaded upon instantiation of
the objects. You may be able to eliminate the default fetch group for
those fields, in which case the lazy loading will be much faster.
Can you post all the SQL that is being issued when you observe this
behavior so we can have a better idea what it happening?
In article <[email protected]>, Bernhard Mandl wrote:
Abe,
I tested with different values of
com.solarmetric.kodo.DefaultFetchThreshold and the results are:
1.) com.solarmetric.kodo.DefaultFetchThreshold = -1 causes
jdoPostLoad() to
be called exactly once (perfect for small result sets)
2.) any other value of com.solarmetric.kodo.DefaultFetchThreshold
causes
jdoPostLoad() to be called more than once.
This looks loke a bug in the implementation of lazy loading ?!
Regards,
Bernhard
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from yourcode
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from yourcode--
Fred Lucas
SolarMetric Inc.
202-595-2064 x1122
http://www.solarmetric.com

Probable reasons for poor youtube performance with Chrome browser

Using my new Lenovo Yoga 3 11 inch I have been experiencing horrendeously choppy youtube performance using the chrome browser, which was generating lots of heat due to the demands that chrome was asking of the CPU. The same youtube video plays perfectly smooth using Internet Explorer, and the laptop remains cool thanks to the much lower CPU load. So I was wondering why this was so. I wasted a lot of time following the stock answers of the internet - disabling plugins, 32 bit vs 64 bit chrome, updating drivers, even factory resetting and updating! But after routing through the internet guff, I did find some excellent information that fits my experiences, so I have little reason to doubt that the following statements, extracted from various parts of the internet, are true: Quote: "Google decided that Chrome should always use VP9 codec on PCs – even if there is no hardware acceleration available. This means that Chrome is doing CPU decide and that is pretty demanding in a 3.5w power limit for CPU, GPU, LLC, and FIVR. On IE, YouTube uses H.264/AVC and the hardware codec support kicks in for much more power efficiency." Quote: "When you watch YouTube using Chrome it uses VP8/VP9encoding by default. This type of encoding does not support hardware acceleration (which means it won’t use the on-board GPU – or video chip for you non-techies) so, your CPU has to do all of the work to decode and display the video." I thought people may find this information interesting, expecially if you are using a laptop with a light CPU such as Intel Core M. Chrome is my browser of choice, but this situation has forced me to use Internet Explorer for youtube.

I found that Chrome youtube runs much smoother and cooler on my Lenovo Yoga 3 11 inch after installing the h264ify Chrome extension. This allows Chrome to use the h264 codec for youtube instead of the CPU hammering VP9 codec.

Poor Performance with Fairpoint DSL

I started using Verizon DSL for my internet connection and had no problems. When Fairpoint Communications purchased Verizon (this is in Vermont), they took over the DSL (about May 2009). Since then, I have had very poor performance with all applications as soon as I start a browser. The performance problems occur regardless of the browser - I've tried Firefox (3.5.4), Safari (4.0.3) and Opera (10.0). I've been around and around with Fairpoint for 6 months with no resolution. I have not changed any software or hardware on my Mac during that time, except for updating the browsers and Apple updates to the OS, iTunes, etc. The performance problems continued right through these updates. I've run tests to check my internet speed and get times of 2.76Mbps (download) and 0.58Mbps (upload) which are within the specified limits for the DSL service. My Mac is a 2GHz PowerPC G5 runnning OSX 10.4.11. It has 512MB DDR SDRAM. I use a Westell Model 6100 modem for the DSL provided by Verizon.
Some of the specific problems I see are:
1. very long waits of more than a minute after a click on an item in the menu bar
2. very long waits of more than two minutes after a click on an item on a browser page
3. frequent pinwheels in response to a click on a menu item/browser page item
4. frequent pinwheels if I just move the mouse without a click
5. frequent messages for stopped/unresponsive scripts
6. videos (like YouTube) stop frequently for no reason; after several minutes, I'll get a little audio but no new video; eventually after several more minutes it will get going again (both video and audio)
7. response in non-browser applications is also very slow
8. sometimes will get no response at all to a mouse click
9. trying to run more than one browser at a time will bring the Mac to its knees
10. browser pages frequently take several minutes to load
These are just some of the problems I have.
These problems all go away and everything runs fine as soon as I stop the browser. If I start the browser, they immediately surface again. I've trying clearing the cache, etc with no improvements.
What I would like to do is find a way to determine if the problem is in my Mac or with the Fairpoint service. Since I had no problems with Verizon and have made no changes to my Mac, I really suspect the problem lies with Fairpoint. Can anyone help me out? Thanks.

1) Another thing that you could try it is deleting the preference files for networking. Mac OS will regenerate these files. You would then need to reconfigure your network settings.
The list of files comes from Mac OS X 10.4.
http://discussions.apple.com/message.jspa?messageID=8185915#8185915
http://discussions.apple.com/message.jspa?messageID=10718694#10718694
2) I think it is time to do a clean install of your system.
3) It's either the software or an intermittent hardware problem.
If money isn't an issue, I suggest an external harddrive for re-installing Mac OS.
You need an external Firewire drive to boot a PowerPC Mac computer.
I recommend you do a google search on any external harddrive you are looking at.
I bought a low cost external drive enclosure. When I started having trouble with it, I did a google search and found a lot of complaints about the drive enclosure. I ended up buying a new drive enclosure. On my second go around, I decided to buy a drive enclosure with a good history of working with Macs. The chip set seems to be the key ingredient. The Oxford line of chips seems to be good. I got the Oxford 911.
The latest the hard drive enclosures support the newer serial ata drives. The drive and closure that I list supports only older parallel ata.
Has everything interface:
FireWire 800/400 + USB2, + eSATA 'Quad Interface'
save a little money interface:
FireWire 400 + USB 2.0
This web page lists both external harddrive types. You may need to scroll to the right to see both.
http://eshop.macsales.com/shop/firewire/1394/USB/EliteAL/eSATAFW800_FW400USB
Here is an external hd enclosure.
http://eshop.macsales.com/item/Other%20World%20Computing/MEFW91UAL1K/
Here is what one contributor recommended:
http://discussions.apple.com/message.jspa?messageID=10452917#10452917
Folks in these Mac forums recommend LaCie, OWC or G-Tech.
Here is a list of recommended drives:
http://discussions.apple.com/thread.jspa?messageID=5564509#5564509
FireWire compared to USB. You will find that FireWire 400 is faster than USB 2.0 when used for a external harddrive connection.
http://en.wikipedia.org/wiki/UniversalSerial_Bus#USB_compared_toFireWire
http://www23.tomshardware.com/storageexternal.html

Connceting FMS over RTMPT resulted in poor perfomance of whole application

Hi,
We are connecting to FMS 3.5.7 behind the firewall through rtmpt and we have very poor performance over whole application even though we are not playing video in the application.My question is does the rtmpt use port 80 over http eventhough when we dont play video in the application.does it effect performance of whole application when connected through rtmpt?.
Can you pleae suggest me the solution to imporve my perfomance of the applciation when atleast not playing video in the applicaiton.Please suggest some changes..

Hi,
If you are accessing application from outside the firewall It cause problem in continuing the connection with FMS. you can see through wireshark, there will be reconnection very frequently. So, it is better to use rtmps for better performance.

Poor performance caused by using OCI driver?

[Sorry for the multipost]
I'm working on a medium-sized Apache / Tomcat / WLS 5.10 / Oracle
system hosted on some 4-processor Suns. The Apache / Tomcat tier
uses one box, the WebLogic tier uses another, and the Oracle tier
uses a third.
We've found that the performance, measured as the time it takes user
operations like loading a page that displays database data, gets
unacceptably bad at suspiciously low loads. When the system is in
this state, none of the machines appears to be pushed very hard.
There's no significant paging going on, the disk and network I/O
isn't out of line, and the CPU load just isn't high enough to
explain what's going on. Only the WebLogic tier shows a load over
10%. When the system is perceived as too slow by the users, the
CPU load on this tier is only 30-40%.
To try to find out what's going on, I did a series of thread dumps.
When the system is heavily loaded, I only see about three Oracle
statements currently being processed (runnable threads with call
stacks inside weblogic.db.oci.*). What I do see lots of is blocked
(and one runnable) threads inside
weblogic.rjvm.RJVMImpl.removePeerGoneListener or
weblogic.rjvm.RJVMImpl.addPeerGoneListener. These threads appear to
be attempting to obtain or release database connections.
I don't know why, but the site is configured to use the WebLogic OCI
driver for Oracle, instead of the Oracle-supplied thin driver. Is what I'm
seeing what Sun is describing in this paragraph
(excerpted from http://java.sun.com/docs/hotspot/PerformanceFAQ.html#24):
Oracle provides two types of database drivers: a type-2
driver, called the OCI (Oracle Call Interface) driver
that utilizes native code, and a type-4 pure Java driver
called the thin driver. In single processor environments,
the thin driver works somewhat better than the OCI driver
because of the JNI overhead associated with the OCI
driver. On multi-processor configuations, synchronization
points within Solaris used by the OCI driver become big
bottlenecks and prevent scaling. We recommend using the
thin driver in all cases.
-- Erik

Hi. I'll chip in here too. Yes, you are wasting JVM cycles having all those
wasted threads. Threads aren't free, inexhaustable sources of compute power
that some people assume (I'm not saying you're one). All these threads do
share a single OS process and CPU. The JVM has to check all these all the
time to see if they have something to do. I recommend configuring the
server to run about 15 or 20 execute-threads.
I see only one thread waiting on Oracle to return data, so I don't think this
is a JDBC issue necessarily. What I do see is lots of threads trying to operate
on a Vector, all being blocked, or at least serialized by the lock this thread has, below.
Is the server hung at this point, or just slow?
"ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
at java.util.Vector.removeElementAt(Vector.java:509)
at java.util.Vector.removeElement(Vector.java:598)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
at
com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Erik Horstkotte wrote:
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
You generally need a lot of data to find the performance problem in
a distributed system like this.Understood, but I was hoping that someone would recognize my description
as the "signature" of the locking problem with the OCI driver that Sun
describes.
It's very easy to switch to the Thin driver so you might as well
try it.I had hoped so, and in most cases, you're likely correct. Unfortunately,
the OCI driver is a touch more permissive than the thin driver. Some
errors (too many bind parameters) have crept in to our code that don't
cause problems for the OCI driver, but cause exceptions to be thrown by
the thin driver. In this particular case, I'm trying to solve a problem on
a production system - fixing the code there isn't an option (we are
switching to thin driver in our next release, so we are fixing these
problems).
If that doesn't help, I would suggest inserting some timing logic
in your code. In particular, I'd want to know the time a request
entered apache/tomcat, left apache/tomcat, entered WLS, left WLS
(to go to the database), returned from the database, left WLS, got
back to apache/tomcat, and finally left apache/tomcat to return the
response. With information like that, you should be able to narrow
down the problem a bit.In the next release, this is a good idea, and we'll probably do something
much like this. Unfortunately I can't make changes to the code on the
production site, so I have to rely on more passive methods of data
collection for the moment.
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
There can be other reasons for bad performance ranging from
serialized access to singletons to inefficient queries to
server mis-configuration. I have some doubts that oci driver
would affect performance at low loads.I don't see any evidence of serialization blocking, except for the
interesting locking issue that I mentioned in the original message (a
PeerGoneListener table maintained somewhere down inside WLS).
I'm certain that inefficient queries play a large role in our
performance problems.
Service mis-configuration could very well play a role here. Note for
example the large number of blocked idle execute threads in the thread
dump below. Clearly this instance has way too many execute threads. Not
knowing the internal architecture of WebLogic Server, nor the
implementation method Sun used for monitors in Solaris JVM 1.4.2, I don't
know how much of an impact an excess of execute threads has on
performance. Anyone?
Could you post a questionable thread dump here?See the bottom of this message. The dump has been "blinded" to remove some
customer-specific information.
Also, what's the load in terms of number of concurrent users
and requests per second?At peak load, there are about 60 users logged in, of whom only about 4-12
actually do much. The number of requests per second is very peaky, and
varies from about 1-10 per second. The complexity of requests also varies
wildly.
I've attached a thread dump from a point in time when the WebLogic Server
instance was taking about 30% of the CPU.
Any and all ideas are appreciated.
-- Erik
Full thread dump:
"HighPriority TimeEventGenerator" daemon prio=9 tid=0x4223ed0 nid=0xa7 waiting on monitor [0xcceff000..0xcceffc68]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:484)
"ListenThread" prio=5 tid=0x423f7a0 nid=0xa6 runnable [0xccbff000..0xccbffc68]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=5 tid=0x331ea0 nid=0xa2 waiting on monitor [0xccfff000..0xccfffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"NBExecuteThread-0" daemon prio=5 tid=0x3317b8 nid=0xa1 waiting on monitor [0xcd0ff000..0xcd0ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-149" daemon prio=5 tid=0x330228 nid=0xa0 runnable [0xcd1ff000..0xcd1ffc68]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-148" daemon prio=5 tid=0x32f740 nid=0x9f waiting on monitor [0xcd2ff000..0xcd2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-147" daemon prio=5 tid=0x32ec58 nid=0x9e waiting for monitor entry [0xcd3ff000..0xcd3ffc68]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-146" daemon prio=5 tid=0x32e170 nid=0x9d waiting for monitor entry [0xcd4ff000..0xcd4ffc68]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-145" daemon prio=5 tid=0x32ce80 nid=0x9c waiting on monitor [0xcd5ff000..0xcd5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-144" daemon prio=5 tid=0x32c398 nid=0x9b waiting for monitor entry [0xcd6ff000..0xcd6ffc68]
at java.util.Vector.removeElement(Vector.java:595)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.jts.internal.CoordinatorImpl.unregisterClientDeathNotification(CoordinatorImpl.java:101)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:347)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.ProfileSessionEJBEOImpl.getContactNumbers(ProfileSessionEJBEOImpl.java:5687)
at com.xxx.yyy.as.ProfileSessionEJBEOImpl_WLSkel.invoke(ProfileSessionEJBEOImpl_WLSkel.java:222)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-143" daemon prio=5 tid=0x32b8b0 nid=0x9a waiting on monitor [0xcd7ff000..0xcd7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-142" daemon prio=5 tid=0x32adc8 nid=0x99 waiting on monitor [0xcd8ff000..0xcd8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-141" daemon prio=5 tid=0x32a2e0 nid=0x98 waiting on monitor [0xcd9ff000..0xcd9ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-140" daemon prio=5 tid=0x3297f8 nid=0x97 waiting on monitor [0xcdaff000..0xcdaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-139" daemon prio=5 tid=0x328d10 nid=0x96 waiting for monitor entry [0xcdbff000..0xcdbffc68]
at java.util.Vector.addElement(Vector.java:573)
at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
at weblogic.time.server.ScheduledTrigger.setExecCon(ScheduledTrigger.java:46)
at weblogic.t3.srvr.T3ServerServices.getScheduledTrigger(T3ServerServices.java:177)
at weblogic.jts.internal.CoordinatorImpl.resetTimer(CoordinatorImpl.java:210)
at weblogic.jts.internal.CoordinatorImpl.<init>(CoordinatorImpl.java:83)
at weblogic.jts.internal.CoordinatorFactoryImpl.createCoordinator(CoordinatorFactoryImpl.java:95)
at weblogic.jts.internal.CoordinatorFactoryImpl_ServiceStub.createCoordinator(CoordinatorFactoryImpl_ServiceStub.java:69)
at weblogic.jts.internal.TxContext.getCoordinator(TxContext.java:139)
at weblogic.jts.internal.TxContext.begin(TxContext.java:93)
at weblogic.jts.internal.CurrentImpl.begin(CurrentImpl.java:48)
at weblogic.jts.internal.TransactionManagerImpl.begin(TransactionManagerImpl.java:56)
at weblogic.ejb.internal.EJBHomeImpl.setupTransaction(EJBHomeImpl.java:838)
at weblogic.ejb.internal.BaseEJBObject.setupTransaction(BaseEJBObject.java:281)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:471)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfigurationSiteSpecific(SecuritySessionEJBEOImpl.java:143)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:254)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-138" daemon prio=5 tid=0x328228 nid=0x95 waiting on monitor [0xcdcff000..0xcdcffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-137" daemon prio=5 tid=0x326d38 nid=0x94 waiting on monitor [0xcddff000..0xcddffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-136" daemon prio=5 tid=0x326250 nid=0x93 waiting on monitor [0xcdeff000..0xcdeffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-135" daemon prio=5 tid=0x325768 nid=0x92 waiting on monitor [0xcdfff000..0xcdfffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-134" daemon prio=5 tid=0x324c80 nid=0x91 waiting on monitor [0xce0ff000..0xce0ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-133" daemon prio=5 tid=0x324198 nid=0x90 waiting on monitor [0xce1ff000..0xce1ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-132" daemon prio=5 tid=0x3236b0 nid=0x8f waiting on monitor [0xce2ff000..0xce2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-131" daemon prio=5 tid=0x322bc8 nid=0x8e waiting on monitor [0xce3ff000..0xce3ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-130" daemon prio=5 tid=0x3220e0 nid=0x8d waiting on monitor [0xce4ff000..0xce4ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-129" daemon prio=5 tid=0x3215f8 nid=0x8c waiting on monitor [0xce5ff000..0xce5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-128" daemon prio=5 tid=0x320b10 nid=0x8b waiting on monitor [0xce6ff000..0xce6ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-127" daemon prio=5 tid=0x320028 nid=0x8a waiting on monitor [0xce7ff000..0xce7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-126" daemon prio=5 tid=0x31f540 nid=0x89 waiting on monitor [0xce8ff000..0xce8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-125" daemon prio=5 tid=0x31ea58 nid=0x88 waiting on monitor [0xce9ff000..0xce9ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-124" daemon prio=5 tid=0x31df70 nid=0x87 waiting on monitor [0xceaff000..0xceaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-123" daemon prio=5 tid=0x31d488 nid=0x86 waiting on monitor [0xcebff000..0xcebffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-122" daemon prio=5 tid=0x31bb90 nid=0x85 waiting on monitor [0xcecff000..0xcecffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-121" daemon prio=5 tid=0x31b0a8 nid=0x84 waiting on monitor [0xcedff000..0xcedffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-120" daemon prio=5 tid=0x31a5c0 nid=0x83 waiting for monitor entry [0xceeff000..0xceeffc68]
at java.util.Vector.addElement(Vector.java:573)
at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
at weblogic.jdbc20.rmi.internal.ConnectionImpl.<init>(ConnectionImpl.java:39)
at weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.java:65)
at weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiDataSource_ServiceStub.java:179)
at com.xxx.yyy.asutil.DataAccessManager.getConnection(DataAccessManager.java:113)
at com.xxx.yyy.as.MetricsSessionEJB.logEvent(MetricsSessionEJB.java:222)
at com.xxx.yyy.as.MetricsSessionEJBEOImpl.logEvent(MetricsSessionEJBEOImpl.java:324)
at com.xxx.yyy.as.MetricsSessionEJBEOImpl_WLSkel.invoke(MetricsSessionEJBEOImpl_WLSkel.java:242)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-119" daemon prio=5 tid=0x319ad8 nid=0x82 waiting on monitor [0xcefff000..0xcefffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-118" daemon prio=5 tid=0x318ff0 nid=0x81 runnable [0xcf0fe000..0xcf0ffc68]
at weblogic.db.oci.OciCursor.execAndFetch(Native Method)
at weblogic.db.oci.OciCursor.oci_execAndFetch(OciCursor.java:1890)
at weblogic.jdbcbase.oci.Statement.executeQuery(Statement.java:905)
at weblogic.jdbcbase.jts.Statement.executeQuery(Statement.java:58)
at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:46)
at weblogic.jdbc20.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:40)
at com.xxx.yyy.as.SecuritySessionEJB.getClientConfiguration(SecuritySessionEJB.java:1669)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfiguration(SecuritySessionEJBEOImpl.java:985)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:234)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.extensions.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:82)
at weblogic.rmi.internal.ServerRequest.sendOneWay(ServerRequest.java:73)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:77)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLStub.getClientConfiguration(SecuritySessionEJBEOImpl_WLStub.java:703)
at com.xxx.yyy.as.QuestionnaireSessionEJB.getQuestionnaireBatches(QuestionnaireSessionEJB.java:3479)
at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl.getQuestionnaireBatches(QuestionnaireSessionEJBEOImpl.java:631)
at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl_WLSkel.invoke(QuestionnaireSessionEJBEOImpl_WLSkel.java:237)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-117" daemon prio=5 tid=0x317f00 nid=0x80 waiting on monitor [0xcf1ff000..0xcf1ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-116" daemon prio=5 tid=0x317418 nid=0x7f waiting on monitor [0xcf2ff000..0xcf2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-115" daemon prio=5 tid=0x316930 nid=0x7e waiting on monitor [0xcf3ff000..0xcf3ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-114" daemon prio=5 tid=0x315e48 nid=0x7d waiting on monitor [0xcf4ff000..0xcf4ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-113" daemon prio=5 tid=0x314b58 nid=0x7c waiting on monitor [0xcf5ff000..0xcf5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-112" daemon prio=5 tid=0x314070 nid=0x7b waiting on monitor [0xcf6ff000..0xcf6ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-111" daemon prio=5 tid=0x313588 nid=0x7a waiting on monitor [0xcf7ff000..0xcf7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-110" daemon prio=5 tid=0x312aa0 nid=0x79 waiting on monitor [0xcf8ff000..0xcf8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
at java.util.Vector.removeElementAt(Vector.java:509)
at java.util.Vector.removeElement(Vector.java:598)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
at com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-108" daemon prio=5 tid=0x3114d0 nid=0x77 waiting on monitor [0xcfaff000..0xcfaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-107" daemon prio=5 tid=0x3109e8 nid=0x76 waiting on monitor [0xcfbff000..0xcfbffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-106" daemon prio=5 tid=0x30ff00 nid=0x75 waiting on monitor [0xcfcff000..0xcfcffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-105" daemon prio=5 tid=0x30f418 nid=0x74 waiting for monitor entry [0xcfdff000..0xcfdffc68]
at java.util.Vector.removeElement(Vector.java:595)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.jdbc20.rmi.internal.ConnectionImpl.close(ConnectionImpl.java:161)
at weblogic.jdbc20.rmi.SerialConnection.close(SerialConnection.java:162)
at com.xxx.yyy.asutil.Util

Essbase Perform backup, recovery, application migration and task automation

Hi Everyone,
I am very new (actually starting) to Essbase and trying to learn it from the documentation and examples available on the web. At my job, we just are planning to use Hyperion Essbase for planning and budgeting application. As I am the Oracle DBA so the installation and admin tasks are falling on my shoulders. Can you please refer me to the documentation, Note or References for Essbase Performing backups, recovery, application migration, task automation and optimization. Or a starting point from where I can explore the Essbase administration part only.
Thanks
-Samar-

Hi,
There is documentation available
Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide Release 11.1.1.3 =
http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_backup_recovery/launch.html
or pdf version - http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_backup_recovery.pdf
System 9.3.1
http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/hfm_backup.pdf
All documentation
http://www.oracle.com/technology/documentation/epm.html
Cheers
John
http://john-goodwin.blogspot.com/

How to port custom forms application from oracle apps to standard Forms

Hi All
I have developed a small custom forms application inside Oracle EBS.
I have used the TEMPLATE.fmb for all of my custom forms and followed all the standard metalink docs for building a custom forms application inside Oracle EBS 11i.
Now i kindly want to ask if there is any possibility on hos to port this custom application in a standard forms and reports services with oracle database, not using the Oracle EBS technology stack.
Is there any doc or step by step procedures?
thank you very much in advance
Soni

Now i kindly want to ask if there is any possibility on hos to port this custom application in a standard forms and reports services with oracle database, not using the Oracle EBS technology stack.If you want to register this custom form and integrate it with EBS then you need to do it from EBS.
Is there any doc or step by step procedures?https://forums.oracle.com/forums/search.jspa?threadID=&q=custom+AND+form+AND+register&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=custom+AND+application+AND+register&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Flash CS3 - No Form Applications?

I was looking at the new Flash CS3 course at Lynda.com and I
noticed that there was no Form Application in the templates
section. Is this true? If so I will have to retrain all my
non-flash people on a new way to place their content.
Anyone have any further info on this
subject....................?
Thanks in advance

You can still make Forms and Screens in Flash CS3
Professional. It's not under templates now though. Rather File>
New, then in the General tab of the dialog you can selected 'Flash
Slide Presentation' for screens, of 'Flash Form Application' for
forms..

Insufficient permissions for performing this operation through Windows Form application.

When accessing a report through the browser the user can view the report, however, have a report viewer in a Windows Form application get the below error when loading the report:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Web.Services.Protocols.SoapException: The permissions granted to user
'domain\username'
are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'domain\username' are insufficient for performing this operation.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at ReportServer.ReportService.ReportingService2010.GetReportServerConfigInfo(Boolean ScaleOut)
   at ReportServer.ReportItems.GetReportServerName()
   at Evolution2Application.FormMain.treeViewEvolutionReports_AfterSelect(Object sender, TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
   at System.Windows.Forms.TreeView.WmNotify(Message& m)
   at System.Windows.Forms.TreeView.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
C# code I use to connect to the reporting service
ReportingService2010
rs =newReportingService2010();
rs.Credentials
=System.Net.CredentialCache.DefaultCredentials;
rs.Url
=http://sqlserver01/reportserver/reportservice2010.asmx;
Can someone explain what I need to do to prevent getting this error, the user has ContentManager rights on the server through a security group.

found the issue rs.GetConfigInfo(false) was causing the error, now removed this.

Poor performance of web dynpro application

Hi,
I have developed web dynpro application which fetches data from R3 system using JCO connection.Large amount of data is transferred between R3 and application,because of which it is taking too long for displaying result.
After displaying timestamp before and after RFC execution code I came to know that, it is taking approx. 5 min for RFC execution, resulting in poor performance.Time taken for rest of processing is negligible.Is there any way by which I can reduce time for RFC execution or data transfer?
Thanks in advance,
Apurva

HI Apurva,
I think u r displaying the whole data at a stretch in the front end. So it will take some time for rendring. So try to reduce the display elements (For example, for tables, display only 10 rows at a time).
regards
Fahad Hamsa

WAD-Analysis Item-Poor performance for new lines

Hi.
I use WAD7 for entering new records in IP.
According to our business requirements, in analysis item properties I have defined "Number of New Lines in Planning Queries" = 50.
After that I face before extremely poor performance - it takes about 1-2 minutes until the page has loaded (note that it is empty page - only new blank rows).
When I define new lines = 1 performance is very good (2-3 sec).
Does anybody know what could be the problem ?
Thanks.

Hello Andrey,
the number of new lines configured in WAD is completely unknown in the ABAP backend and has no impact on backend performance; in fact, the front end gets information about one 'line' of template cells, this costs nothing.
Checks for characteristic relationships etc. only may have significant costs for cells of the result set, not for new lines.
Whether this problem comes from the ABAP backed or form the Java stack or from the browser rendering can be checked
with an RSTT trace. Is the run time of the trace different between 1 or 50 new lines, were different backend calls recorded?
If not, the problem comes from the Java stack or from the browser rendering. One can check the latter via task manager.
To check (partially) the run time in Java and/or ABAP stack add the parameter &PROFILING=X in the url, cf. note 1048691.
Regards,
Gregor

What could be the reason for continuous Full GC's during application startu

What could be the reason for continuous Full GC's during application (webapplication deployed on tomcat) startup?
JDK 1.6
Memory settings
-Xms1024M -Xmx1024M -XX:PermSize=200M -XX:MaxPermSize=512M -XX:+UseParallelOldGC
jmap output is below
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 1073741824 (1024.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = 17592186044415 MB
OldSize = 5439488 (5.1875MB)
NewRatio = 2
SurvivorRatio = 8
PermSize = 209715200 (200.0MB)
MaxPermSize = 536870912 (512.0MB)
Verbose GC logs
==========
0.194: [GC [PSYoungGen: 10489K->720K(305856K)] 10489K->720K(1004928K), 0.0061190 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
0.200: [Full GC (System) [PSYoungGen: 720K->0K(305856K)] [ParOldGen: 0K->594K(699072K)] 720K->594K(1004928K) [PSPermGen: 6645K->6641K(204800K)], 0.0516540 secs] [Times: user=0.10 sys=0.00, real=0.06 secs]
6.184: [GC [PSYoungGen: 262208K->14797K(305856K)] 262802K->15392K(1004928K), 0.0354510 secs] [Times: user=0.18 sys=0.04, real=0.03 secs]
9.549: [GC [PSYoungGen: 277005K->43625K(305856K)] 277600K->60736K(1004928K), 0.0781960 secs] [Times: user=0.56 sys=0.07, real=0.08 secs]
11.768: [GC [PSYoungGen: 305833K->43645K(305856K)] 322944K->67436K(1004928K), 0.0584750 secs] [Times: user=0.40 sys=0.05, real=0.06 secs]
15.037: [GC [PSYoungGen: 305853K->43619K(305856K)] 329644K->72932K(1004928K), 0.0688340 secs] [Times: user=0.42 sys=0.01, real=0.07 secs]
19.372: [GC [PSYoungGen: 273171K->43621K(305856K)] 302483K->76957K(1004928K), 0.0573890 secs] [Times: user=0.41 sys=0.01, real=0.06 secs]
19.430: [Full GC (System) [PSYoungGen: 43621K->0K(305856K)] [ParOldGen: 33336K->54668K(699072K)] 76957K->54668K(1004928K) [PSPermGen: 36356K->36296K(204800K)], 0.4569500 secs] [Times: user=1.77 sys=0.02, real=0.46 secs]
19.924: [GC [PSYoungGen: 4280K->128K(305856K)] 58949K->54796K(1004928K), 0.0041070 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
19.928: [Full GC (System) [PSYoungGen: 128K->0K(305856K)] [ParOldGen: 54668K->54532K(699072K)] 54796K->54532K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.3531480 secs] [Times: user=1.19 sys=0.10, real=0.35 secs]
20.284: [GC [PSYoungGen: 4280K->64K(305856K)] 58813K->54596K(1004928K), 0.0040580 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
20.288: [Full GC (System) [PSYoungGen: 64K->0K(305856K)] [ParOldGen: 54532K->54532K(699072K)] 54596K->54532K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2360580 secs] [Times: user=1.01 sys=0.01, real=0.24 secs]
20.525: [GC [PSYoungGen: 4280K->96K(305856K)] 58813K->54628K(1004928K), 0.0030960 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
20.528: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54532K->54533K(699072K)] 54628K->54533K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2311320 secs] [Times: user=0.88 sys=0.00, real=0.23 secs]
20.760: [GC [PSYoungGen: 4280K->96K(305856K)] 58814K->54629K(1004928K), 0.0034940 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
20.764: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54533K->54533K(699072K)] 54629K->54533K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2381600 secs] [Times: user=0.85 sys=0.01, real=0.24 secs]
21.201: [GC [PSYoungGen: 5160K->354K(305856K)] 59694K->54888K(1004928K), 0.0019950 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
21.204: [Full GC (System) [PSYoungGen: 354K->0K(305856K)] [ParOldGen: 54533K->54792K(699072K)] 54888K->54792K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2358570 secs] [Times: user=0.98 sys=0.01, real=0.24 secs]
21.442: [GC [PSYoungGen: 4280K->64K(305856K)] 59073K->54856K(1004928K), 0.0022190 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
21.444: [Full GC (System) [PSYoungGen: 64K->0K(305856K)] [ParOldGen: 54792K->54792K(699072K)] 54856K->54792K(1004928K) [PSPermGen: 36300K->36300K(204800K)], 0.2475970 secs] [Times: user=0.95 sys=0.00, real=0.24 secs]
21.773: [GC [PSYoungGen: 11200K->741K(305856K)] 65993K->55534K(1004928K), 0.0030230 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
21.776: [Full GC (System) [PSYoungGen: 741K->0K(305856K)] [ParOldGen: 54792K->54376K(699072K)] 55534K->54376K(1004928K) [PSPermGen: 36538K->36537K(204800K)], 0.2550630 secs] [Times: user=1.05 sys=0.00, real=0.25 secs]
22.033: [GC [PSYoungGen: 4280K->96K(305856K)] 58657K->54472K(1004928K), 0.0032130 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
22.036: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54376K->54376K(699072K)] 54472K->54376K(1004928K) [PSPermGen: 36537K->36537K(204800K)], 0.2507170 secs] [Times: user=1.01 sys=0.01, real=0.25 secs]
22.289: [GC [PSYoungGen: 4280K->96K(305856K)] 58657K->54472K(1004928K), 0.0038060 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
22.293: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54376K->54376K(699072K)] 54472K->54376K(1004928K) [PSPermGen: 36537K->36537K(204800K)], 0.2640250 secs] [Times: user=1.07 sys=0.02, real=0.27 secs]
22.560: [GC [PSYoungGen: 4280K->128K(305856K)] 58657K->54504K(1004928K), 0.0036890 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
22.564: [Full GC (System) [PSYoungGen: 128K->0K(305856K)] [ParOldGen: 54376K->54377K(699072K)] 54504K->54377K(1004928K) [PSPermGen: 36537K->36536K(204800K)], 0.2585560 secs] [Times: user=1.08 sys=0.01, real=0.25 secs]
22.823: [GC [PSYoungGen: 4533K->96K(305856K)] 58910K->54473K(1004928K), 0.0020840 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
22.825: [Full GC (System) [PSYoungGen: 96K->0K(305856K)] [ParOldGen: 54377K->54377K(699072K)] 54473K->54377K(1004928K) [PSPermGen: 36536K->36536K(204800K)], 0.2505380 secs] [Times: user=0.99 sys=0.01, real=0.25 secs]
23.077: [GC [PSYoungGen: 4530K->32K(305856K)] 58908K->54409K(1004928K), 0.0016220 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
23.079: [Full GC (System) [PSYoungGen: 32K->0K(305856K)] [ParOldGen: 54377K->54378K(699072K)] 54409K->54378K(1004928K) [PSPermGen: 36536K->36536K(204800K)], 0.2320970 secs] [Times: user=0.95 sys=0.00, real=0.23 secs]
24.424: [GC [PSYoungGen: 87133K->800K(305856K)] 141512K->55179K(1004928K), 0.0038230 secs] [Times: user=0.01 sys=0.01, real=0.01 secs]
24.428: [Full GC (System) [PSYoungGen: 800K->0K(305856K)] [ParOldGen: 54378K->54950K(699072K)] 55179K->54950K(1004928K) [PSPermGen: 37714K->37712K(204800K)], 0.4105190 secs] [Times: user=1.25 sys=0.17, real=0.41 secs]
24.866: [GC [PSYoungGen: 4280K->256K(305856K)] 59231K->55206K(1004928K), 0.0041370 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
24.870: [Full GC (System) [PSYoungGen: 256K->0K(305856K)] [ParOldGen: 54950K->54789K(699072K)] 55206K->54789K(1004928K) [PSPermGen: 37720K->37719K(204800K)], 0.4160520 secs] [Times: user=1.12 sys=0.19, real=0.42 secs]
29.041: [GC [PSYoungGen: 262208K->12901K(275136K)] 316997K->67691K(974208K), 0.0170890 secs] [Times: user=0.11 sys=0.00, real=0.02 secs]
Edited by: 807460 on Feb 6, 2011 8:28 PM

What do you see if you use the least number of options you need to start the application. I would try just
-mx1024M -XX:MaxPermSize=512M I would only add options which appear to improve performance.

Poor performance for full screen desktop

Hi,
Full screen desktop ( displayed as Kiosk ) of Linux with gnome ( I believe it's the same for all window managers ) is poor ( even with command as ls you see the delays ).
It happens on the local network. Connection to the application server is SSH.
SGD server - Solaris 10 , Sun Fire 280. Application server is regular modern PC.
Regular windows performance is very good.
Any suggestions ?
Thanks

I think you will find the poor performance is only with GTK applications.
For example, if you go into a large directory of files, and do an ls -aRl, you will notice it is a lot slower with a gnome-terminal than it is with a plain xterm.
I think 4.3 will resolve this performance issue.

Performance of Oracle forms application

Hi,
I would like to know about the performance of Oracle forms application over HTTP protocol. We may have citrix server and diskless nodes. Can you please let me know about the performance of the oracle forms application compared with html codes? Can you please send me some info about the performnance of the application? Do we need to have any software on the client side for this?
Thanks
regards,
Vaidyanathan G

Bruno, did you solve the performance problem? I'm experiencing the same lack of speed.

Reasons for poor performance of Forms Application(s)....

Similar Messages

Maybe you are looking for