WLS vs WebSphere performance

I have been running informal benchmarks of WLS6.1SP2 and WebSphere4.0.4 on a Win32 box, and am surprised to see WLS to come in at ~60% of pagesPerSec/responseTime of WebSphere at same CPU utilization. Has anybody exeperienced similar behavior? I have read through the WL docs, but can't find anything in my setup that would impose a performance penalty.
Using a Win32 2CPU box with 654MB RAM, WL setup: IIS using iisproxy.dll proxies requests to two local WL servers. All tracing (IIS and WL) turned off. Images served by IIS. Remote ORCL db, connection pool size 10 initial/50 max. Same EJB used for both tests.

Interesting. Try splitting out the JSP from the EJB test. I'm curious where
you're paying the penalty.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Stephan Lips" <[email protected]> wrote in message
news:3db4370d$[email protected]..
I have been running informal benchmarks of WLS6.1SP2 and WebSphere4.0.4 ona Win32 box, and am surprised to see WLS to come in at ~60% of
pagesPerSec/responseTime of WebSphere at same CPU utilization. Has anybody
exeperienced similar behavior? I have read through the WL docs, but can't
find anything in my setup that would impose a performance penalty.
>
Using a Win32 2CPU box with 654MB RAM, WL setup: IIS using iisproxy.dllproxies requests to two local WL servers. All tracing (IIS and WL) turned
off. Images served by IIS. Remote ORCL db, connection pool size 10
initial/50 max. Same EJB used for both tests.

Similar Messages

  • WL vs WebSphere performance

    I have been running informal benchmarks of WLS6.1SP2 and
    WebSphere4.0.4 on a Win32 box, and am surprised to see WLS to come in
    at ~60% of pagesPerSec/responseTime of WebSphere at same CPU
    utilization. Has anybody exeperienced similar behavior? I have read
    through the WL docs, but can't find anything in my setup that would
    impose a performance penalty.
    Using a Win32 2CPU box with 654MB RAM, WL setup: IIS using
    iisproxy.dll proxies requests to two local WL servers. All tracing
    (IIS and WL) turned off. Images served by IIS. Remote ORCL db,
    connection pool size 10 initial/50 max. Same EJB used for both tests.

    That's very surprising. WLS should outrun websphere.
    Is the test environment idential? (ie does websphere go through the IIS
    proxying as well?)
    Are you using the same JDK for both setups? IBM's JDK tends to be
    faster than the Sun 1.3.x that is bundled with WLS. You might also try
    BEA's jrockit jvm.
    How many concurrent threads are you running? If you vary the client
    threads, does that change the WLS v Websphere relationship?
    -- Rob
    Stephan Lips wrote:
    I have been running informal benchmarks of WLS6.1SP2 and
    WebSphere4.0.4 on a Win32 box, and am surprised to see WLS to come in
    at ~60% of pagesPerSec/responseTime of WebSphere at same CPU
    utilization. Has anybody exeperienced similar behavior? I have read
    through the WL docs, but can't find anything in my setup that would
    impose a performance penalty.
    Using a Win32 2CPU box with 654MB RAM, WL setup: IIS using
    iisproxy.dll proxies requests to two local WL servers. All tracing
    (IIS and WL) turned off. Images served by IIS. Remote ORCL db,
    connection pool size 10 initial/50 max. Same EJB used for both tests.

  • Can not view 24 hours data in Websphere performance page

    We configured EM 10.2.0.5 to monitor Websphere 6.1 on AIX.
    Now we can see current data in the performance page.
    But when we switch to 24 hours view, there is not any data shown in the page.
    Does EM 10.2.0.5 support viewing Websphere historical data?

    This issue is solved.
    The OMR parameter job_queue_processes is set to 0.
    It should be 10 or above.

  • EJB20.zip patch and WLS 6.1 performance?

    Does the WLS 6.1 beta use the same ejb20.zip patch as WLS 6.0.x and does compiling
    and enabling this support increase performance of applications? The download
    for ejb20.zip is labeled WLS 6.0, not WLS 6.1.

    It's the same file for both...
    There is nothing in that file other than an enablement class. We have to do
    this enablement because it is required by Sun. The entire code base is
    always maintained within the server.
    Tyler
    "Don Wood" <[email protected]> wrote in message
    news:3b5d8b26$[email protected]..
    >
    Does the WLS 6.1 beta use the same ejb20.zip patch as WLS 6.0.x and doescompiling
    and enabling this support increase performance of applications? Thedownload
    for ejb20.zip is labeled WLS 6.0, not WLS 6.1.

  • Suggestion for a WLS book

    All,
    I need a book about WLS administration and performance tuning.
    We develop ADF applications, and I'm in charge to admin and deploy it, with best performances, on a standalone WLS.
    Could someone of you suggest me a good read on the subject ?
    Thanks in advance,
    Sergio.

    There are some mentioned here: http://www.munzandmore.com/2011/ora/review-weblogic-11g-administration-handbook-with-an-overview-of-other-wls-11g-books
    The first one has two excellent chapters on administration and performance tuning (respectively chapter 12 and 13)

  • WLS threads - how to retrieve individual operations?

    Hello everybody,
    can anyone tell me if is there a way to find out which WLS thread is
    performing each individual operation - for instance, compiling or executing
    a specific JSP?
    TIA
    Paola R.

    You can get a "photo" of what each execution thread is doing in two ways:
    - weblogic console - select a server in the left pane, then, on the right
    pane, select 'Monitoring' tab and 'General' subtab; click on 'Monitor all
    Active Queues...' then click on the 'default' queue
    - you can have a thread dump on the standard output using the command line
    Admin (http://e-docs.bea.com/wls/docs81/admin_ref/cli.html#THREAD_DUMP) or
    doing a kill -3 on the server provess
    Ciao
    Marco
    "Paola R." <[email protected]> wrote in message news:41505ea2@mail...
    Hello everybody,
    can anyone tell me if is there a way to find out which WLS thread is
    performing each individual operation - for instance, compiling orexecuting
    a specific JSP?
    TIA
    Paola R.

  • What about parameter weblogic.PosixSocketReaders in WLS 8.1

    Hi,
    I would want to know what is the effect of the parameter weblogic.PosixSocketReaders in wls 8.1?
    The only doc i can read on this subject is http://e-docs.bea.com/wls/docs70/perform/appb_tunetips.html and concerne wls 7.
    Which is the effect if I put this parameter at value 1 (with wls81 and native i/o)?
    Thanks.

    CASE_ID_NUM: 642649
    PosixSocketReaders and how they work in WLS:
    WLS utilizes native code to perform socket handling, called the performance pack. Native code polls sockets on the OS layer if a new socket and data has to be processed, if a socket contains data that WLS is supposed to process it is picked up by Java threads from the WLS SocketReader thread queue. The SocketReader Java threads have the task of passing the socket and the contained raw message to an execute thread performing the application specific processing.
    The flow of a socket and data from the OS to WLS is as follows:
    OS TCP/IP Socket --> WLS native code (performance pack) polls for sockets --> Java SocketReader thread -- dispatch --> WLS Java execute thread (e.g. execute thread from default WLS execute queue)
    The number of SocketReader threads is per default set to 3 on Unix environments, this is generally a good default value. In some case and specific OS environments experience has shown that tuning the number of SocketReader threads is beneficial to get the maximum performance from WLS in dispatching a socket from the native layer to a WLS execute thread.
    The reason why tuning the SocketReaders can have an positive effect is based on two main factors:
    1. SocketReader threads have many Java synchronization blocks as they are working very concurrently on the native code layer. 2. A big number of sockets being opened to WLS
    In case the JVM and/or OS is not very good in handling synchronization locks point 1. is the limiting performance factor of Socketreaders as the JVM and OS are more busy handling Java synchronization locks than doing the actual dispatch work. For such a scenario experience with other customers has shown that using PosixSocketReaders=1 is beneficial
    On the other side if the JVM and OS handle synchronization locks very well it can be beneficial to increase the number of PosixSocketReaders threads and thus allow WLS to dispatch more socket data from the native layer to a WLS execute thread in parallel.
    As the performance of PosixSocketReaders very much depends on the OS / JVM and if the system/application is heavily socket/network related a good value for PosixSocketReaders has to be identified based on test runs. Generally the default value of 3 PosixSocketReaders is good for most applications and environments.

  • Anyone working on WebSphere 7.0.0.13 using ADF

    According to Oracle documentation, IBM WebSphere 7.0.0.13 is certified for JDeveloper & ADF. But I would like to know if anyone is successfully implemented and application is working as per their requirements.
    Thanks

    Hi,
    I think the problem is the ADF Face.
    Let me explain the step that I tried.
    I create simple ADF application with one button and one JSF page is built using components from Trinidad Components library that are avaiable in JDev 11g. ( without ADF Face).
    This application is working fine in both integrated WLS and WebSphere Server
    Then, I try to create ADF application with one button and one JSF page is built using components from ADF Faces that are avaiable in JDev 11g.
    After I deployed and tried to access the application , I got this error.
    It appears that the problem could be with ADF Faces Library.
    This is the error stack.
    ADF_FACES-60032:Could not find ExtendedRenderKitService.
    oracle.adfinternal.view.faces.lifecycle.LifecycleImpl handleException ADFFACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
    Error
    ====
    [11/9/11 11:05:03:155 ICT] 0000002b servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet Faces Servlet in application ADF3_war. Exception created : java.lang.NullPointerException: ADF_FACES-60032:Could not find ExtendedRenderKitService.
    at oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit.getService(RichRenderKit.java:163)
    at org.apache.myfaces.trinidad.util.Service.getService(Service.java:86)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.getService(UnifiedRenderKit.java:146)
    at org.apache.myfaces.trinidad.util.Service.getService(Service.java:86)
    at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl._getExtendedRenderKitService(ViewHandlerImpl.java:374)
    at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:171)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:710)
    oracle.adfinternal.view.faces.lifecycle.LifecycleImpl handleException ADFFACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
    Other Information
    ==============
    - JDeveloper 11.1.1.3
    - WebSphere Platform 7.0.0.13
    - Linux, version 2.6.18-194.el5
    - IBM JDK 1.6
    I already tried https://support.oracle.com but they told me that Oracle will not look into the Bug if IBM JDK is used since it is not supported.
    They mentioned that JDeveloper 11g is supported with Sun JDK and JRockit JDK. JDev 11g is NOT supported with IBM JDK.
    Regards,
    zenoni

  • Re: Throughput drops dramatically when I increase the number of instances in a cluster

    Thanks for the quick reply.
              Yes, we are running WLS with the performance pack.
              "Bernie Wong" <[email protected]> wrote in message
              news:[email protected]...
              > Fellow clusterers ....
              >
              > I have an EJB driver program that pumps work into a WLS cluster. For
              > scalability, I increase the number of drivers. The drivers have a big pool
              > of work to pump into the cluster.
              >
              > I noticed that with 6 (nothing special about that number) drivers, I can
              get
              > 500K worked items per hour in a single instance (clustered). That is, the
              > instance is cluster enabled and is watching for multicast, etc..
              >
              > When I add the second instance into the cluster, the cluster-wide
              throughput
              > with the six drivers drops to 370K items per hour. When I add the third
              > instance, the cluster-wide throughput drops further to 250K items per
              hour.
              > When I kill an instance, the throughput grows back to 370K items per hour.
              > When I kill another instance (to get back to one instance), the throughput
              > grows back to 500K/hr.
              >
              > Can somebody point out what we are doing wrong - do we need to tweek some
              > WLS parameters, do we have to avoid some features that limit cluster
              > scalability, etc..
              >
              > My WLS configuration is .....
              > - WLS 5.1, SP5
              > - JDK 1.2.1_04c with JIT, no Hotspot
              >
              > My hardware/software configuration consists of:
              > - an E4500 - 8 processor database server - this is only running at 15%
              > server busy
              > - three E4500 - all 8 processors/6GB RAM - application processors
              >
              > The cluster is implemented with one instance per application server.
              > Each application server is only 10-15% busy.
              >
              > My driver and application is ....
              > - stateless EJB driver and stateless EJB bean
              >
              > Your thoughts and comments would be greatly appreciated.
              >
              > Bernie
              >
              >
              

    Thanks. It works. We screwed up the settings.
              "Bernie Wong" <[email protected]> wrote in message
              news:[email protected]...
              > Thanks for the reply.
              >
              > We ran the benchmark again and got the same scaling profile. This
              afternoon,
              > we are going to run a benchmark with a really simple driver + bean (a do
              > nothing bean) and see if we get the same scaling profile. From all the
              > responses, it would appear that WLS can scale therefore we want to isolate
              > the problem to either our code or our configuration (or both).
              >
              > I will let you know.
              >
              > Bernie
              >
              > "Rob Woollen" <[email protected]> wrote in message
              > news:[email protected]...
              > > Make sure that this was set on the client not the server.
              > >
              > > -- Rob
              > >
              > > Bernie Wong wrote:
              > > >
              > > > Jim,
              > > >
              > > > Thanks for the suggestions. One of my performance engineers ran
              several
              > > > experiments last week where he set the executeThreadCount to 6 and to
              10
              > > > along with a percentSocketReaders to 50. He saw no improvement. We
              will
              > > > rerun that experiment again since that seems to be the most common
              > > > recommendation.
              > > >
              > > > Bernie
              > > >
              > > > "Jim Zhou" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > One possible reason is not enough socket reader execute threads, try
              > to do
              > > > > this:
              > > > > "-Dweblogic.system.executeThreadCount=10"
              > > > > "-Dweblogic.system.percentSocketReaders=50" on your client JVM
              startup
              > > > > command line.
              > > > >
              > > > > http://www.weblogic.com/docs51/admindocs/tuning.html#tuning clients
              > > > >
              > > > > WebLogic RMI
              > > > > If you are using WebLogic RMI clients and there are more than 2
              > Weblogic
              > > > > servers in a cluster, you may encounter a significant performance
              > > > > degradation (very long round trip times for stateless session beans,
              > for
              > > > > instance). The solution is to make some property changes on the
              client
              > > > side
              > > > > as explained below.
              > > > >
              > > > > The solution to this problem is to ensure that there are at least as
              > many
              > > > > socket reader threads as there are connections to the server and
              also
              > > > > allowing for some extra threads for processing other tasks. This is
              > > > > accomplished by starting the client with the command line argument
              > > > > "-Dweblogic.system.percentSocketReaders" set to a sufficiently high
              > > > > percentage (say 50) and by ensuring that there sufficient number of
              > > > execute
              > > > > threads for other processing on the client. A metric of twice the
              > number
              > > > of
              > > > > execute threads as there are servers in a cluster should work fine
              if
              > the
              > > > > above percentage is at 50. The command line argument affecting the
              > number
              > > > of
              > > > > execute threads is
              > > > >
              > > > > "-Dweblogic.system.executeThreadCount".
              > > > >
              > > > > For instance, we could use:
              > > > >
              > > > > "-Dweblogic.system.executeThreadCount=10"
              > > > >
              > > > > and
              > > > >
              > > > > "-Dweblogic.system.percentSocketReaders=50"
              > > > >
              > > > > when testing with 3 or 4 servers in a cluster.
              > > > >
              > > > >
              > > > > Bernie Wong <[email protected]> wrote in message
              > > > > news:[email protected]...
              > > > > > Thanks for the quick reply.
              > > > > >
              > > > > > Yes, we are running WLS with the performance pack.
              > > > > >
              > > > > >
              > > > > > "Bernie Wong" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > > Fellow clusterers ....
              > > > > > >
              > > > > > > I have an EJB driver program that pumps work into a WLS cluster.
              > For
              > > > > > > scalability, I increase the number of drivers. The drivers have
              a
              > big
              > > > > pool
              > > > > > > of work to pump into the cluster.
              > > > > > >
              > > > > > > I noticed that with 6 (nothing special about that number)
              drivers,
              > I
              > > > can
              > > > > > get
              > > > > > > 500K worked items per hour in a single instance (clustered).
              That
              > is,
              > > > > the
              > > > > > > instance is cluster enabled and is watching for multicast, etc..
              > > > > > >
              > > > > > > When I add the second instance into the cluster, the
              cluster-wide
              > > > > > throughput
              > > > > > > with the six drivers drops to 370K items per hour. When I add
              the
              > > > third
              > > > > > > instance, the cluster-wide throughput drops further to 250K
              items
              > per
              > > > > > hour.
              > > > > > > When I kill an instance, the throughput grows back to 370K items
              > per
              > > > > hour.
              > > > > > > When I kill another instance (to get back to one instance), the
              > > > > throughput
              > > > > > > grows back to 500K/hr.
              > > > > > >
              > > > > > > Can somebody point out what we are doing wrong - do we need to
              > tweek
              > > > > some
              > > > > > > WLS parameters, do we have to avoid some features that limit
              > cluster
              > > > > > > scalability, etc..
              > > > > > >
              > > > > > > My WLS configuration is .....
              > > > > > > - WLS 5.1, SP5
              > > > > > > - JDK 1.2.1_04c with JIT, no Hotspot
              > > > > > >
              > > > > > > My hardware/software configuration consists of:
              > > > > > > - an E4500 - 8 processor database server - this is only
              > running at
              > > > > 15%
              > > > > > > server busy
              > > > > > > - three E4500 - all 8 processors/6GB RAM - application
              > processors
              > > > > > >
              > > > > > > The cluster is implemented with one instance per application
              > > > server.
              > > > > > > Each application server is only 10-15% busy.
              > > > > > >
              > > > > > > My driver and application is ....
              > > > > > > - stateless EJB driver and stateless EJB bean
              > > > > > >
              > > > > > > Your thoughts and comments would be greatly appreciated.
              > > > > > >
              > > > > > > Bernie
              > > > > > >
              > > > > > >
              > > > > >
              > > > > >
              > > > >
              > > > >
              >
              >
              

  • Java.lang.OutOfMemory error when transforming xml using xsl with Weblogic 6.1 sp2

    Hello,
    I have an OutOfMemoryError when applying an xsl transformation to generate html
    code in a web page. I'm running Weblogic 6.1 sp2
    I think the problem comes from the objectin which th html is stored during the
    transformation. The problem only occurs from a minimal xml size. I could fix
    it by increasing JVM allocated size but I would like to find a more flexible solution.
    If I know an other way to solve this problem, I really would appreciate !
    Thanl you,
    Laurent.
    [AgentsGeres.jsp]

    Hello,
    You might try asking your question in the JSP newsgroup:
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.jsp
    There just may not be a more flexible solution :-)
    This doc may be of some value, see chapter 2:
    http://edocs.bea.com/wls/docs61/pdf/perform.pdf
    HTH,
    Bruce
    Laurent Gosuin wrote:
    >
    Hello,
    I have an OutOfMemoryError when applying an xsl transformation to generate html
    code in a web page. I'm running Weblogic 6.1 sp2
    I think the problem comes from the objectin which th html is stored during the
    transformation. The problem only occurs from a minimal xml size. I could fix
    it by increasing JVM allocated size but I would like to find a more flexible solution.
    If I know an other way to solve this problem, I really would appreciate !
    Thanl you,
    Laurent.
    Name: AgentsGeres.jsp
    AgentsGeres.jsp Type: Hypertext Markup Language (text/html)
    Encoding: base64

  • Application Clustering & JMS

    Hi All,
    I am in the process of moving an existing application to WebLogic 11g. This applications used to run on OC4J and we used multiple JVMs for the OC4J container to get some scalability.
    For WebLogic, we are considering a similar feature and arrived at the WebLogic Cluster with an HTTP-proxy for distributing the incoming traffic. The application depends on certain hard-coded resources.
    We have a very simple cluster, consisting of 2 managed Servers: MS1, MS2.
    MS1 is the server that physically holds the JMS Server, an MDB to process messages from this JMS queue.
    The application is deployed to the entire cluster (MS1+MS2)
    After restarting the cluster, we find that the application is available on MS1, but cannot be access from MS2 since the JNDI replication in the cluster seems to take place AFTER the MS2 server has tried to activate the application deployment. Hence, the application is in a failed state on MS2, having run into an javax.naming.NameNotFoundException (after this, WLS tries to perform the JNDI replication across the cluster and it is only after this that the JNDI entries do show on the MS2 server's JNDI tree).
    We have multiple queues with multiple consumers, so we do not want to create a distributed queue, since then we would also need to create multiple instance for each consumer (viz. one for each actual destination) ?
    This problem occurs both when using a regular and a migratable target for the JMS server setup ...
    Any ideas how to prevent the application deployment/activation BEFORE JNDI replication ?
    Thx,
    Milco

    We're having similar problem with distributed destinations:
    - 2 managed servers in cluster - MS1 and MS2
    - 2 default migratable targets - MS1 (migratable) and MS2 (migratable)
    - 2 JMS Servers - JMSServer1 and JMSServer2, 1 on each migratable target
    - System JMS Module targeted to cluster
    in it: Connection factories targeted to cluster and topics and queues targeted to subdeployment "JMSServer1,JMSServer2"
    EAR application, deployed to cluster, is trying to connect to JMS destinations from postStart(ApplicationLifecycleEvent evt).
    Understanding is that by the time postStart is called all JMS resources should've been created, but application is getting error
    javax.naming.NameNotFoundException: Unable to resolve 'Queue JNDI Name'. Resolved '';
    Could anybody help with this?..

  • Periods of inactivity causes a slow down

    hi all..
    we have a websphere 6.1 server and a java application which is a multi thread rmi server (a product from an external supplier), residing on the same aix machine, using the same jdk (NOT jvm off course) , and both are connected to oracle.
    we have noticed that periods of inactivity in our web application causes a slowdown in performance once they used again, for example you do an operation in the web application go for lunch, do the same thing the suffer a slow performance. lately while the scanning the log of the rmi server, we have noticed that it too has the same issue, after periods (which could be minutes even) the same operation could take 2 times more. our supplier suggested that it might have something to do with swapping/paging the application , but i'm not sure, we first thought the websphere performs some sort of resources clean-ups, but the rmi application has no such thing (not using even a connection pool), so i was thinking that maybe oracle has something to do with it.
    is there anyway to monitor such a thing, the memory paging, and oracle connections?

    i the following test:
    i create a small servlet under websphere which opened a connection (using jdbc ,no data source) ,executed a query and returned forward only result set , i ran thought the result set, (extracting only one field) and closed the connection, the measured in code the time it took for each action (connection to oracle, execute the statment and itirating the results)
    the first time, the itirating thought the query took 800 ms, but subseqient actions (just placing refresh on the page which caused the servlet to do it again) only took half the time.
    i waited 10 minutes and did it again, this time connecting to oracle took 5 seconds! (instead 80-100 ms it usually took including the first time) but the query look preformed ok).
    i waited 10 more minutes and then did it again, this time it preformed ok, i pressed again but this time the loop itself took 1.2 seconds!, what can i learn from that?

  • Weblogic 9.2 capability

    Please help me with answers for the below questions
    1) Weblogic 9.2 server capacity for handling the concurrent users (max count of concurrent users)?
    2) Maximum user's count for Weblogic 9.2 server (Normal users count)?
    3) How many concurrent requests Weblogic can handle?
    4) What are the scenarios for going with load balancer for Weblogic 9.2 server?
    PS: Application is expected to have over 400 users and 50 concurrent users, and for each year the users growth is 15%
    Edited by: user10238705 on Sep 9, 2008 1:37 PM
    Edited by: user10238705 on Sep 9, 2008 2:09 PM

    Answering precisely will be difficult because of all the factors involved and you will likely get an "it depends" for many of your questions. The capacity planning guide provides general guidelines that you should consider.
    HTML: http://edocs.bea.com/wls/docs92/perform/appc_capplan.html
    PDF: http://edocs.bea.com/wls/docs92/pdf/perform.pdf

  • OutOfMemoryError when applying an xsl transformation

              Hello,I have an OutOfMemoryError when applying an xsl transformation to generate
              htmlcode in a web page. I'm running Weblogic 6.1 sp2I think the problem comes
              from the objectin which th html is stored during thetransformation. The problem
              only occurs from a minimal xml size. I could fixit by increasing JVM allocated
              size but I would like to find a more flexible solution. If I know an other way
              to solve this problem, I really would appreciate !
              Thank you,
              Laurent.
              [AgentsGeres.jsp]
              

    Hello,
    You might try asking your question in the JSP newsgroup:
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.jsp
    There just may not be a more flexible solution :-)
    This doc may be of some value, see chapter 2:
    http://edocs.bea.com/wls/docs61/pdf/perform.pdf
    HTH,
    Bruce
    Laurent Gosuin wrote:
    >
    Hello,
    I have an OutOfMemoryError when applying an xsl transformation to generate html
    code in a web page. I'm running Weblogic 6.1 sp2
    I think the problem comes from the objectin which th html is stored during the
    transformation. The problem only occurs from a minimal xml size. I could fix
    it by increasing JVM allocated size but I would like to find a more flexible solution.
    If I know an other way to solve this problem, I really would appreciate !
    Thanl you,
    Laurent.
    Name: AgentsGeres.jsp
    AgentsGeres.jsp Type: Hypertext Markup Language (text/html)
    Encoding: base64

  • Newsgroups -- general use announcement

    General use announcement for BEA newsgroups:
    BEA newsgroups are intended as positive forums for individuals that share common
    interests in BEA products to exchange ideas and share information.
    BEA employees that participate in these groups volunteer their time.
    BEA newsgroups are not the place for advertisement of products or services.
    BEA newsgroups are not the place for non-productive rants. Have respect for all
    participants. Abusive language is prohibited as well as non-productive.
    BEA newsgroups are not BEA technical support. You can not log a bug report here.
    For your support options, please go to:
    http://www.bea.com/support/index.jsp
    Thank you
    Lauren Wright
    WLS Product Manager - Performance, Platform Certification, Beta

    General use announcement for BEA newsgroups:
    BEA newsgroups are intended as positive forums for individuals that share common
    interests in BEA products to exchange ideas and share information.
    BEA employees that participate in these groups volunteer their time.
    BEA newsgroups are not the place for advertisement of products or services.
    BEA newsgroups are not the place for non-productive rants. Have respect for all
    participants. Abusive language is prohibited as well as non-productive.
    BEA newsgroups are not BEA technical support. You can not log a bug report here.
    For your support options, please go to:
    http://www.bea.com/support/index.jsp
    Thank you
    Lauren Wright
    WLS Product Manager - Performance, Platform Certification, Beta

Maybe you are looking for