BO XI3.1 SP3 to SP6.3 Upgrade

Hi,
We have BOXI3.1 SP3 FP3.1 with Oracle Application Server on Solaris.
We have planned to upgrade to FP6.3 and the path will be SP4 + SP6 + FP6.3.
Also in SP6 OAS is not supported, so we will use weblogic server.
Could you please suggest the sequence of action that I will be following.
Below steps I am thinking not sure if they are correct or is there any short steps.
Stop all services except CMS
Apply SP4
<what actions needed ? Do I need to deploy war files and start BO and keep only CMS up?>
Apply SP6 <Do I need to take any special care here ? CMS database is in Oracle 11gR2>
<Do I need to deploy in weblogic ?><What else I need to take care ?>
Apply FP6.3
Generate war files and deploy
<Any other thing I need to take care>
<Any special consideration for weblogic>
currently the server java is 1.5. Do I need to upgrade the server jav ? If yes then at what stage of upgrade ?
It will be great help if you advise me on this.
Regards,
Amaresh

Hello,
first of all, are you aware that already SP7 is available for XI 3.1?! If you need to update anyhow you should consider update to SP7.
I would procced as follows (My assumption is that XI 3.1 is on the same Host as the OAS and WebLogic):
1. Stop all Services
2. Make a Backup of the CMS DB and the FRS
3. Start only CMS, IFRS and OFRS
4. Update to SP4
5. Update to SP6
6. Update to SP6 Fix Pack 3
7. Configure the WebLogic to JDK 7 (JDK 6 is out of support by Oracle)
8. Re- deploy Web Applications
9. Start everything
Regards
-Seb.

Similar Messages

  • Error inside TicketCreator (EP5.0 SP5 to SP6 upgrade)

    Is there anyone having this experience before?  Our original portal is EP5.0 SP5, with 1 lockserver box, 2 portal server box. within these portal server boxes, 1 with installation type  as "primary" and one as "clustered."
    The upgrade from original EP 5.0 SP5 to SP6 is perfectly fine for lockserver and "primary" portal.  However, for clustered node, after I have applied EP5.0 SP5 to SP6 upgrade kit, a launch of portal got an error message as "Error inside TicketCreator Failed to create SSO cookie. The cookie returned from the cookie creation URL returned an empty value."
    Any tips to this?  anyone have encountered this before and how to get it around, thks
    Stephen
    Message was edited by: Lee Stephen
    Message was edited by: Lee Stephen

    Hi,
    this is my first post in SDN.
    I installed EP5SP6 and got the same error message "Error inside TicketCreator Failed to create SSO cookie. The cookie returned from the cookie creation URL returned an empty value.".
    I found out that the error comes from the function "CreateTicket(userName)" in the file "TicketCreator.asp" in folder "\inetpub\wwwroot\SAPPortal\Common" (this function is called from "Default.asp" when no "MYSAPSSO2"-Cookie was found); it uses the "SAP J2EE Engine 6.20" in order to create a new cookie (in my case for "userName = admin") by calling the following URL:
    http://localhost:8100/irj/servlet/prt/prtroot/InitialLogonSupport.default?IntegrityToken=&URL=
    The response header from this URL is the following (Status = 200 => OK):
    <i>Server: SAP J2EE Engine/6.20
    Content-Type: text/html
    Content-Length: 631
    Date: Thu, 20 Apr 2006 13:04:56 GMT</i>
    The mentioned error occurs because there is no entry in the header with "Set-Cookie: MYSAPSSO2...".
    I also found out that the "MSXML4.DLL" is used for calling the above URL, so I modified the function
    "CreateTicket(...)" and inserted the following:
    if req.status = 200 then
    >>> INSERT
    CreateTicket = req.responseText
    exit function
    >>> INSERT
    Note: the function "responseText(...)" is defined in the interface "IXMLHTTPRequest" which is implemented in "MSXML4.dll"; you can find out other functions using a "TypeLib viewer".
    When I now call the portal again I see a Java runtime exception:
    java.lang.StringIndexOutOfBoundsException: String index out of range: 14
    Now I realised that something in the URL must be missing; the source for creating the URL looks like that:
    url = url & "/irj/servlet/prt/prtroot/InitialLogonSupport.default?IntegrityToken=" & timeStamp & "&URL="
    The generated URL (see above) shows that the "timeStamp" must be empty, so the following code must fail:
    timeStamp = Server.URLEncode(encoder.TimeStamp(userName))
    The "encoder" is an instance of the object "HyRelEncoder":
    set encoder = Application("Locator").NamedComponent("HyRelEncoder")
    Now I'm at the end because I can't find any further information about the "HyRelEncoder" object. Maybe someone can find out more and help me to solve this problem,
    Oliver

  • CRM 7.0 upgrade from SP3 to SP6

    Hi gurus,
    we have a live CRM system 7.0 SP3 and we would like to upgrade to SP6.
    The system is quite customized especially in the User Interface. Moreover some modification to the standard code has been made here and there.
    My feeling is that it could be quite a huge task to do.
    Has anybody experience with that? Is there any SAP reliable tool that could help me understand roughly the size of collitions?
    It seems the tools that works for ABA and BASIS do not work for CRM.
    Any feedback is appreciated.
    C

    Hi,
    We have been patching our CRM 7.0 system to SP6 and have almost finishedbut have hit a problem patching the BBPCRM component. Right at the very
    end, several wizards and screens have popped up and each step has been
    confirmed and moved on until we reach one which says "Resolve conflicting
    versions of BDoc types.
    At least all changed BDoc types require conflict resolution.
    To do this, click on Execute to call the BDoc Modeler.
    BDoc types that have conflicting versions are marked accordingly.
    For further information, select Help -> Application Help.
    When I click on execute, I get the following pop up error message:-
    The customizing settings in this client is different from other clients.
    and it won't let us continue any further. This is now holing up the
    patching of the rest of our landscape, so any help in resolving this
    would be gratefully received.
    Thanks in advance,

  • Problem since SP6 upgrade

    Hello there,
    I am fairly confident this is not the correct forum, but then which one. Here goes.
    Since the update, NW OES 6.5 sp6, I continually get java "out of Memory" errors after about 5 minutes of people going into virtual office. The only things on this server are File, print (Broker and manager), iManager, Novel Storage Manager, Antivirus, DHCP/DNS. It is a Dual 3.8 Gig (with virtual processor off) and 4 GIG of RAM
    Any ideas or tweaks? I can not get into iManager to configure anything unless VO is not turned on. I took away the link from people because I do not know how to turn it off. :)
    Tom

    Hi,
    Treat the following:
    review tcadmup.ncf (sys:/system) and verify that the line exist:
    setenv CATALINA_OPTS=-vm160m -Xmx512m -Djavax.net.ssl.trustStore=sys:/adminsrv/conf/.keystore -Dsun.io.useCanonCaches=false
    the same for tomcat4.ncf
    Tell me that happen....
    WEB_on
    "Tom Hafemann" <[email protected]> escribi en el mensaje news:457517F9.3DEF.0061.0@nonspamtbmidwesttechnolo gies.com...
    Without the XMS statement, the server goes out of memory in about 5 minutes. With it, it takes abou
    t 15 minutes.
    Tom
    >>> WEB_on<[email protected]> 12/1/2006 9:28 AM >>>
    Yes. It already tried without Xms256m.
    "Tom Hafemann" <[email protected]> escribi en el mensaje news:[email protected]...
    are you asking me to take out the Xms256m?
    >>> WEB_on<[email protected]> 12/1/2006 8:53 AM >>>
    You already proved with this (without Xmx256m) ?
    setenv CATALINA_OPTS=-vm160m -Xmx512m -Djavax.net.ssl.trustStore=sys:/adminsrv/conf/.keystore -Dsun.io.useCanonCaches=false
    "Tom Hafemann" <[email protected]> escribi en el mensaje news:[email protected]...
    setenv CATALINA_OPTS=-vm160m -Xms256m -Xmx512m -Djavax.net.ssl.trustStore=sys:/adminsrv/conf/.keystore -Dsun.io.useCanonCaches=false
    Already did that-one of the first things. :(
    Tom
    >>> WEB_on<[email protected]> 11/30/2006 3:51 PM >>>
    see:
    http://www.novell.com/documentation/...e.html#b75prct
    2.10 Java Out-of-Memory Issue
    To avoid Java out-of-memory issues with Virtual Office and iManager, you can increase the memory allocated by editing the sys:\tomcat\4\tomcat4.ncf and increase the -Xmx256m setting up to -Xmx512. Then restart Tomcat.
    "Tom Hafemann" <[email protected]> escribi en el mensaje news:4566CAB6.3DEF.0061.0@nonspamtbmidwesttechnolo gies.com...
    Hello there,
    I am fairly confident this is not the correct forum, but then which one. Here goes.
    Since the update, NW OES 6.5 sp6, I continually get java "out of Memory" errors after about 5 minutes of people going into virtual office. The only things on this server are File, print (Broker and manager), iManager, Novel Storage Manager, Antivirus, DHCP/DNS. It is a Dual 3.8 Gig (with virtual processor off) and 4 GIG of RAM
    Any ideas or tweaks? I can not get into iManager to configure anything unless VO is not turned on. I took away the link from people because I do not know how to turn it off. :)
    Tom

  • Missing CRT - for Enhancement Pack 6 SP6 Upgrade

    performing an upgrade on on the config phase of the prepare i get an error due to a missing CRT file -
    2EETN388 The following CRTs of the Add-On "FI-CAX" rel."604" must be included as well:
    3WETN389 CRT &4"SAPK-60406INFICAX" for Support Package &1"SAPKH60406" of software component &2"SAP_APPL" rel.&3"604"
    checked in the market place for the missing CRT file but cant find it
    can anyone help ?

    Hi my friend
    I think EHPI means you need to include SAPK-60406INFICAX in the same queue with SAPKH60406.
    Regards,

  • Upgrade BOXIR2 to BO XI3.1

    Hi,
    I have BO XIR2 running on one system and I want to upgrade the version to XI3.1 SP2 FP2.7. I do not want to perform a separate installation. Is it possible to upgrade the version and also the contents without a separate installation? If yes, is there any documentation available which can guide step by step?
    Many Thanks

    Just a clarification,
    XI 3.1 does in fact have an upgrade option for XIR2 (I have had to repair 2 systems after customers attempted this myself) It is not the safest option (as it deletes your XIR2 and copies the CMS DB to the current data source nby default) and using a 2nd server is recommended in most cases but the upgrade is available. If using XI 3.1 to upgrade then you will have to patch to SP2 and FP 2.7 seperately after the upgrade rather than before. You have to [login to SMP to access this link |https://websmp102.sap-ag.de/~sapidb/011000358700001646952008E/xi3-1_bip_upgrade_en.pdf]apparently
    Upgrading will also be available with integrated SP3 (estimated to be out in a week or so) which will hopefully be more reliable. You will always have more risk with an upgrade since attempting to do everything on 1 server and using any method please backup your CMS DB and FRS priorr to any attempts.
    On the int kit message is the SAP client installed on the server? SP2 for XI 3.1 requires a recent version of the SAP client. Also the jco muyst be installed
    Regards,
    Tim

  • Upgrade Exchange 2010 SP2 to SP3 getting fail

    Hi,
    I am trying to upgrade from exchange 2010 SP2 to SP3, but it getting failed.
    I have already run the prepare schema, prepare and domain prep in all domains and it got replicated in DR Domain controllers.
    But, still i am not able to upgrade the server. The error says,
    Preparing Exchange Setup
        Copying Setup Files                           COMPLETED
    The following server roles will be upgraded
    Languages
    Hub Transport Role
    Client Access Role
    Management Tools
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                 COMPLETED
        Organization Checks                                      
    FAILED
         Setup needs to contact the Active Directory schema master but this computer
     is not in the same Active Directory site as the schema master (Default-First-Si
    te-Name).
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have been created but have not yet replicat
    ed to the local domain.  Wait for replication to complete and then run setup aga
    in.
        Language Pack Checks                                     
    COMPLETED
        Hub Transport Role Checks                                 FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have been created but have not yet replicat
    ed to the local domain.  Wait for replication to complete and then run setup aga
    in.
        Client Access Role Checks                                 FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have been created but have not yet replicat
    ed to the local domain.  Wait for replication to complete and then run setup aga
    in.
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    Exchange Server setup encountered an error.
    Thanks,
    San

    Hi,
    Schema updates should be done on a schema master or on a DC in the same AD site as the schema master. Once extended, the updates will replicated via AD replication. To narrow down the issue, I recommend you check if there is any event related to replication
    on domain controller holding schema master role.
    Is the schema master role in the same site as the Exchange server which you want to upgrade? If not, you can try to transfer FSMO role to a domain controller which is in the site where you want to install Exchange 2010 SP3 and then upgrade to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Upgrading from 8.1 SP5 to 8.1.SP6

    Is there a patch to upgrade sp5 to sp6? I am only finding support for a fresh install to get to SP6.
    Thanks,
    Joe

    There is a SP6 upgrade installer
    Jin
    :-)

  • SunONE SP6 - admin console login failures

    Hi,
    I have just upgraded from SunONE 5.2 SP3 to SP6 running on Solaris 8. The upgrade appeared to go perfectly smoothly (i.e. no error messages) but now when I try to login to the admin server console with the old "admin" and associated password, it repeatedly gives me an error message saying "cannot login because of an incorrect userID, incorrect password, or directory problem".
    The documentation around the patch does not suggest that any passwords will get changed or that I need to do anything to the webserver that runs the console, although it appears to be this that is giving me a "401 unauthorized" error.
    I'd appreciate any help someone could give me as to why this error might be occurring ...
    Thanks,
    Darren

    Hi Darren,
    as far as I remember updating the Admin-Server will set the admin port to an random value, so it's worthful to check the admin-server.
    Anyway, please clarify:
    - is the DS it's own config-directory or does it use an remote one?
    - is it possible to log into the console using cn=directory manager?
    - is it possible to do ldapsearch using uid=admin, ... and the password you use on the admin gui?
    best regards
    Andre

  • I keep getting exact duplicate songs in playlists and libraries, how can you filter this out when upgrading these lists, or sync to the same device again? And how to do it without going through each and every P'list or Library ?

    I have Windows XP-Pro SP3, the latest upgrades of Three media players, iTunes being the default player. I keep getting duplicates in playlists, libraries etc., of the same version of song. Everytime i make a change or renew my media to device or SYNC it wants to add duplicates to the computer disk, lists etc. Can you filter out same copies without having to edit each and every song, which in my case is quite large. For instance if you want to convert all mpeg, or mp4-a files to AAC you will end up with duplicates of each file type. Or you sync to an ipod, the library adds to itself---- including copies of songs already in it, if in a different file version.

    Your refer to:
    " if you want to convert all mpeg, or mp4-a files to AAC "
    This will always duplicate files within iTunes.  I need to ask why you're doing this conversion - all formats are compatible with iTunes, and conversion between mp3 and AAC will always involve some loss of quality.

  • WebLogic 5.1 sp6 .. session in cluster not working properly

    It seems like there is a problem in Weblogic 5.1 with sessions in a
              clustered environment. The problem is immediately visible with sp3 but
              also appears in different form with sp6 . I discovered the problem is
              actually with session while testing the cluster with a Session servlet
              given with the Weblogic 5.1 kit.
              I regiestered the servlet as servlet/session.
              The environment is briefly as follows:
              Solaris 2.6
              Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              machine with two multihome addreses like home1:7001 and home2:7001
              Cluster properties in mycluster/weblogic.properties are set as,
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              and also started with required cluster properties in startup.
              iPlanet 4.0 webserver - obj.conf has entries like
              WebLogicCluster="home1:7001,home2:7001"
              All requests are made as http://<host>/servlet/session
              sp3 ) After both members are booted up, the first call to session
              servlet from any new browser session throws a NullException in server,
              but subsequent calls work fine. Single server works fine.
              After looking at sp6 release notes it appeared to me that it was a known
              problem with cluster.
              sp6 ) After both members are booted up, all calls to session servlet do
              not complete and eventually it times out. Other servlets work fine.
              It only works if we do these steps,
              - one of the member is booted up and then session servlet is called and
              response comes back.
              - second member is booted up and it works well if session servlet is
              called. Subsequent requests to both members work fine.
              Another strange behaviour:
              While running a snoop servlet in cluster subsequent requests show,
              Requested url :
              either http://<host>/servlet/snoop
              or http://<host>:7001/servlet/snoop alternatively
              which is strange.
              

    You are not using the same service pack on both the servers. let try do that and see how it goes.
              1. Also, if you are doing testing why do you so many threads.
              2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
              - Prasad
              Sutanu Ghosh wrote:
              > Here are the thread dumps from both members of the cluster. I took the dumps
              > about 5 times in 10 secs interval. It will be helpful for us if you can give
              > some insight about this problem.
              > Also about the snoop servlet, can you explain why the requested url is
              > different (one with weblogic port another without it) in every alternate
              > requests ?
              > thanks
              >
              > Prasad Peddada wrote:
              >
              > > Sutanu Ghosh wrote:
              > >
              > > > It seems like there is a problem in Weblogic 5.1 with sessions in a
              > > > clustered environment. The problem is immediately visible with sp3 but
              > > > also appears in different form with sp6 . I discovered the problem is
              > > > actually with session while testing the cluster with a Session servlet
              > > > given with the Weblogic 5.1 kit.
              > > > I regiestered the servlet as servlet/session.
              > > >
              > > > The environment is briefly as follows:
              > > > Solaris 2.6
              > > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              > > > machine with two multihome addreses like home1:7001 and home2:7001
              > > > Cluster properties in mycluster/weblogic.properties are set as,
              > > > weblogic.httpd.clustering.enable=true
              > > > weblogic.httpd.session.enable=true
              > > > weblogic.httpd.session.persistence=true
              > > > weblogic.httpd.session.persistentStoreType=replicated
              > > > and also started with required cluster properties in startup.
              > > >
              > > > iPlanet 4.0 webserver - obj.conf has entries like
              > > > WebLogicCluster="home1:7001,home2:7001"
              > > >
              > > > All requests are made as http://<host>/servlet/session
              > > >
              > > > sp3 ) After both members are booted up, the first call to session
              > > > servlet from any new browser session throws a NullException in server,
              > > > but subsequent calls work fine. Single server works fine.
              > > > After looking at sp6 release notes it appeared to me that it was a known
              > > > problem with cluster.
              > > >
              > > > sp6 ) After both members are booted up, all calls to session servlet do
              > > > not complete and eventually it times out. Other servlets work fine.
              > > > It only works if we do these steps,
              > >
              > > Take thread dumps in intervals of 10 seconds and post them again.
              > >
              > > > - one of the member is booted up and then session servlet is called and
              > > > response comes back.
              > > > - second member is booted up and it works well if session servlet is
              > > > called. Subsequent requests to both members work fine.
              > > >
              > > > Another strange behaviour:
              > > > While running a snoop servlet in cluster subsequent requests show,
              > > > Requested url :
              > > > either http://<host>/servlet/snoop
              > > > or http://<host>:7001/servlet/snoop alternatively
              > > > which is strange.
              >
              > ------------------------------------------------------------------------
              > SIGQUIT
              > A SIGQUIT has been received. Do you want to:
              > [ 0 ] continue program
              > [ 1 ] check & print one deadlock
              > [ 2 ] check & print all deadlocks
              > [ 3 ] dump thread stacks
              > [ 4 ] dump lock registry
              > [ 5 ] heap inspection
              > [ 6 ] terminate program
              > Type number corresponding to selected action: Found 0 deadlock
              >
              > Full thread dump:
              > "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
              >
              > [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
              > [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
              > [3] java.lang.Thread.run(Thread.java:479)
              > -------------------
              > "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:224)
              > [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
              > [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
              > [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:223)
              > [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
              > [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
              > [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
              > [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
              > [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
              > [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
              > [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
              > [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
              > [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
              > [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
              > [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
              > [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
              > [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
              > [9] weblogic.jndi.Environment.getContext(Environment.java:122)
              > [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
              > [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
              > [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
              > [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
              > [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
              > [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
              > [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
              > [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
              > [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
              > [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
              > [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              > [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
              > [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
              > [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
              > [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              > [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
              > [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
              > [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.ke

  • Exchange 2010 SP3 UR9 OWA users cannot open mail items

    We recently had users reporting unable to open items in OWA.  Issue is confirmed across all CAS servers.
    Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
    3 AD Site DAG, multi-role servers
    So far we have done the following to troubleshoot:
    * Check security propagation for account permissions.
    * Check security on all virtual directories.
    * Check permissions on web.config
    * Re-run PrepareAD
    * Uninstall and reinstall CAS role
    Please review the errors below and let me know if you have any words of wisdom on this issue.  Thanks!
    Errors:
    Request
    Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
    User: user
    EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
    SMTP Address: [email protected]
    OWA version: 14.3.235.1
    Mailbox server: server.domain.com
    Exception
    Exception type: System.UriFormatException
    Exception message: Invalid URI: The format of the URI could not be determined.
    Call stack
    System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
    Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
    Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
    Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
    Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Request
    Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
    User: user
    EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
    SMTP Address: [email protected]
    OWA version: 14.3.235.1
    Mailbox server: server.domain.com
    Exception
    Exception type: System.UriFormatException
    Exception message: Invalid URI: The format of the URI could not be determined.
    Call stack
    System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
    Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
    Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Hi Noel,
    Base on my search, it may be due to IRM feature been enabled for OWA.
    I recommend you use the following command to check if the value of IRMEnabled parameter is true:
    Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
    If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Weblogic server 8.1 SP2 to SP6 ugrade

    Hello All
    Am looking for any document that would outline steps to upgrade weblogic 8.1 SP2 to SP6.
    Can we directly upgrade to SP6 ?
    Found the patch 9479129 BEA WebLogic Platform: Patchset WEBLOGIC PLATFORM 8.1 WITH SP6 UPGRADE INSTALLER but the readme doesnt have any instructions.
    Neither could i find in http://docs.oracle.com/cd/E13222_01/wls/docs81/index.html
    Any pointers in this regard would be helpful.
    Thanks
    Sundari

    WLS 8.1SP2 can not be upgraded directly to WLS8.1 SP6.
    The existing domain should be at WLS 8.1 SP4 atleast so that it can be upgraded to WLS 8.1 SP6.
    The link:
    http://commerce.bea.com/
    Has be decommissioned and now in order to download the upgrade installers and WLS service pack versions you should have a Support ID which is required to create a login to metalink.oracle.com .
    Then You can follow the following:
    Login to: https://Metalink.oracle.com
    Go to tab: Patches & Updates
    Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs
    Patch Bundles for Individual Products or Components
    Select BEA Weblogic Platform
    Select the WebLogic Main version and SP version
    Then you should see the download screen.
    Thanks,
    Sandeep

  • Weblogic 8.1 SP3 and Toplink

    I recently upgraded our weblogic server from 8.1sp2 to 8.1 SP3 . This upgrade requires an jdk142_04 as opposed to jdk141_05 . I have recompiled my whole application and deployed it . I find that my enity bean methods are not working any more . All Entity bean methods finder's and create's .
    Here is the stack trace .
    The actual Exception is : javax.transaction.TransactionRolledbackException: <b>EJB Exception: : java.lang.AbstractMethodError: </B>oracle.toplink.internal.ejb.cmp.wls.WlsBeanManager.remoteCreate (Lweblogic/ejb20/internal/InvocationWrapper;Ljava/lang/reflect/Method;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljavax/ejb/EJBObject;
    at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:246)
    at com.rhii.mjplus.fo.people.beans.People_z2e2a7_HomeImpl.create(People_z2e2a7_HomeImpl.java:356)
    at com.rhii.mjplus.fo.people.beans.PeopleManagerBean.setPeople(PeopleManagerBean.java:439)
    at com.rhii.mjplus.fo.people.beans.PeopleManager_ncwdjk_EOImpl.setPeople(PeopleManager_ncwdjk_EOImpl.java:162)
    at com.rhii.mjplus.fo.people.controller.People_FastSave_Servlet.doPost(People_FastSave_Ser
    Anyone has a clue as to where to look .
    Thanks

    Anybody here working with Toplink . I wonder if Toplink 9.0.4 is jdk1.4.2 compatible

  • Can't upgrade to AIR 2. Same old "administrator" error.

    On Windows XP SP3, attempting to upgrade from Pandora Player, Adobe AIR 1.5.3.9130 to 2.0.2.12610 I get this error.
    An error occurred while installing Adobe AIR. Installation may not be allowed by your administrator.
    I download the installer and try running directly with same results.
    I delete:
    c:\Documents and Settings\David\Local Settings\Application Data\Adobe\AIR\
    and remove related registry entries using CCleaner. [The recommended Windows Installer Cleanup Utility miscuu2.exe seems to no longer be available.] Same results. Here's the log.
    [2010-07-31:09:37:56] Performing runtime install
    [2010-07-31:09:37:56] UI SWF load is complete
    [2010-07-31:09:37:58] UI initialized
    [2010-07-31:09:37:58] starting user confirmation
    [2010-07-31:09:37:58] Version of this installer: 2.0.2.12610
    [2010-07-31:09:37:58] Installation type: new
    [2010-07-31:09:38:03] starting install
    [2010-07-31:09:38:03] Scheduling runtime installation operations
    [2010-07-31:09:38:03] Active AIR product GUID is {A2BCA9F1-566C-4805-97D1-7FDC93386723}
    [2010-07-31:09:38:03] Scheduling an MSI install operation
    [2010-07-31:09:38:03] Beginning runtime installation
    [2010-07-31:09:38:03] Beginning install
    [2010-07-31:09:38:03] Installing c:\docume~1\david\locals~1\temp\air68d.tmp\setup.msi
    [2010-07-31:09:38:03] Error occurred; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2010-07-31:09:38:03] Rolling back install of c:\docume~1\david\locals~1\temp\air68d.tmp\setup.msi
    [2010-07-31:09:38:03] Rollback due to error complete
    [2010-07-31:09:38:03] error during install: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2010-07-31:09:38:03] runtime install entering error state: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2010-07-31:09:38:07] begin quitting
      --David

    Can you retry the installation (user interface version), dismiss error and send me the AIR Install.log? ([email protected])
    Located: C:\User\"your_user_name"\ApData\Local\Adobe\AIR\logs.
    Down load current AIR version here:  http://get.adobe.com/air/
    Regarding uninstall, did you see dialog similar to this?
    What was preventing you from  unnstalling AIR?
    This dialog usually displays all the AIR apps installed on your system.
    You should still be able to remove AIR runtime and re-install.
    Regarding cmdline install:
    Can you run a silent install from cmd line (Run as Administrator) with 2.0.3 version of AIR?
    AdobeAIRInstaller.exe -silent

Maybe you are looking for

  • I double click on the Mozilla Firefox desktop item and it wont open!

    I tried to open firefox and it wont. I'll double clicked on the icon and nothing will open. Windows explorer opens fine but not firefox. I even Uninstalled it then re-installed it but still nothing. it was working fine earlyer today though. can you h

  • SES, TREX ... and search in indexed table

    Hi I have a task, to use SES to create intarface (in ABAP) for search in one specyfic table. This table contains field with long description text and I would like to use SES to search over it. I read some documents and i checked SAP Help ... but i st

  • BUG: import from elements leads to broken directory structure

    I want to migrate from Elements 4 to Lightroom. When I start the "Import from elements" function in Lightroom the original folder structure is not presented correctly. I'm sorry, but my directory structure in Elements is not homogeneous. Most directo

  • Layer Mask thumbnails won't activate.

    I am using photoshop CC and am suddenly not able to activate my layer masks by clicking on the layer mask thumbnails. I am using Windows 8.1 if that matters. I have never had this happen before. Can anyone give me some help with this ? Thank you.

  • "Acrobat Ribbon?"

    I recently purchased and downloaded Adobe Acrobat XI Standard (Windows,English). In my old version of Acrobat there was an "Acrobat" ribbon in Word, Excel, Outlook, etc. It is not there after this download. Advice on how to get that back?? Thanks!