Installation of webgate on Solaris (sparcv9) with WLS 10.3.5 and Apache2

Problem Description: We have installed IDM 11g and OAM 10.1.4.3 on RHEL5.5 hosts, respectively. We have successfully installed all the components:
Environment Details:
- Server1 -- 64 bit Intel RHEL5
Fusion Middleware Identity Management - 11.1.1.2
WLS 10.3.2
ODSM,OID,OVD
DB 10.2.0.4
- Server 2 32-bit Intel RHEL5
OAM 10.1.4.3
OHS 11.1.1.2
After successfully installing these hosts, we needed to create a webhost from where we could test our protected resources. This host would have a sparc v9 OS, include WLS 10.3.5, and use apache2 as its web server. These have all been successfully installed by root and are running.
Our next step was to create the webgate/access gate on the OAM host and setup the necessary policy. This was successful.
We then copied Oracle_Access_Manager10_1_4_3_0_sparc-s2_APACHE2_WebGate to the host and started the installation. Since the host is headless (just a host -- no keyboard, mouse, or gui attached to it) we have to ssh to the host and execute all the installs from the command line without gui. When we got to entering the webgate id and hit return... the process just ended without any error or logfiles. We are assuming that at that point the webgate software was installed but not configured.
We went ahead and tried the configureWebGate script:
./start_configureWebGate -i /opt/oracle/middleware/webgate -l WebGate
ld.so.1: configureWebGate: fatal: /opt/oracle/middleware/webgate/access/oblix/tools/configureWebGate/../../../oblix/lib/libstdc++.so.5: wrong ELF data format: ELFDATA2LSB
Killed
We have successfully installed OAM and IDM many times and have installed webhosts as well... but the webhosts have always been RHEL5 with WLS and OHS instead of Sparc, wls, and apache. Is there anything special about a sparc or apache install?
WLS and apache were installed as root... we have tried installing the webgate as root, oracle, even apache... but get the same results. The gcc libs are downloaded and available, but the error we see during configuration seems to indicate that they are not found. We have tried seting the LD_LIBRARY_PATH to include the directory containing the libs.
Edited by: OldGuy on Jul 7, 2011 4:04 AM

On another note... is there a Sparc equivalent for the mod_wl_ohs.conf where we would place
<Location /<deployed app>>
SetHandler weblogic-handler
WebLogicHost <weblogichost>
WebLogicPort 7001
</Location>
It appears that this goes into the apache httpd.conf file, correct? Or does the mod_wl_ohs.conf equivalent exist?
We have just about completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host.
When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, no logfile entries... just a blank browser.

Similar Messages

  • Accesing protectred URIs on Solaris (sparcv9) with WLS 10.3.5 and Apache2

    I had started to ask questions about this on another thread of mine, but since I had listed that one as answered and this being different from the original question on that thread...I felt it better to create its own thread.
    Problem Description: Environment Details:
    - Server1 -- 64 bit Intel RHEL5
    Fusion Middleware Identity Management - 11.1.1.2
    WLS 10.3.2
    ODSM,OID,OVD
    DB 10.2.0.4
    - Server 2 32-bit Intel RHEL5
    OAM 10.1.4.3
    OHS 11.1.1.2
    - Server 3 64-bit SparcV9 Webhost -- deployed app as protected uri
    WLS 10.3.5
    Apache2
    Webgate 10.1.4.3
    We believe we have completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. We have installed webhost with XP and RHEL5.6 successfully using OHS 11.1.1.2. This is the first time creating a webhost on Sparc. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host. The only differences are the SUN OS, Apache2, and WLS 10.3.5. I believe those are all acceptable for these Oracle products and versions.
    When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, ... just a blank browser.
    Doing an apachectl -l I receive the following:
    Compiled in modules:
    core.c
    prefork.c
    http_core.c
    mod_so.c
    So mod_so.c is included.
    If I go directly to the protected uri through 7001 instead of the 8890 -- the port httpd.conf has configured to listen on -- the page displays. If I open the oamsso/login.html using 8890... it displays. But if I use 8890 to bring up the protected uri... as described above nothing displays.
    One other thing, since the Sparc host is "headless" -- as described by our SysAdmin... no access directly through the sun console and no gui access via the sun host since there is no sun console just the server -- we have to access the gui via a browser on the same network. The browser is actually on the OAM host.
    From apache2 error_log on SUN host:
    15-7-2011 14:35:51Sending message: 0 13
    protocol=NAP version=3 oldest=1
    15-7-2011 14:35:51Received message: 0 13
    protocol=NAP version=3 oldest=1
    15-7-2011 14:35:51Sending NMP STS negotiation message: 0 0
    sts=open
    15-7-2011 14:35:51Received NMP STS negotiation message: 0 0
    sts=open
    15-7-2011 14:35:51Sending message: 0 14
    cm=mtisunfireHost_AG challenge=b516f1a00c2a95ee
    15-7-2011 14:35:51Received message: 0 14
    cm=access_svrid1 challenge=95520d6315ad3865 st=ma%3d25 rt=1
    15-7-2011 14:35:51Sending message: 0 15
    response=531be0a851cb2773c90aa0c91d9f779c
    15-7-2011 14:35:51Received message: 0 15
    response=2b62c22a9458e962c35d8d7d358f4fc1 st=ma%3d25 rt=1
    15-7-2011 14:35:51Sending message: 0 8
    cm=mtisunfireHost_AG ct=0 version=3
    15-7-2011 14:35:51Received message: 0 8
    ci=id%3dmtisunfireHost_AG%20maxConnections%3d1%20debug%3d0%20maxSessionTime%3d24%20sleepFor%3d60%20security%3dopen%20failoverThreshold%3d1%20aaaTimeoutThreshold%3d%20cookieSessionTime%3d3600%20maxCacheElems%3d100000%20cacheTimeout%3d1800%20configLastUpdateTime%3d1310754351%20preferredHost%3dmtisunfire:8890%20state%3dEnabled%20primaryCookieDomain%3d%20idleSessionTimeout%3d3600%20accessClientPasswd%3d02434564584046435641510409%20primaryServer1%3dhost%253dirsam-oam.dchc.smil.mil%2520port%253d8887%2520numOfConnections%253d1%20denyOnNotProtected%3d0%20cachePragmaHeader%3dno-cache%20cacheControlHeader%3dno-cache%20ipValidation%3d1 st=ma%3d25%20mi%3d2%20sg%3d32%20sm%3d rt=1
    [Fri Jul 15 14:35:52 2011] [notice] child pid 18581 exit signal Segmentation fault (11)
    [Fri Jul 15 14:35:58 2011] [notice] child pid 18582 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:01 2011] [notice] child pid 18583 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:04 2011] [notice] child pid 18585 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:07 2011] [notice] child pid 18586 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:11 2011] [notice] child pid 18590 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:12 2011] [notice] child pid 18591 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:14 2011] [notice] child pid 18592 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:15 2011] [notice] child pid 18593 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:16 2011] [notice] child pid 18594 exit signal Segmentation fault (11)
    [Fri Jul 15 14:38:35 2011] [notice] child pid 18595 exit signal Segmentation fault (11)
    [Fri Jul 15 14:38:38 2011] [notice] child pid 18596 exit signal Segmentation fault (11)
    I believe that apache is currently setup correctly at this point, but cannot understand what we are missing.

    I would say that OAM does support Apache (according to the certified Apache versions and OS's). However, there are so many distributions out there and it can be configured with countless options, be compiled with a number of different compilers, and include any number of modules that some compatibility issues are bound to arise. The Solaris distribution - also Oracle - is a case in point. I have also encountered issues with the Apache version bundled with some Linux versions (for different reasons than the Solaris bundle) for which the easiest solution has also been to download and build from source. I would imagine that is the reason for what you were told about support for generic Apache, though of course I do not know the context.
    Regards,
    Colin

  • Compatibility error with WLS 10.3.5 and OSB 11.1.1.4.0

    As per out project requirement I am using WLS 10.3.5, OSB 11.1.1.4.0, and OEPE 11.1.1.6.1, but this oepe does not support these two WLS and OSB.
    when I am trying to create a new Oracle Service Bus Configuration Project, i am getting a error:
    Plug-in "com.bea.alsb.ui" was unable to instantiate class "com.bea.alsb.ui.wizards.NewALSBContainerWizard".
    com/bea/alsb/core/containers/exceptions/ContainerException
    Can anyone please suggest the correct version of OEPE if any.
    Thanks in advance,
    Jai

    Thanks Rene, but as I said we are not using the same version of WLS and OSB so in that case is there any option that which version of OEPE i should download which support these two versions of WLS 10.3.5 and OSB 11.1.1.4.0.

  • Problems with WLS 4.5.1 and F5 Big IP HA+ Switch

    Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
              4.5.1 servers (two in the pool currently). At seemly random intervals the
              Big IP believes the one or both of the servers are not responding, so they
              are removed from the pool. We have a growing body of anecdotal evidence to
              suggest that the servers are actually on-line and available during the
              event. Either the switch is confused or the WLS servers aren't always
              responding correctly to the HTTP requests sent by the switch for polling.
              We're having problems catching the problem with the right diagnostics.
              Has anyone out there observed similar behavior with these components?
              Thanks.
              - Sean McRae
              

    Sort of,
              I use iplanet between the 2, so I havent had this problem, but I have had
              several problems with clustering, here is what I recomend doing:
              write a simple java program (or whatever your prefered language) to do a HTTP
              ping on your distinct weblogic servers every X seconds/minutes where X is less
              than Big IPs death tolerance. Time how long/or if ever each of your pings take.
              turn on verbose gc.
              My guess is its one of 3 things:
              1.) your have a big gc going on and your server isnt responding quick enough
              and big ip is marking it dead
              2.) you have thread contention that is causing your server not to respond quick
              enough
              3.) your network has some issues and the packets arent making it there, or not
              quick enough.
              the ping program will prove/disprove #2 and lead you to or away from 3. Verbose
              gc will prove/disprove #1.
              hope this helps
              -Joel
              Sean wrote:
              > Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
              > 4.5.1 servers (two in the pool currently). At seemly random intervals the
              > Big IP believes the one or both of the servers are not responding, so they
              > are removed from the pool. We have a growing body of anecdotal evidence to
              > suggest that the servers are actually on-line and available during the
              > event. Either the switch is confused or the WLS servers aren't always
              > responding correctly to the HTTP requests sent by the switch for polling.
              > We're having problems catching the problem with the right diagnostics.
              >
              > Has anyone out there observed similar behavior with these components?
              >
              > Thanks.
              >
              > - Sean McRae
              

  • JTA with WLS 8.1 sp5 and Oracle 10.1.0.4

    Hi,
              I am testing a global transaction involving two EJBs (stateless session beans) running on two separate WebLogic servers. Each ejb calls an Oracle stored procedure against a different datbase. One ejb is deployed on one server the other one on the second server.
              I want to know if it is mandatory to set up a trust relationship between the two servers. The reason I ask is that it seems the transaction is working without it (with the SecurityIdentity automatically downgraded to 'anonymous').
              However it only seems to consistently work between certain servers and randomly failing when using a different pair of servers.
              Thanks
              Cristian

    Cristian Mihaila wrote:
              > Hi Joe,
              >
              > Here is the stack trace :
              Ok, you should make sure you're using consistent SecurityInteropMode settings
              on the different servers. Trust is only needed if the servers are on different
              domains otherwise trust is not needed. We made many changes to correct a downgrade
              issue on different subsystems JTA, JMS, EJB in 81sp6. There is a patch
              available for 81sp5 for this.
              Please read: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1120356
              Joe
              >
              > <Feb 20, 2007 11:53:54 AM EST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],Xid=BEA1-02DD480140BE7F28EDB9(12622847),Status
              > =Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
              > BEA1-02DD480140BE7F28EDB9],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=89,seconds left=10,XAServerResourceInfo[OmdbXMultiPool]=(ServerResourceInfo[OmdbXMultiPool]=(state=new,assigned=pinpp2),xar=null,re-Registered = false),SCInfo[pinpp+pinpp2]=(state=rolling-back),SCInfo[mydomain+m
              > yserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+159
              > .175.18.251:7001+mydomain+t3+, XAResources={JMS_FileStore, shadbConnectionPool, arrow1lclprdPool},NonXAResources={})],CoordinatorURL=myserver+159.175.18.251:7001+mydomain+t3+): weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
              > BEA1-02DD480140BE7F28EDB9
              > at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1600)
              > at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1147)
              > at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1882)
              > at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1064)
              > at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
              > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
              > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
              > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
              > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
              > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
              > --------------- nested within: ------------------
              > weblogic.transaction.RollbackException: Transaction timed out after 29 seconds
              > BEA1-02DD480140BE7F28EDB9 - with nested exception:
              > [weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
              > BEA1-02DD480140BE7F28EDB9]
              > at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1684)
              > at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
              > at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
              > at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
              > at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
              > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl.authenticate(EPinFacade_y6z7xe_EOImpl.java:110)
              > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl_WLSkel.invoke(Unknown Source)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
              > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
              > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
              > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
              > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
              >
              > Thanks
              > Cristian

  • UOO sequencing along with WLS high availability cluster and fault tolerance

    Hi WebLogic gurus.
    My customer is currently using the following Oracle products to integrate Siebel Order Mgmt to Oracle BRM:
    * WebLogic Server 10.3.1
    * Oracle OSB 11g
    They use path service feature of a WebLogic clustered environment.
    They have configured EAI to use the UOO(Unit Of Order) Weblogic 10.3.1 feature to preserve the natural order of subsequent modifications on the same entity.
    They are going to apply UOO to a distributed queue for high availability.
    They have the following questions:
    1) When during the processing of messages having the same UOO, the end point becomes unavailable, and another node is available in order to migrate, there is a chance the UOO messages exist in the failed endpoint.
    2) During the migration of the initial endpoint, are these messages persisted?
    By persisted we mean that when other messages arrive with the same UOO in the migrated endpoint this migrated resource contains also the messages that existed before the migration?
    3) During the migration of endpoints is the client receiving error messages or not?
    I've found an entry on the WLS cluster documentation regarding fault tolerance of such solution.
    Special Considerations For Targeting a Path Service
    When the path service for a cluster is targeted to a migratable target, as a best practice, the path
    service and its custom store should be the only users of that migratable target.
    When a path service is targeted to a migratable target its provides enhanced storage of message
    unit-of-order (UOO) information for JMS distributed destinations, since the UOO information
    will be based on the entire migratable target instead of being based only on the server instance
    hosting the distributed destinations member.
    Do you have any feedback to that?
    My customer is worry about loosing UOO sequencing during migration of endpoints !!
    best regards & thanks,
    Marco

    First, if using a distributed queue the Forward Delay attribute controls the number of seconds WebLogic JMS will wait before trying to forward the messages. By default, the value is set to −1, which means that forwarding is disabled. Setting a Forward Delay is incompatible with strictly ordered message processing, including the Unit-of-Order feature.
    When using unit-of-order with distributed destinations, you should always send the messages to the distributed destination rather than to one of its members. If you are not careful, sending messages directly to a member destination may result in messages for the same unit-of-order going to more than one member destination and cause you to lose your message ordering.
    When unit-of-order messages are processed, they will be processed in strict order. While the current unit-of-order message is being processed by a message consumer, the next message in the unit-of-order will not be delivered unless it is to the same transaction or session. If no message associated with a particular unit-of-order is processing, then a message associated with that unit-of-order may go to any session that’s consuming from the message’s destination. This guarantees that all messages will be processed one at a time and in order, and any rollback or recover will not prevent ordered processing of the messages.
    The path service uses a persistent store to save the state of which member destination a particular unit-of-order is currently using. When a Path Service receives the first message for a particular unit-of-order bound for a distributed destination, it uses the normal JMS load balancing heuristics to select which member destination will handle the unit and writes that information into its persistent store. The Path Service ensures that a new UOO, or an old UOO that has no messages currently on any destination, can be enqueued anywhere in the cluster. Adding and removing member destinations will not disrupt any existing unit-of-order because the routing decision is made dynamically and those decisions are persistent.
    If the Path Service is unavailable, any requests to create new units-of-order will throw the JMSOrderException until the Path Service is available. Information about existing units-of-order are cached in the connection factory and destination servers so the Path Service availability typically will not prevent existing unit-of-order messages from being sent or processed.
    Hope this helps.

  • Installation Solaris 10 with JumpStart (ssh)

    Hello,
    I want to install Solaris 10 with a server JumpStart.
    But i want only actived the ssh mod (for security).
    How do you write that in the jumpstart script ?
    What is the command line ?
    Anybody can help me, please ?
    Thank you :)
    Message was edited by:
    Marcorel

    I have seen this too over the years and it ultimately comes down to something innate:
    Here are a few suggestions:
    1. Try and use interface ce0.
    2. Check default route on both jumpstart server and client.
    3. The arp cache may need to be flushed on the Jumpstart server.
    4. Use snoop and see what happens during the actual RARPing phase between the server and host.
    5. Switch the order in the sysid config file as indicated below:
    system_locale=en_US
    name_service=none
    network_interface=ce2
    {hostname=donau1  ip_address=10.50.57.24 netmask=255.255.252.0 protocol_ipv6=no default_route=10.50.56.1}
    security_policy=none
    terminal=vt100
    timezone="MET"
    timeserver=10.50.57.214
    nfs4_domain=dynamic
    root_password=*****************
    Please note I blanked your root password. Let me know if this helps.

  • BEA JRockit(R) R27.3.1-1-solaris-sparcv9 crashed

    Hi, This happens in solaris sparc machine. Please find the dmp below, could anyone shed some lights on this issue, please?
    Error Message: Illegal memory access. [54]
    Signal info : si_signo=10, si_code=3 si_addr=0xffffffff76a08000
    Version : BEA JRockit(R) R27.3.1-1-85830-1.5.0_11-20070716-1248-solaris-sparcv9
    GC Strategy : Mode: throughput. Currently using strategy: genparpar
    GC Status : OC is not running. Last finished OC was OC#0.
    : YC is not running. Last finished YC was YC#0.
    YC History : Ran 0 YCs since last OC.
    Heap : 0x1700000 - 0x5700000
    Compaction : (no compaction area)
    NurseryList : 0x1700000 - 0x3700000
    KeepArea : (no keeparea in use)
    NurseryMarker: [ 0x26ffff0,  0x2efffe8 ]
    CompRefs : References are compressed.
    <Nov 26, 2007 3:23:40 PM> <Debug> <NodeManager> <Waiting for the process to die: 4083>
    <Nov 26, 2007 3:23:40 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <Nov 26, 2007 3:23:40 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying wai
    ters>
    Thanks
    Tamil

    Solaris installation provides only the details I have pasted already. I dont see the core details. However, I was able to reproduce the problem in windows 64 bit machine. Here is the core details.
    ===== BEGIN DUMP =============================================================
    JRockit dump produced after 0 days, 00:03:36 on Tue Dec 04 20:44:05 2007
    Additional information is available in:
    c:\CT\dev\am\test\cases\wls\jrockit.3684.dump
    c:\CT\dev\am\test\cases\wls\jrockit.3684.mdmp
    If you see this dump, please open a support case with BEA and
    supply as much information as you can on your system setup and
    the program you were running. You can also search for solutions
    to your problem at http://forums.bea.com in
    the forum jrockit.developer.interest.general.
    Error Message: Illegal memory access. [54]
    Exception Rec: EXCEPTION_ACCESS_VIOLATION (00000000c0000005) at 0x000007FF7FC52B00 - memory at 0x0000000000000000 could not be written.
    Minidump : Wrote mdmp. Size is 133MB
    SafeDllMode : -1
    Version : BEA JRockit(R) R27.3.1-1-85830-1.5.0_11-20070716-1248-windows-x86_64
    GC Strategy : Mode: throughput. Currently using strategy: genparpar
    GC Status : OC is not running. Last finished OC was OC#145.
    : YC is not running. Last finished YC was YC#51.
    OC History : Strategy genparpar was used for OC#137.
    : Strategy singleparpar was used for OC#138.
    : Strategy genparpar was used for OC#139 to OC#140.
    : Strategy singleparpar was used for OC#141.
    : Strategy genparpar was used for OC#142 to OC#145.
    YC History : Ran 0 YCs before OC#141.
    : Ran 9 YCs before OC#142.
    : Ran 1 YCs before OC#143.
    : Ran 10 YCs before OC#144.
    : Ran 20 YCs before OC#145.
    : Ran 2 YCs since last OC.
    Heap : 0x0000000010500000 - 0x0000000011E29000
    Compaction : 0x00000000109B7B00 - 0x0000000010B9D200
    NurseryList : 0x0000000010B8C180 - 0x000000001189CF78
    KeepArea : 0x0000000011384B10 - 0x00000000116BCC40
    NurseryMarker: [ 0x0000000011384B10,  0x00000000116BCC40 ]
    CompRefs : References are compressed.
    CPU : Intel Core SSE SSE2 SSE3 SSSE3 Core EM64T
    Number CPUs : 1
    Tot Phys Mem : 2184585216 (2083 MB)
    OS version : Microsoft Windows Server 2003 version 5.2 Service Pack 1 (Build 3790) (64-bit)
    Thread System: Windows Threads
    State : JVM is running
    Command Line : -Dbasedir=c:\CT\dev\am\test\cases\wls -Dims.test.wsdl.validate= -Dims.test.wsdl.validate.exclude=com.rsa.configuration.,com.rsa.authmgr.admin.configuration. -Dam.admin.seedfile.path=../test/config/kh0701.xml -Dam.admin.seedfile.password= -Dims.toplevel.dir=c:\CT\dev\am\test\cases\wls/../../.. -Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory -Djava.naming.provider.url=t3s://am-install-w64.das.na.rsa.net:7002/ -Dims.test.admin.login=admin -Dims.test.admin.password=password -Dims.test.admin.ldap=false -Dims.test.admin.activedomain=ims.000000000000000000001000e0011000 -Dam.test.output.debug=false -Dam.test.config.dir.path=../test/config/ -Dam.test.seedfile.name=tknseed_fob_5.xml -Dam.test.64bit.seedfile.name=ENG0103_1_TOKEN.XML -Dam.test.level2=false -Djava.net.preferIPv4Stack=true -Dam.test.server.ipaddress=127.0.0.1 -Dam.test.nodesecret.search=false -Dam.test.nodesecret.path= -DSDCONF_LOC=../test/config/agent_autoreg/sdconf.rec -DSDNDSCRT_LOC=../test/config/agent_autoreg/securid -DSDSTATUS_LOC=../test/config/agent_autoreg/JAStatus.1 -DRSA_LOG_LEVEL=OFF -Dam.install=true -Dam.console.ssl=false -Dims.test.admin.password.install=5uperMan! -Dam.test.ctkip.seedfile.name=tknseed_software.xml -Dtest.ctkip.client_hello.xml=../test/config/ctkip/clienthellopdu.xml -Dam.test.token.import.nickname.seedfile.name=qa_sidsoft_nn.xml -Dam.test.token.import.nicknameserialnum.seedfile.name=qa_sidsoft_nnsn.xml -Dam.test.token.import.serialnum.seedfile.name=qa_sidsoft_sn.xml -Dtest.ctkip.client_provisioning_data=../test/config/ctkip/provisioningData.xml -Dtest.ctkip.client_nonce.xml=../test/config/ctkip/clientnoncepdu.xml -Dam.test.ldap=false -Dam.test.oa.client.type=lac -Dam.test.oa.dac.domain=SID4WIN -Dam.test.oa.run=false -Dam.test.oa.dps.ipaddress=127.0.0.1 -Dam.test.oa.dah.ipaddress=10.104.102.224 -Dam.test.output.debug.prependDate=false -Dam.test.oa.dah.nodesecret.export.path=. -Dam.test.cluster.primary.membernode.hostname.1=w2k3-qa-clstr2 -Dam.test.cluster.primary.membernode.hostname.2=w2k3-qa-clstr3 -Dam.test.cluster.primary.leadernode.hostname=w2k3-qa-clstr1 -Dam.test.cluster.primary.nodes=2 -Dam.test.cluster=false -Dproperties.directory=c:/opt/rsa/am-326425/utils/etc -Djava.library.path.systemtools= -Dbea.home=c:\CT\dev\am\test\cases\wls -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=c:/opt/rsa/am-326425/appserver/jdk/jre/lib/security/cacerts -Dssl.debug= -Dweblogic.StdoutDebugEnabled= -Dims.test.ldap.isAD=false -Dtest.level=1 -Dtest.cluster=false -Dtest.oa=false -Dtest.installer=false -Dtest.runbug=false -Dtest.admin.username=admin -Dtest.admin.password=5uperMan! -Dtest.replicas.count=0 -Dtest.ids.target=SystemIS -Dtest.realm.target=SystemDomain -Dtest.internalids.name=SystemIS -Dtest.systemdomain.name=SystemDomain -Dtest.config.dir=../test/config/ -Dtest.ns.dir=c:\CT\dev\am\test\cases\wls/../../../test/cases/wls/target -Dtest.trust.enabled=false -Dtest.trust.internalids.name=SystemIS -Dtest.trust.systemdomain.name=SystemDomain -Dtest.trust.admin.username=admin -Dtest.trust.admin.password=password -Dtest.trust.cmdclient.username=CmdClient -Dtest.trust.cmdclient.password=password -Dtest.trust.naming.factory.initial=weblogic.jndi.WLInitialContextFactory -Dtest.trust.naming.provider.url=t3://ims0.na.rsa.net:7001/ -Dam.test.config.migration.dir.path=../test/config/migration/6.1/ -Dam.test.config.migration.ldap.name=LDAP-STORE -Dims.test.admin.ldap=false -Dims.test.ldap.isAD=false -Dam.test.config.migration.ldap.enabled= -Dims.test.ldap.url=ldap://blah.na.rsa.net:389/ -Dims.test.ldap.username=uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot -Dims.test.ldap.password=adminadmin -Dtest.ids.target.ldap.url=ldap://blash.na.rsa.net:289 -Dtest.ids.target.ldap.username=uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot -Dtest.ids.target.ldap.password=adminadmin -Dhttp.keepAlive=true -Dhttp.maxConnections=5 -Dtest.cmdclient.username=CmdClient_45b0ormy -Dtest.cmdclient.password=Gy0SGr5mSH -Dtest.node1.provider.url= -Dtest.node2.provider.url= -Dtest.replica1.provider.url= -Dtest.replica2.provider.url= -Dtest.replica1.cmdclient.username=CmdClient -Dtest.replica1.cmdclient.password=password -Dtest.replica2.cmdclient.username=CmdClient -Dtest.replica2.cmdclient.password=password -Dtest.method= -Dsun.java.launcher=SUN_STANDARD org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner testsfile=C:\CT\dev\am\test\cases\wls\junittestcases198292503.properties filtertrace=true haltOnError=false haltOnFailure=false formatter=org.apache.tools.ant.taskdefs.optional.junit.SummaryJUnitResultFormatter showoutput=false formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,C:\CT\dev\am\test\cases\wls\target\test-reports\IGNORETHIS.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.BriefJUnitResultFormatter propsfile=C:\CT\dev\am\test\cases\wls\junit533938511.properties
    java.home : C:\opt\rsa\am-326425\appserver\jdk\jre
    j.class.path : C:\CT\dev\am\test\cases\wls\target\test-classes;C:\CT\dev\am\test\cases\wls\target\classes;C:\Documents and Settings\Administrator\.maven\repository\hibernate\jars\hibernate-ejb-persistence-3.2.2.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\weblogic-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\oracle-jdbc\jars\ojdbc14-10.2.0.2.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\framework-common.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\framework-config.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\admin-am.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\radius-core.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\radius-am.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\eap32.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\adjudicator.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\core-api.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\samples.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\common-am.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\amtcgen.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\oa.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\token-transport.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\auth-method-am.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\activity-monitor.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\migration61.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\sms-admin.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\test-command.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\ct-kip.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\cases.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\ims-client.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\ims-server.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\test-command.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\lw-agent.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\liberty.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\systemfields.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\wsapi.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\clu-common.jar;C:\Documents and Settings\Administrator\.maven\repository\altova-xmlspy\jars\xmlspy-schema-2006-sp2.jar;C:\Documents and Settings\Administrator\.maven\repository\caucho\jars\hessian-3.0.19rsa-1.jar;C:\Documents and Settings\Administrator\.maven\repository\httpunit\jars\httpunit-1.6.jar;C:\Documents and Settings\Administrator\.maven\repository\junit\jars\junit-3.8.2.jar;C:\Documents and Settings\Administrator\.maven\repository\jline\jars\jline-0.9.91rsa-1.jar;C:\Documents and Settings\Administrator\.maven\repository\log4j\jars\log4j-1.2.11rsa-2.jar;C:\Documents and Settings\Administrator\.maven\repository\nekohtml\jars\nekohtml-0.7.7.jar;C:\Documents and Settings\Administrator\.maven\repository\jdom\jars\jdom-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-bsafe\jars\jsafe-3.6.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-bsafe\jars\jsafeJCE-3.6.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-bsafe\jars\sslj-4.1.6.3.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-bsafe\jars\rsajsse-4.1.6.3.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-bsafe\jars\certj-2.1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\auth-elements\jars\tcgen-2.0.1-beta.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-beanutils\jars\commons-beanutils-1.7.0.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-collections\jars\commons-collections-3.0.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-httpclient\jars\commons-httpclient-3.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-logging\jars\commons-logging-1.0.4.jar;C:\Documents and Settings\Administrator\.maven\repository\jargs\jars\jargs-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-lang\jars\commons-lang-2.2.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-io\jars\commons-io-1.2.jar;C:\Documents and Settings\Administrator\.maven\repository\axis\jars\axis-1.3.jar;C:\Documents and Settings\Administrator\.maven\repository\jaxrpc\jars\jaxrpc-1.2.jar;C:\Documents and Settings\Administrator\.maven\repository\wsdl4j\jars\wsdl4j-1.5.1.jar;C:\Documents and Settings\Administrator\.maven\repository\commons-discovery\jars\commons-discovery-0.2.jar;C:\Documents and Settings\Administrator\.maven\repository\axis\jars\axis-saaj-1.3.jar;C:\Documents and Settings\Administrator\.maven\repository\springframework\jars\spring-2.0.7.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-aceagent_sdk\jars\authapi-internal-5.0.3.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa-ctkip\jars\ctkip-toolkit-1.2.126.jar;C:\Documents and Settings\Administrator\.maven\repository\ims-soyuz-cd6p1\jars\dataManager.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\am-dataManager.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\aceclntjni.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\sidauthjni.jar;C:\Documents and Settings\Administrator\.maven\repository\easymock\jars\easymock-2.2.jar;C:\Documents and Settings\Administrator\.maven\repository\easymock\jars\easymockclassextension-2.2.jar;C:\Documents and Settings\Administrator\.maven\repository\am-326425\jars\aceclntjni-oo.jar;C:\Documents and Settings\Administrator\.maven\repository\ognl\jars\ognl-2.6.7.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\webservices-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\weblogic-domain-binding-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\weblogic-container-binding-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\diagnostics-binding-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\diagnostics-image-binding-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\wlxbean-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\wlw-langx-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javelinx-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\wlManagementImplSource-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\wlManagementMBean-10.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.antlr.runtime-2.7.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\org.apache.ant.patch-1.6.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.bcel-5.2.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.apache.bcel-5.2.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.commons.collections-3.2.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.commons.lang-2.1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.commons.pool-1.3.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.dom-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.logging-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\org.apache.openjpa-0.9.7.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.xml.security-1.3.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.xml.xmlbeans-2.2.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.logging-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.bea.opensaml-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.xml.staxb.buildtime-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.xml.staxb.runtime-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.annogen-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.kodo-4.1.3.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.kodo.integration-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.kodo.integration.tools-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.process-5.3.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.xml.beaxmlbeans-2.2.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.aspectj.aspectjweaver-5.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.apache.commons.logging-1.1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.springframework.spring-2.0.2.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.springframework.pitchfork-1.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.engine.impl-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.engine.api-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.api-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.impl-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.jdkutils-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.utils-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.providers.utils-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.common.security.providers.env-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.commons.net-1.4.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.el-2.1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxb-2.0.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxws.resolver-2.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxws.rt-2.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxws.saaj.impl-2.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxws.sjsxp-2.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.jaxws.tools-2.0.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.stax.ex-1.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\glassfish.xmlstreambuffer-0.1.117.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.oro-2.0.8.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.activation-1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.annotation-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.interceptor-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.ejb-3.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.jdo-2.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.enterprise.deploy-1.2.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.jms-1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.jsp-2.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.jws-2.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.mail-1.4.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.management.j2ee-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.persistence-1.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.resource-1.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.servlet-2.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.transaction-1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.xml.bind-2.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.xml.soap-1.3.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.xml.stream-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.xml.ws-2.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\javax.xml.rpc-1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache.log4j-1.2.13.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\monfox.dsnmp.agent-4.6.5.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.jsafe-3.5.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.serp-1.12.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.apache-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.beangen-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.beaninfo-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.datasource-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.descriptor-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.repackaged.asm-1.5.2.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.diagnostics.core-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.diagnostics.instrumentor-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.i18n-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.i18n.generator-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.management.core-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.mbean.maker-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.mbean.support-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.messaging.kernel-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.resourcepool-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.rmi.client-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.security.wls-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.saaj-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.stax-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.store-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.store.gxa-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.transaction-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.utils.full-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.utils.classloaders-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.utils.expressions-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.utils.wrapper-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.timers-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.workmanager-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.workarea-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.jatmi-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.weblogic.security-2.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.nodemanager.plugin-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\weblogic\jars\com.bea.core.jmspool-1.0.0.0.jar;C:\Documents and Settings\Administrator\.maven\repository\emma\jars\emma-2.0.5312.jar;C:\Documents and Settings\Administrator\.maven\repository\emma\jars\emma_ant-2.0.5312.jar;C:\Documents and Settings\Administrator\.maven\repository\rsa\jars\maven-rsa-ext-1.1.jar;C:\Documents and Settings\Administrator\.maven\repository\xdoclet\jars\xdoclet-xdoclet-module-1.2.3.jar;C:\Documents and Settings\Administrator\.maven\repository\clover\jars\clover-1.3.13.jar;C:\Documents and Settings\Administrator\.maven\repository\clover\jars\cenquatasks-1.3.14.jar;C:\Documents and Settings\Administrator\.maven\repository\xjavadoc\jars\xjavadoc-1.5-snapshot050611.jar;C:\Documents and Settings\Administrator\.maven\repository\xdoclet\jars\xdoclet-1.2.3.jar;C:\Documents and Settings\Administrator\.maven\repository\hibernate\jars\hibernate-3.2.2.jar;C:\Documents and Settings\Administrator\.maven\repository\hibernate\jars\hibernate-annotations-3.2.1.jar;C:\Documents and Settings\Administrator\.maven\repository\antlr\jars\antlr-2.7.6.jar;C:\Documents and Settings\Administrator\.maven\repository\iscreen\jars\iScreen-1-1-0rsa-1.jar;C:\Documents and Settings\Administrator\.maven\repository\iscreen\jars\iScreen-mvel-1-1-0rsa-1.jar;C:\Documents and Settings\Administrator\.maven\repository\iscreen\jars\mvel-1.1.8-java1.5.0_10.jar;C:\Documents and Settings\Administrator\.maven\repository\asm\jars\asm-1.5.3.jar;C:\Documents and Settings\Administrator\.maven\repository\cglib\jars\cglib-2.1_3.jar;C:\Documents and Settings\Administrator\.maven\repository\odmg\jars\odmg-3.0.jar;C:\Documents and Settings\Administrator\.maven\repository\dom4j\jars\dom4j-1.6.1.jar;C:\Documents and Settings\Administrator\.maven\repository\xerces\jars\xercesImpl-2.7.1.jar;C:\Documents and Settings\Administrator\.maven\repository\xml-apis\jars\xml-apis-1.3.02.jar;C:\Documents and Settings\Administrator\.maven\repository\hsqldb\jars\hsqldb-1.7.2.4.jar;C:\Documents and Settings\Administrator\.maven\repository\opensymphony-oscache\jars\oscache-2.3.2rsa-1.jar;C:\Documents and Settings\Administrator\.maven\repository\j2ee\jars\j2ee-1.5.jar;C:\Documents and Settings\Administrator\.maven\repository\xml-apis\jars\xml-apis-1.3.03.jar;C:\Documents and Settings\Administrator\.maven\repository\xerces\jars\xercesImpl-2.8.0.jar;C:\Documents and Settings\Administrator\.maven\repository\xml-resolver\jars\xml-resolver-1.1.jar;C:\CT\library\apache-maven\1.1\lib\ant-launcher-1.6.5.jar;C:\CT\library\apache-maven\1.1\lib\ant-1.6.5.jar;C:\CT\library\apache-maven\1.1\lib\ant-junit-1.6.5.jar
    j.lib.path : C:\opt\rsa\am-326425\appserver\jdk\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;c:\opt\rsa\am-326425\appserver\jdk\jre\bin;c:\opt\instantclient_10_2;C:\cygwin\bin;c:\CT\library\apache-maven\1.1\bin;c:\CT\library\activetcl\8.4.11\linux-x86\bin;C:\cygwin\bin;C:\cygwin\bin;C:\cygwin\usr\local\bin\;C:\cygwin\usr\sbin;c:\opt\instantclient_10_2;C:\cygwin\bin;c:\CT\library\apache-maven\1.1\bin;c:\CT\library\activetcl\8.4.11\linux-x86\bin;C:\cygwin\bin;C:\cygwin\bin;C:\cygwin\usr\local\bin\;C:\cygwin\usr\sbin;c:\opt\rsa\am-325621\db\bin;c:\opt\rsa\am-325471\db\bin;c:\opt\rsa\am-325281\db\bin;c:\opt\rsa\am-325250\db\bin;c:\opt\rsa\am-325240\db\bin;c:\opt\rsa\am-324877\db\bin;c:\opt\rsa\am-324751\db\bin;c:\opt\rsa\am-324743\db\bin;c:\opt\rsa\am-324632\db\bin;c:\opt\rsa\am-324516\db\bin;c:\opt\rsa\am-324412\db\bin;c:\opt\rsa\am-324131\db\bin;c:\opt\rsa\am-das-323485\db\bin;c:\opt\rsa\am-das-323453\db\bin;c:\opt\rsa\am-das-323386\db\bin;c:\opt\rsa\am-das-323315\db\bin;c:\opt\rsa\am-das-323052\db\bin;c:\opt\rsa\am-das-322733\db\bin;c:\opt\rsa\am-das-322676\db\bin;c:\opt\rsa\am-das-322622\db\bin;c:\opt\rsa\am-das-322471\db\bin;c:\opt\rsa\am-das-322445\db\bin;c:\opt\rsa\am-das-322264\db\bin;c:\opt\rsa\am-das-321939\db\bin;c:\opt\rsa\am-das-321144\db\bin;c:\opt\rsa\am-321052\db\bin;c:\opt\rsa\am-321006\db\bin;c:\opt\rsa\am-320711\db\bin;c:\opt\rsa\am-320613\db\bin;c:\opt\rsa\am-320550\db\bin;c:\opt\rsa\am-320535\db\bin;c:\opt\rsa\am-320466\db\bin;c:\WINDOWS\system32;c:\WINDOWS;c:\WINDOWS\System32\Wbem;C:\cygwin\bin
    JAVA_HOME : c:\opt\rsa\am-326425\appserver\jdk

  • Installing JDK 5.0 update 11 in Solaris (sparcv9 � 64bit)

    I have downloaded the self extracting instillation of JDK 1.5.0_11 (jdk-1_5_0_11-solaris-sparcv9.sh) in to my windows machine and then copied the file to the Solaris box. While running the file, I am getting the following error.
    Do you agree to the above license terms? [yes or no]
    yes
    Unpacking...
    Checksumming...
    1
    The download file appears to be corrupted.  Please refer
    to the Troubleshooting section of the Installation
    Instructions on the download page for more information.
    Please do not attempt to install this archive file.Kindly help me in resolving this issues.
    Thanks,
    Muthu

    Sorry for bothering you all. I had this issues resolved. Follow this thread
    http://forum.java.sun.com/thread.jspa?threadID=787923&messageID=4478546
    NOTE: If you are copying the installable from windows to Solaris box, please use the ftp command with binary mode.
    Thanks,
    Muthu

  • JDK1.5.0_06 Installation problem on SunOS 5.8 with sparc9

    I've downloaded jdk-1_5_0_06-solaris-sparcv9.sh (for 64-bit). Then made it executable. Run it. Some licence text was shown, but then:
    ...bla-bla-bla...
    Agreement. "Programs" mean Java applets and applications intended to
    run on the Java 2 Platform Standard Edition (J2SE platform) platform
    on Java-enabled general purpose desktop computers and servers.
    Do you agree to the above license terms? [yes or no]
    yes
    Unpacking...
    Checksumming...
    1
    The download file appears to be corrupted. Please refer
    to the Troubleshooting section of the Installation
    Instructions on the download page for more information.
    Please do not attempt to install this archive file.
    Please, tell me, what should I do?
    I copy flashget downloader & explorer's one to my windows machine and then via WinSCP to Unix SunOS.
    May be that is not downloading problem?

    never mind...
    I created a new project and instead of picking regular java app, I selected web.
    That seem to set up jars from Tomcat....
    it's working now.
    I need to drill this down a bit further. Still a bit lost.

  • How to configure MQ with WLS (JMS MQ vs Native MQ)

    Hi All,
    SOA Suite = 11.1.3.3
    MQ Series = 6.0
    Jdeveloper = 11.1.3.3
    I want to read/write data to an MQ which is setup on a physical box different from Weblogic Server box. But both systems fall under the same network. I did some research on the forums to know the steps to configure MQ but ultimately got confused with the following questions in mind.
    1. What is the difference between JMS MQ and Native MQ? How to determine which one to use?
    2. If native MQ can be used here, what are the steps to configure Native MQ on WLS in my situation?
    3. Do I need any foreign servers or message bridges to be configured?
    Please provide any directions or pointers.
    Regards,
    Neeraj Sehga

    1. What is the difference between JMS MQ and Native MQ? How to determine which one to use?Native MQ refers to a proprietary api provided by IBM in multiple languages including java so that applications running on these can communicate mq. IBM also provides JMS wrappers around this native api, so that a jms client can talk to mq using JMS API. This is called MQ JMS.
    2. If native MQ can be used here, what are the steps to configure Native MQ on WLS in my situation?SOA suite provides a MQ Resource Adaptor which can be used to connect to MQ. The developers of this resource adapter would have used the native api to enable the adaptor to talk to MQ, so that you dont have to worry about it. However you will need to configure the properties of your local MQ ( qmgr , q name etc). This is done in the outbound connection pool properties of the resource adaptor.
    please check this blog for how to do this : http://soa-bpel-esb.blogspot.com/2009/09/configuring-mq-in-11g-soa-suite.html.
    Since your MQ installation is in a remote machine you will have to configure the following properties specific to your environment - hostname, port, server connection channel, along with the queue manager name and queue name
    3. Do I need any foreign servers or message bridges to be configured?Not required for your case if you are using MQ Adaptor. Since MQ also provides a JMS transport , you would have required foreign servers if you have to use JMS Adaptor instead of MQ Adaptor. Native MQ is expected to be faster than MQ JMS as it doesn't have the extra JMS layer.

  • Problems with WLS 7.0 and NES plug-in

    Hi,
    I am not able to configure NES with weblogic 7.0. I created a domain
    with an admin server and 3 clustered servers. When I tried to configure
    NES it is giving me these errors.
    [06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
    /data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
    ml, line 32, column 15: Error processing obj.conf line 1: init functions
    are not allowed in this objset
    Also below are the lines copied from obj.conf that I added.
    Init fn="load-modules" funcs="wl_proxy,wl_init"\
    shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
    Init fn="wl_init"
    <Object name="weblogic" ppath="*/weblogic/*">
    Service fn=wl_proxy \
    WebLogicCluster="localhost:7001,localhost:7002,\
    localhost:7003" PathTrim="/weblogic"
    </Object>
    Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
    is 6.0 and I am on Solaris 8.
    Shiva.

    Hi,
    I am not able to configure NES with weblogic 7.0. I created a domain
    with an admin server and 3 clustered servers. When I tried to configure
    NES it is giving me these errors.
    [06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
    /data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
    ml, line 32, column 15: Error processing obj.conf line 1: init functions
    are not allowed in this objset
    Also below are the lines copied from obj.conf that I added.
    Init fn="load-modules" funcs="wl_proxy,wl_init"\
    shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
    Init fn="wl_init"
    <Object name="weblogic" ppath="*/weblogic/*">
    Service fn=wl_proxy \
    WebLogicCluster="localhost:7001,localhost:7002,\
    localhost:7003" PathTrim="/weblogic"
    </Object>
    Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
    is 6.0 and I am on Solaris 8.
    Shiva.

  • Solaris x86 with Oracle RAC 10g Enterprise Edition Release 10.2.0.3.0

    Hello,
    Maybe you can help me (new on RMAN backup) in doing this.
    I have configured a single Oracle 10g database to have backup with RMAN with following steps:
    1. $ mkdir $ORACLE_BASE/rman_scripts
    2. $ mkdir $ORACLE_BASE/logs
    3. $ mkdir $ORACLE_BASE/tracking
    4. $ mkdir $ORACLE_BASE/c_backup
    5. $ sqlplus sys/<password> as sysdba
    6. SQL> alter system set db_recovery_file_dest_size = 50G scope=both;
    7. SQL> alter system set db_recovery_file_dest='${ ORACLE_BASE}/flash_recovery_ area' scope=both;
    8. SQL> alter system set log_archive_dest_10='location= use_db_recovery_file_dest';
    9. SQL> shutdown immediate
    10. SQL> startup nomount
    11. SQL> alter database archivelog;
    12. SQL> alter database open;
    13. SQL> alter database enable block change tracking using file '${ORACLE_BASE}/tracking/rman_ change_track.f';
    14. $ rman target /
    15. RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK
    TO '/var/opt/oracle/flash_ recovery_area/ORCL/c_backup/% F';
    16. RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    17. RMAN> CONFIGURE BACKUP OPTIMIZATION ON;
    18. RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    19. RMAN> exit
    I need to configure incremental backup with RMAN on a two node Solaris x86 with Oracle RAC 10g Enterprise Edition Release 10.2.0.3.0 installation.
    We also use ASM to store database files, and have Oracle software installed on separate file systems (two Oracle roots for Node1 and Node2).
    I have following questions:
    1) where to put Flash Recovery Area (FRA)?
    I saw recommendations to put FRA on the ASM, is this the best way to do it?
    2) Can I put FRA on another file system (not on the ASM) which is available only from Node1? This way I can save space on the ASM.
    3) Is it possible/recommended to run RMAN from Node1 only?
    Below is the script used to run RMAN on the normal Oracle database (without RAC) which I need to change :
    =============================================================================================
    2.0 Oracle backup script: /opt/app/oracle/rman_scripts/backup.sh
    Use this for daily backups, possiblly as a cron job.
    Once a week run this: /opt/app/oracle/rman_scripts/backup.sh FULL
    All other days of the week: /opt/app/oracle/rman_scripts/backup.sh INCREMENTAL
    Note: You may have to change ORACLE_SID, ORACLE_BASE below to match your database.
    =============================================================================================
    #!/usr/bin/ksh
    ORACLE_SID=orcl
    ORACLE_BASE=/opt/app/oracle
    ORACLE_HOME=${ORACLE_BASE}/product/10.2.0/db_1
    PATH=${ORACLE_HOME}/bin:/usr/bin
    LOGDIR=${ORACLE_BASE}/logs
    LOGFILE=${LOGDIR}/rman.log
    if [[ $# < 1 ]]
    then
    echo "usage: backup.sh FULL|INCREMENTAL"
    exit;
    fi
    BACKUPTYPE=${1}
    full='FULL'
    incremental='INCREMENTAL'
    if [[ $BACKUPTYPE == $full ]]
    then
    $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
    run {
    backup database;
    SQL 'alter system archive log current';
    backup archivelog all;
    delete noprompt obsolete;
    exit;
    eof
    echo ''
    fi
    if [[ $BACKUPTYPE == $incremental ]]
    then
    $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
    run {
    backup database;
    backup incremental level 1 database;
    SQL 'alter system archive log current';
    backup archivelog all;
    delete noprompt obsolete;
    exit;
    eof
    echo ''
    fi

    Hi [email protected],
    Q1) where to put Flash Recovery Area (FRA)?
    A1) With RAC: on the shared storage
    I saw recommendations to put FRA on the ASM, is this the best way to do it?
    If you want your backups to be available for both nodes you have to use shared storage or tape using an mml library.
    So if you want to use the FRA for rman backups and the database is on ASM just make ASM the standard for the FRA as well.
    Q2) Can I put FRA on another file system (not on the ASM) which is available only from Node1? This way I can save space on the ASM.
    A2) Than you cannot recover in case Node1 is down. Best would be to send your storage admin to a training course so he can manage the clustered raw devices needed for ASM.
    Q3) Is it possible/recommended to run RMAN from Node1 only?
    A3) No see A2.
    Regards,
    Tycho

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • IE5 and Netscape with WLS 5.1

    Hi,
    I sent this out a couple of weeks ago. I have tried the solution but with no success could some one please help...
    We are using Weblogic 5.1 Service Pack 8 on Solaris 2.6, with Apache server acting as a bridge. Apache actually does not serve any content and just forwards ALL requests to WLS. We have a problem at the moment that if you use internet explorer with WLS then it is extremely slow serving up pages. Weblogic listens on port 7001. If we use Netscape to connect then it runs with no slow downs at all, about three second to serve a page but if we use IE it takes nearly a minute. This delay occurs when the request goes through apache. If we directly access WLS on port 7001 then there is no such delay.
    Any ideas on what could cause that delay? Is it an Apache bridge problem or a WLS one?
    Cheers,
    Barnaby
    [att1.html]

    You can have it but not for fail-safe configuration.
    It is not possible to have clusters with different
    WLS versions especially between 5.1 & 8.1
    Kumar
    Alexander von Alkier wrote:
    hi all,
    we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
    have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
    I'm now thinking of is: is it possible to run a WLS cluster that has 2
    Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
    Reason of thinking so, is that want to have the most failsafe configration
    as possible during our upgrade.
    I searched the BEA docs, but didn't find anything.
    any help would be fine.
    thanks
    Alexander

Maybe you are looking for