WebLogic RMI UNIX Performance problem

Hi.
I'm experiencing problems with the performance of RMI calls from within session
beans to external RMI services. I have a system running 4 RMI services in separate
JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+ Gb of RAM.
The system was developed on NT and deployed to UNIX. A typical request is serviced
in 70-90 ms on the NT development box (Desktop 512Mb RAM) but when deployed to
the UNIX box takes anywhere between 500-4000 ms. Performance metrics in the code
indicate that 'crunch' times are similar but remote RMI calls are orders of magnitude
greater.
Has anybody had similar problems? I have checked the tuning guides wrt TCP/IP
configurations but would not expect such a large difference using the default
Solaris configuration. Memory and CPU utilisation on the SPARC are low as are
I/O and other metrics available from vmstat.
Cheers
Pete

Hi.
The JVMs are running on the same machine thus should be looking in /etc/hosts
and not going via DNS.
I have read there is a performance gain by tying WL to a single CPU, any insight?
Pete
Andy Piper <[email protected]> wrote:
"Pete Harris" <[email protected]> writes:
I'm experiencing problems with the performance of RMI calls from withinsession
beans to external RMI services. I have a system running 4 RMI servicesin separate
JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+Gb of RAM.
The system was developed on NT and deployed to UNIX. A typical requestis serviced
in 70-90 ms on the NT development box (Desktop 512Mb RAM) but whendeployed to
the UNIX box takes anywhere between 500-4000 ms. Performance metricsin the code
indicate that 'crunch' times are similar but remote RMI calls are ordersof magnitude
greater.
Has anybody had similar problems? I have checked the tuning guideswrt TCP/IP
configurations but would not expect such a large difference using thedefault
Solaris configuration. Memory and CPU utilisation on the SPARC arelow as are
I/O and other metrics available from vmstat.Its possible that you are getting a DNS lookup for each request or
worse a reverse lookup. You might want to try using IP addresses in
your config to see if that helps.
andy

Similar Messages

  • Oracle Performance problem in Tru64 Unix

    Hello All,
    I am having performance problem in Tru6u Unix. Details are mentioned below :
    OS: Tru64 Unix
    Oracle Version : 8.1.7.4.0
    Forms : 6.0
    Mode: Oracle Parallel Server
    When, developers are trying to save some data using forms, it's taking too much time.
    Any hint/idea, how to start tracking the things, will be highly appreciated.
    Regards,
    Rajeev Tomar

    Check what are the session waits from v$session_wait and try to tune them.
    If possible, get the code and tune the sqls.
    Without knowing the application behaviour and other related stuff, no one can simple adice on performance problems.
    Jaffar

  • Weblogic problem,weblogic.rmi.extensions.RemoteRuntimeException: Unexpected

    hello，everyone.
    I have a problem.please help me.
    My application is running on weblogic 9.2. My oracle is oracle10g. system:linux redhat4.
    my weblogic's log have a problem.
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
    at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
    at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
    at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
    at jsp_servlet._ctssale.__teamline_show._jspService(__teamline_show.java:264)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:230)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at filters.AuthFilter.doFilter(AuthFilter.java:95)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3200)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1844)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Hi
    Looking at the error stack trace, you are getting this error when trying to close the statement object from your own java code (not weblogic code...) - DBController.releaseConn(...)
    at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
    at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
    at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
    at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
    Well check the code you have at this location. Usually the way we release/close the db resources are like first close ResultSet, then Statement, then Connection. But if you close connection first, then try to close the Statement object, it throws errors like what you see.
    I am giving 2 methods code snippet. One method is caleld like closeAll(..). This method gets called in finally block of all other db methods that does the actual db code to connect and get data etc etc.
    // Sample main method that does all db stuff...This is just code snippet only and NOT the full code. Focus on try catch finally block
    public static void getCustomerProfile(long custId) throws Exception {
         Connection aConnection = getConnection();
         CallableStatement aCallableStatement = null;
         ResultSet aResultSet = null;
         try {
              aCallableStatement = aConnection.prepareCall("{ call someFunction(?, ?) }");
              aCallableStatement.execute();
              aResultSet = (ResultSet) aCallableStatement.getObject("variable_name_from_sp");
              while(aResultSet.next()) {
                   // get all data for each record etc...
         } catch (Exception e) {
              e.printStackTrace();
              throw e;
         } finally {
              closeAll(aConnection, aCallableStatement, aResultSet);
    // While closing RS, Statment, Connection, enclose them in their own try/catch block and ofcourse check for nulls first
    public static void closeAll(Connection aConn, Statement aStmt, ResultSet aRS) {
         if (aRS != null) {
              try {
                   aRS.close();
              } catch (Exception e) {
                   System.out.println("Not Able To Close The ResultSet");
                   //e.printStackTrace();
         if (aStmt != null) {
              try {
                   aStmt.close();
              } catch (Exception e) {
                   System.out.println("Not Able To Close The Statement");
                   //e.printStackTrace();
         if (aConn != null) {
              try {
                   aConn.close();
              } catch (Exception e) {
                   System.out.println("Not Able To Close The Connection");
                   //e.printStackTrace();
    }Thanks
    Ravi Jegga

  • Performance problem with Oracle

    We are currently getting a system developed in Unix/Weblogic/Tomcat/Oracle environment. We have developed a screen that contains 5 or 6 different parameters to select from. We could select multiple parameters in each of these selections. The idea behind the subsequent screens is to attach information to already existing data/ possible future data that matches the selection criteria.
    Based on these selections, existing data located within the system in a table is searched and those that match are selected. Also new rows are created in the table against combinations that do not currently have a match. Frequently multiple parameters are selected, and 2000 different combinations need to be searched in the table. Of these selections, only about 100 or 200 combinations will be available in existing data. So the system is having to insert 1800 rows. The user meanwhile waits for the system to come up with data based on their selections. The user is not willing to wait more than 30 seconds to get to the next screen. In the above mentioned scenario, the system takes more than an hour to insert the new records and bring the information up. We need suggestions to see if the performance can be improved this drastically. If not what are the alternatives? Thanks

    The #1 cause for performance problems with Oracle is not using it correctly.
    I find it hard to believe that with the small data volumes mentioned, that you can have perfornance problems.
    You need to perform a sanity check. Are you using Oracle correctly? Do you know what bind variables are? Are you using indexes correctly? Are you using PL/SQL correctly? Is the instance setup correctly? What about storage, are you using SAME (RAID10) or something else? Etc.
    Facts. Oracle peforms exceptionally well. Oracle exceptionally well.
    Simple example from a benchmark I did on this exact same subject. App-tier developers not understanding and not using Oracle correctly. Incorrect usage of Oracle doing a 100,000 SQL statements. 24+ minutes elapsed time. Doing those exact same 100,000 SQL statement correctly (using bind variables) - 8 seconds elapsed time. (benchmark using Oracle 10.1.0.3 on a Sunfire V20z server)
    But then you need to use Oracle correctly. Are you familiar with the Oracle Concepts Guide? Have you read the Oracle Application Developer Fundamentals Guide?

  • Weblogic on unix vs nt

    What are some of the advantages of running weblogic on unix vs nt?
    Can someone point me to books about performance?
    Thanks,
    Linda

    Generally, Unix is much better for running things for long periods of time
    and under varying amounts of load. Unix is also considered much better for
    administration, and much more secure. I personally think Unix (all variants)
    is dreadful to use which coincidentally goes a long way to explaining its
    stability -- no one actually wants to use it, so it doesn't end up with
    loads of unnecessary junk on it. Our Sun server only goes down when the
    power goes out for longer than the UPS can feed it.
    Windows NT may have an edge if you are administering only one server and you
    are used to the Windows interface and it is inside a firewall with only one
    port exposed. I have been happy with Windows 2000 (NT5) but I've also heard
    horror storries with driver problems when upgrading from NT4. One big thing
    that it fixed was the unexplainable "I've been running for more than 8 hours
    so I'll grind to a halt" problem that NT4 had. (Ever come up to an NT server
    and move the mouse to "wake it up" and have it take 5 or 6 minutes to
    re-paint the screen while it thrashes the hard drive?) Using Windows 2000
    for servers and "single tasking" them (basically only one responsibility per
    server) seems to be stable enough, and reboots are down from daily (NT4) to
    roughly monthly.
    Peace,
    Cameron Purdy
    Tangosol Inc.
    Tangosol Coherence: Clustered Coherent Cache for J2EE
    Information at http://www.tangosol.com/
    "Linda Smith" <[email protected]> wrote in message
    news:[email protected]..
    What are some of the advantages of running weblogic on unix vs nt?
    Can someone point me to books about performance?
    Thanks,
    Linda

  • StuckThreadMaxTime,"weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce6

    Hi guys!
    I am having a problem suddenly with weblogic application server on aix box. I am getting error after couple of users login.managed Server is getting shutdown. Here is the description of the error.
    <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '47' for queue: 'weblogic.kernel.Default' has been busy for "717" seconds working on the request "weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce690f", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
    Please suggest something to fix this problem.can you explain how we can check thread dumps in weblogic on unix environment.
    -Chandu

    Paul Eddington wrote:
    Thanks for the response.
    We don't have any connection pools defined.
    The application we have deployed gets information from the DB all the time. But it makes it's own connection. We connect to an Oracle 9i DB running on a different server. We are running on AIX 5.3 servers.
    Thanks again
    PaulHi. nevermind about the pool question. If/when you get that sort of message you want to get a thread
    dump of the server or find the log where it shows the full stacktrace of that thread. The message
    simply says a thread has been busy or hanging longer than the WLS limit (configurable). The thread
    could be hung on a lock, waiting for the DBMS, in an infinite loop, os simply not done yet with
    some job that is taking more than the stuck-thread-limit. WLS doesn't actually know what the
    thread is doing...
    Joe

  • (new?) performance problem using jDriver after a Sql Server 6.5 to 2000 conversion

    Hi,
    This is similar - yet different - to a few of the old postings about performance
    problems with using jdbc drivers against Sql Server 7 & 2000.
    Here's the situation:
    I am running a standalone java application on a Solaris box using BEA's jdbc driver
    to connect to a Sql Server database on another network. The application retrieves
    data from the database through joins on several tables for approximately 40,000
    unique ids. It then processes all of this data and produces a file. We tuned
    the app so that the execution time for a single run through the application was
    24 minutes running against Sql Server 6.5 with BEA's jdbc driver. After performing
    a DBMS conversion to upgrade it to Sql Server 2000 I switched the jDriver to the
    Sql Server 2000 version. I ran the app and got an alarming execution time of
    5hrs 32 min. After some research, I found the problem with unicode and nvarchar/varchar
    and set the "useVarChars" property to "true" on the driver. The execution time
    for a single run through the application is now 56 minutes.
    56 minutes compared to 5 1/2 hrs is an amazing improvement. However, it is still
    over twice the execution time that I was seeing against the 6.5 database. Theoretically,
    I should be able to switch out my jdbc driver and the DBMS conversion should be
    invisible to my application. That would also mean that I should be seeing the
    same execution times with both versions of the DBMS. Has anybody else seen a
    simlar situation? Are there any other settings or fixes that I can put into place
    to get my performance back down to what I was seeing with 6.5? I would rather
    not have to go through and perform another round of performance tuning after having
    already done this when the app was originally built.
    thanks,
    mike

    Mike wrote:
    Joe,
    This was actually my next step. I replaced the BEA driver with
    the MS driver and let it run through with out making any
    configuration changes, just to see what happened. I got an
    execution time of about 7 1/2 hrs (which was shocking). So,
    (comparing apples to apples) while leaving the default unicode
    property on, BEA ran faster than MS, 5 1/2 hrs to 7 1/2 hrs.
    I then set the 'SendStringParametersAsUnicode' to 'false' on the
    MS driver and ran another test. This time the application
    executed in just over 24 minutes. The actual runtime was 24 min
    16 sec, which is still ever so slightly above the actual runtime
    against SS 6.5 which was 23 min 35 sec, but is twice as fast as the
    56 minutes that BEA's driver was giving me.
    I think that this is very interesting. I checked to make sure that
    there were no outside factors that may have been influencing the
    runtimes in either case, and there were none. Just to make sure,
    I ran each driver again and got the same results. It sounds like
    there are no known issues regarding this?
    We have people looking into things on the DBMS side and I'm still
    looking into things on my end, but so far none of us have found
    anything. We'd like to continue using BEA's driver for the
    support and the fact that we use Weblogic Server for all of our
    online applications, but this new data might mean that I have to
    switch drivers for this particular application.Thanks. No, there is no known issue, and if you put a packet sniffer
    between the client and DBMS, you will probably not see any appreciable
    difference in the content of the SQL sent be either driver. My suspicion is
    that it involves the historical backward compatibility built in to the DBMS.
    It must still handle several iterations of older applications, speaking obsolete
    versions of the DBMS protocol, and expecting different DBMS behavior!
    Our driver presents itself as a SQL7-level application, and may well be treated
    differently than a newer one. This may include different query processing.
    Because our driver is deprecated, it is unlikely that it will be changed in
    future. We will certainly support you using the MS driver, and if you look
    in the MS JDBC newsgroup, you'll see more answers from BEA folks than
    from MS people!
    Joe
    >
    >
    Mike
    The next test you should do, to isolate the issue, is to try another
    JDBC driver.
    MS provides a type-4 driver now, for free. If it is significantly faster,
    it would be
    interesting. However, it would still not isolate the problem, because
    we still would
    need to know what query plan is created by the DBMS, and why.
    Joe Weinstein at BEA
    PS: I can only tell you that our driver has not changed in it's semantic
    function.
    It essentially send SQL to the DBMS. It doesn't alter it.

  • OBIEE 11g performance problem

    Hi,
    I am facing a performance problem in OBIEE 11g. When I run the query taking from nqquery.log in database, it is giving me the result within few seconds. But In the OBIEE Answers the query runs forever not showing any data.
    Attaching the query below.
    Please help to solve.
    Thanks
    Titas
    [2012-10-16T18:07:34.000+00:00] [OracleBIServerComponent] [TRACE:2] [USER-23] [] [ecid: 3a39339b45a46ab4:-70b1919f:13a1f282668:-8000-00000000000769b2] [tid: 44475940] [requestid: 26e1001e] [sessionid: 26e10000] [username: weblogic] -------------------- General Query Info: [[
    Repository: Star, Subject Area: BM_BG Pascua Lama, Presentation: BG PL Project Analysis
    [2012-10-16T18:07:34.000+00:00] [OracleBIServerComponent] [TRACE:2] [USER-18] [] [ecid: 3a39339b45a46ab4:-70b1919f:13a1f282668:-8000-00000000000769b2] [tid: 44475940] [requestid: 26e1001e] [sessionid: 26e10000] [username: weblogic] -------------------- Sending query to database named XXBG Pascua Lama (id: <<26911>>), connection pool named Connection Pool, logical request hash e3feca59, physical request hash 5ab00db6: [[
    WITH
    SAWITH0 AS (select sum(T6051.COST_AMT_PROJ_RATE) as c1,
    sum(T6051.COST_AMOUNT) as c2,
    T6051.AFE_NUMBER as c3,
    T6051.BUDGET_OWNER as c4,
    T6051.COMMENTS as c5,
    T6051.COMMODITY as c6,
    T6051.COST_PERIOD as c7,
    T6051.COST_SOURCE as c8,
    T6051.COST_TYPE as c9,
    T6051.DATA_SEL as c10,
    T6051.FACILITY as c11,
    T6051.HISTORICAL as c12,
    T6051.OPERATING_UNIT as c13,
    T5633.project_number as c14,
    T5637.task_number as c15
    from
    (SELECT project_id proj_id
    ,segment1 project_number
    ,org_id
    FROM pa.pa_projects_all
    WHERE org_id IN (825, 865, 962, 2161)) T5633,
    (SELECT project_id proj_id
    ,task_id
    ,task_number
    ,task_name
    FROM pa.pa_tasks) T5637,
    (SELECT xxbg_pl_proj_analysis_cost_v.AFE_NUMBER,
    xxbg_pl_proj_analysis_cost_v.BUDGET_OWNER,
    xxbg_pl_proj_analysis_cost_v.COMMENTS,
    xxbg_pl_proj_analysis_cost_v.COMMODITY,
    xxbg_pl_proj_analysis_cost_v.COST_PERIOD,
    xxbg_pl_proj_analysis_cost_v.COST_SOURCE,
    xxbg_pl_proj_analysis_cost_v.COST_TYPE,
    xxbg_pl_proj_analysis_cost_v.FACILITY,
    xxbg_pl_proj_analysis_cost_v.HISTORICAL,
    xxbg_pl_proj_analysis_cost_v.PO_NUMBER_COST_CONTROL,
    xxbg_pl_proj_analysis_cost_v.PREVIOUS_PROJECT,
    xxbg_pl_proj_analysis_cost_v.PREV_AFE_NUMBER,
    xxbg_pl_proj_analysis_cost_v.PREV_COST_CONTROL_ACC_CODE,
    xxbg_pl_proj_analysis_cost_v.PREV_COST_TYPE,
    xxbg_pl_proj_analysis_cost_v.PROJECT_NUMBER,
    xxbg_pl_proj_analysis_cost_v.SUPPLIER_NAME,
    xxbg_pl_proj_analysis_cost_v.TASK_DESCRIPTION,
    xxbg_pl_proj_analysis_cost_v.TASK_NUMBER,
    xxbg_pl_proj_analysis_cost_v.TRANSACTION_NUMBER,
    xxbg_pl_proj_analysis_cost_v.WORK_PACKAGE,
    xxbg_pl_proj_analysis_cost_v.WP_OWNER,
    xxbg_pl_proj_analysis_cost_v.OPERATING_UNIT,
    xxbg_pl_proj_analysis_cost_v.DATA_SEL,
    pa_periods_all.PERIOD_NAME,
    xxbg_pl_proj_analysis_cost_v.ORG_ID,
    xxbg_pl_proj_analysis_cost_v.COST_AMT_PROJ_RATE COST_AMT_PROJ_RATE,
    xxbg_pl_proj_analysis_cost_v.COST_AMOUNT COST_AMOUNT,
    xxbg_pl_proj_analysis_cost_v.project_id,
    xxbg_pl_proj_analysis_cost_v.task_id
    FROM (select xpac.*,
    decode(xpac.historical, 'Y', 'Historical', 'N', 'Current') data_sel
    from apps.xxbg_pl_proj_analysis_cost_v xpac
    union
    select xpac.*, 'All' data_sel
    from apps.xxbg_pl_proj_analysis_cost_v xpac) xxbg_pl_proj_analysis_cost_v,
    (select period_name, org_id from apps.pa_periods_all) pa_periods_all
    WHERE ((xxbg_pl_proj_analysis_cost_v.ORG_ID = pa_periods_all.ORG_ID))
    AND (xxbg_pl_proj_analysis_cost_v.ORG_ID IN (825,865,962,2161))
    AND (APPS.XXBG_PL_PA_COMMITMENT_PKG.GET_LAST_DAY(xxbg_pl_proj_analysis_cost_v.COST_PERIOD) <=
    APPS.XXBG_PL_PA_COMMITMENT_PKG.GET_LAST_DAY(pa_periods_all.PERIOD_NAME))) T6051
    where ( T5633.proj_id = T5637.proj_id and T5633.project_number = 'SUDPALAPAS11' and T5637.proj_id = T6051.PROJECT_ID and T5637.task_id = T6051.TASK_ID and T5637.task_number = '2100.2000.01.BC0100' and T6051.DATA_SEL = 'All' and T6051.OPERATING_UNIT = 'Compañía Minera Nevada SpA' and T6051.PERIOD_NAME = 'JUL-12' )
    group by T5633.project_number, T5637.task_number, T6051.AFE_NUMBER, T6051.BUDGET_OWNER, T6051.COMMENTS, T6051.COMMODITY, T6051.COST_PERIOD, T6051.COST_SOURCE, T6051.COST_TYPE, T6051.DATA_SEL, T6051.FACILITY, T6051.HISTORICAL, T6051.OPERATING_UNIT)
    select D1.c1 as c1, D1.c2 as c2, D1.c3 as c3, D1.c4 as c4, D1.c5 as c5, D1.c6 as c6, D1.c7 as c7, D1.c8 as c8, D1.c9 as c9, D1.c10 as c10, D1.c11 as c11, D1.c12 as c12, D1.c13 as c13, D1.c14 as c14, D1.c15 as c15, D1.c16 as c16 from ( select distinct 0 as c1,
    D1.c3 as c2,
    D1.c4 as c3,
    D1.c5 as c4,
    D1.c6 as c5,
    D1.c7 as c6,
    D1.c8 as c7,
    D1.c9 as c8,
    D1.c10 as c9,
    D1.c11 as c10,
    D1.c12 as c11,
    D1.c13 as c12,
    D1.c14 as c13,
    D1.c15 as c14,
    D1.c2 as c15,
    D1.c1 as c16
    from
    SAWITH0 D1
    order by c13, c14, c2, c3, c4, c5, c6, c7, c8, c9, c10, c11, c12 ) D1 where rownum <= 65001

    Hi Titas,
    with such problems typically, at least for me, the cause turns out to be something simple and embarrassing like:
    - I am connected to another database,
    - The database is right but I have made some manual adjustments without committing them,
    - I have got the wrong query from the query log,
    - I have got the right query but my request is based on multiple queries.
    Do other OBIEE reports work fine?
    Have you tried removing columns one by one to see whether it makes a difference?
    -JR

  • Performance Problem on ODS Activate

    Hello,
    I've got a performance problem when I activate an ODS.
    In the ODS Activation log, I can see that there is a very long time between the end of the calcul of statistics and the next Line. Log example :
    14:42:03 Job lancé
    ..."SQL Request for calcul of statistics"
    14:42:07 SQL-END: 11.08.2005 14:42:07 00:00:10  
    16:29:53 SIDs determined successfully for request...
    Is there someone that can tell me what does SAP do during that 1h47min ?
    How can I Optimize ?
    Thanks

    Hi,
    I'm cheking ODS setting that have "Bex Reports" selected to verify if it is really necessary.
    Yesterday, SAP Kernel has been upgraded in 640 (advice from GoingLive for Better Stats), and I made a reboot of the unix sun server, SAP BW host, to take in account new OS settings (shmmax *2).
    During the night, BW has generated SID's in 10 minutes instead of nearly 2 hours.
    I hope it will be the same next night.
    Ravi talks about Active Data Table. How can I check it ? rsrv ?
    Pascal

  • I have a question about weblogic RMI , how can I resolve it.Thank you

    I have a question about the weblogic RMI .
    I have a program.web services+weblogic RMI +Data Sources When I run the program in the console application.it is ok.But When i run it with the web services(it 'is mean Get some parameter and run the different program).it's fail.The Exception is
    cannot assign instance of yype weblogic.rmi.RMIServices_1033_WLStub to field demo.RMIServer_1033_WLStub.stubinfo of type weblogic.rmi.internal.StubInfo in instance of demo.RMIEsrver_1033_WLStub
    how to resolve .Thank you.

    Hi Charles,
    Parental Controls has always had problems with https sites, no idea if it's fixed in 10.9.x or not.
    When you setup your Mac it shouldv'e made an admin account, are you not running from that account, or did you somehow change it to a Managed account???

  • Weblogic 8.1.6 problem.......

    Hi All,
    i am facing a strange problem, when i start the weblogic server after starting successfully it throws an exception :-
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Socket> <BEA-000440> <Native IO Enabled.>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "admin_svr" for doma
    in "charter" running in Development Mode>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 16
    818, ip address *.*>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <WebLogicServer> <BEA-000213> <Adding address: 10.55.13.58 to licensed client list>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to
    the repository.>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has
    been backed up at /home/chrtr18/domains/charter/./config.xml.booted.>
    <1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] FileServlet: init>
    <1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] FileServlet: Using standard I/O>
    <1-Nov-2007 3:12:22 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] actions: init>
    <1-Nov-2007 3:13:24 o'clock AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal
    .BasicServerRef@109 - hostID: '8499232654163808380S:10.55.13.31:[16818,16818,-1,-1,-1,-1,-1,0,0]:charter:admin_svr', oid: '265
    ', implementation: 'weblogic.jms.dispatcher.DispatcherImpl@e5f0d2'
    java.lang.SecurityException: [Security:090398]Invalid Subject: system.
    java.lang.SecurityException: [Security:090398]Invalid Subject: system
    at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:698)
    at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:205)
    at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:841)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:307)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1114)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1032)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:225)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:809)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:782)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:718)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:664)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    Is i am missing something...any suggestion will help...
    Thanks.

    Hi All,
    i am facing a strange problem, when i start the weblogic server after starting successfully it throws an exception :-
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Socket> <BEA-000440> <Native IO Enabled.>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "admin_svr" for doma
    in "charter" running in Development Mode>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 16
    818, ip address *.*>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <WebLogicServer> <BEA-000213> <Adding address: 10.55.13.58 to licensed client list>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to
    the repository.>
    <1-Nov-2007 3:10:23 o'clock AM EDT> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has
    been backed up at /home/chrtr18/domains/charter/./config.xml.booted.>
    <1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] FileServlet: init>
    <1-Nov-2007 3:12:04 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] FileServlet: Using standard I/O>
    <1-Nov-2007 3:12:22 o'clock AM EDT> <Info> <HTTP> <BEA-101047> <[ServletContext(id=24067799,name=console,context-path=/console
    )] actions: init>
    <1-Nov-2007 3:13:24 o'clock AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal
    .BasicServerRef@109 - hostID: '8499232654163808380S:10.55.13.31:[16818,16818,-1,-1,-1,-1,-1,0,0]:charter:admin_svr', oid: '265
    ', implementation: 'weblogic.jms.dispatcher.DispatcherImpl@e5f0d2'
    java.lang.SecurityException: [Security:090398]Invalid Subject: system.
    java.lang.SecurityException: [Security:090398]Invalid Subject: system
    at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:698)
    at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:205)
    at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:841)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:307)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1114)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1032)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:225)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:809)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:782)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:718)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:664)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    Is i am missing something...any suggestion will help...
    Thanks.

  • Java.lang.NoSuchMethodError: weblogic.rmi.extensions.WRMIOutputStream

    Hi,
    I'm trying to run examples.jdbc.datasource.simplesql with Weblogic 5.1sp8,
    but am hitting this problem when it executes:
    An exception was caught. javax.naming.NamingException [Root exception is
    weblogic.rmi.ServerError: A Rem
    oteException occurred in the server method
    - with nested exception:
    [java.lang.NoSuchMethodError: weblogic.rmi.extensions.WRMIOutputStream:
    method writeObject(Ljava/lang/Ob
    ject;)V not found]]
    An exception was caught. java.lang.NullPointerException:
    Any pointers would be appreciated.
    Thanks,
    -Triet

    Hi..
    I guess itzz more of the service pack problems.
    Jars built on the later version won't work in the previous version (service packs) of weblogic.
    Try building a jar on the oldest version (service pack) u have and then try deploying it to the later version , i think it won't give u any problems.
    Try it out and let me know if u face any problems

  • Weblogic.rmi.internal.LocalServerRefMissing

    I am Attempting to serialize and deserialize a stateful session
    bean. The deserialization seems to be the problem. I have
    figured out that the line throwing the error is the "readObject"
    line.
    A similar problem was reported on Jan 31 2002, but the solution
    suggested deals with the "getEJBObject" line. I have tryed to
    implement this solution, as you can see below, but since the
    error I am getting is thrown before getting to that line, it
    makes no difference.
    The Exception I am getting is an "InvalidClassException".
    The message reads as follows = "weblogic.rmi.internal.
    LocalServerRefMissing no-arg constructor for class".
    As far as the "no-arg constructor" error goes, as I understand
    it I should not be having that problem. My Session bean
    implements the SessionBean interface and does not explicitly
    extend anything, so by default it extends Object, right?!
    Object has a no-args constructor, so there should be no problem.
    My code is as follows:
    ---SERIALIZATION---
    Handle msaHandle = contributions.getHandle();
    ObjectOutputStream toFile = new ObjectOutputStream(
    new FileOutputStream(handleFile));
    toFile.writeObject(msaHandle);
    toFile.close();
    ---DESERIALIZATION---
    ObjectInputStream fromFile = new ObjectInputStream(
    new FileInputStream(handleFile));
    Handle msaHandle = (Handle) fromFile.readObject();
    //MsaSession contributions =
    (MsaSession) msaHandle.getEJBObject();
    MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
    Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
    fromFile.close();
    I have tried to print "classname" (available in the
    InvalidClassException class), but only get null as the value.
    Anyone have any ideas?
    Matthew

    I am Attempting to serialize and deserialize a stateful session
    bean. The deserialization seems to be the problem. I have
    figured out that the line throwing the error is the "readObject"
    line.
    A similar problem was reported on Jan 31 2002, but the solution
    suggested deals with the "getEJBObject" line. I have tryed to
    implement this solution, as you can see below, but since the
    error I am getting is thrown before getting to that line, it
    makes no difference.
    The Exception I am getting is an "InvalidClassException".
    The message reads as follows = "weblogic.rmi.internal.
    LocalServerRefMissing no-arg constructor for class".
    As far as the "no-arg constructor" error goes, as I understand
    it I should not be having that problem. My Session bean
    implements the SessionBean interface and does not explicitly
    extend anything, so by default it extends Object, right?!
    Object has a no-args constructor, so there should be no problem.
    My code is as follows:
    ---SERIALIZATION---
    Handle msaHandle = contributions.getHandle();
    ObjectOutputStream toFile = new ObjectOutputStream(
    new FileOutputStream(handleFile));
    toFile.writeObject(msaHandle);
    toFile.close();
    ---DESERIALIZATION---
    ObjectInputStream fromFile = new ObjectInputStream(
    new FileInputStream(handleFile));
    Handle msaHandle = (Handle) fromFile.readObject();
    //MsaSession contributions =
    (MsaSession) msaHandle.getEJBObject();
    MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
    Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
    fromFile.close();
    I have tried to print "classname" (available in the
    InvalidClassException class), but only get null as the value.
    Anyone have any ideas?
    Matthew

  • Java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.inte

    Hi,
    I am trying to deploy ejb3.0 on weblogic 10 server. I am able to find the JNDI name of the stateless session bean correctly, but getting an exception while narrowing it down. My ejb3.0 client is a standalone java client. I am trying to access the stateless session ejb3.0 bean.Please help me. i have been trying it for many days.
    thanks in advance,
    Sanjeev
    [sanpraka@localhost certEjb]$ java -cp ./:/usr/weblogic/bea/wlserver_10.0/server/lib/weblogic.jar:/usr/weblogic/bea/wlserver_10.0/server/lib/wlclient.jar com.titan.clients.Client
    Object is weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null'
    java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null' to com.titan.travelagent.TravelAgentRemote
    at weblogic.corba.server.naming.ReferenceHelperImpl.narrow(ReferenceHelperImpl.java:206)
    at weblogic.rmi.extensions.PortableRemoteObject.narrow(PortableRemoteObject.java:88)
    at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteObjectDelegateImpl.java:32)
    at javax.rmi.PortableRemoteObject.narrow(Unknown Source)
    at com.titan.clients.Client.main(Client.java:24)
    [sanpraka@localhost certEjb]$

    We have a similar problem. We have a web application (on server A) that invokes an EJB on a remote server (server B). This works fine, until we deploy another web application to server A at which point the existing web application starts to throw java.lang.ClassCastException when narrowing the remote EJB interface. The exception starts to be thrown at the moment the latter web application is deployed - start is not required.
    The latter web application contains (actually in APP-INF/lib) the old version of the EJB remote interface, that somehow gets to be loaded into the classpath of the existing web application. The solution is to delete the old version of the EJB remote interface from APP-INF/lib of the latter web application (we didn't need it anyway), but it would be interesting to know in which circumstances classes can get mixed between enterprise applications.
    I failed to reproduce the error in simple scenario, so this does not happen always.

  • Weblogic RMI error

    Dear all,
    I am using weblogic rmi. When I run the client, the following error
    appeared:
    java.rmi.UnmarshalException: failed to unmarshal class
    java.lang.Object; nested
    exception is:
    java.lang.ClassNotFoundException: Hello_WLStub
    --------------- nested within: ------------------
    weblogic.rmi.MarshalException: Remapped jndi exception
    - with nested exception:
    [java.rmi.UnmarshalException: failed to unmarshal class
    java.lang.Object; nested
    exception is:
            java.lang.ClassNotFoundException: Hello_WLStub]
    at weblogic.rmi.Naming.toWeblogicRmiException(Naming.java:289)
    at weblogic.rmi.Naming.lookup(Naming.java:78)
    at HelloClient.main(HelloClient.java:40)
    Server and client are 2 separate machine.However, when I copy
    Hello_WLStub.class to the client machine, it runs without problem.
    When weblogic do not download the stub class to client instead?
    Moreover, I found that all my startup classes must be placed inside
    E:\bea\wlserver6.0, otherwise those startup classes will not work. How
    to change this default location?Thanks!

    Dear all,
    I am using weblogic rmi. When I run the client, the following error
    appeared:
    java.rmi.UnmarshalException: failed to unmarshal class
    java.lang.Object; nested
    exception is:
    java.lang.ClassNotFoundException: Hello_WLStub
    --------------- nested within: ------------------
    weblogic.rmi.MarshalException: Remapped jndi exception
    - with nested exception:
    [java.rmi.UnmarshalException: failed to unmarshal class
    java.lang.Object; nested
    exception is:
            java.lang.ClassNotFoundException: Hello_WLStub]
    at weblogic.rmi.Naming.toWeblogicRmiException(Naming.java:289)
    at weblogic.rmi.Naming.lookup(Naming.java:78)
    at HelloClient.main(HelloClient.java:40)
    Server and client are 2 separate machine.However, when I copy
    Hello_WLStub.class to the client machine, it runs without problem.
    When weblogic do not download the stub class to client instead?
    Moreover, I found that all my startup classes must be placed inside
    E:\bea\wlserver6.0, otherwise those startup classes will not work. How
    to change this default location?Thanks!

Maybe you are looking for