Newbee's question: Error connecting to the management server for the first time

Dear all, I am very new to the oralce world and got stuck today the first time I install oracle 8i on my win2k pro.
After the installation, I was trying to connect the Enterprise Manager Console for the first time, using the default user name sysman and password oem_temp (correct?). The problem is that I don't know exactly what is a management server, and what name it should be called. I named the database/sid name orarem, under D:\Oracle\admin\OraRem, does it have something to do with this issue?
I only installed the oracle enterprise server edition 8.1.6.0.0, not the Client part, will that matter if I only wanna run oracle on my stand alone desktop as a testing procedure for now?
Any help would be really appreciated!!

Bingo!! I had been trying dumping various .plist files
Not surprisingly i was a little hesitant about throwing the Airport folder in the bin.
First thing I did was to check it had been replaced on restarting!
Glad to say that "Check for updates" is now doing its thing.
I don't know why it gave me such grief, I just felt it could develope into something nasty down the line.
Thank you again.
Unfortunately they don't seem to have a points system for this topic.
Your fix should be available in Google from now on

Similar Messages

  • Sendgrid addon "The management portal for the add-on isn't available right now. Please try again later"

    After adding the Sendgrid Addon, when we go to the "Go to the SendGrid web site for the next steps"  link, we get the following error message: "The management portal for the add-on isn't available right now. Please try again later." 
    Best regards,
    Joe Boren

    Hi,
    If you have successfully purcasedAdd-on SendGrid, but it is not available, I suggest you contact with support, it's the best choice for you.Please contact support team by creating a support ticket at
    http://www.windowsazure.com/en-us/support/contact/ Or if that doesn't work because you don't have an active subscription you will need to contact general customer support to have them create a
    support ticket for you
    http://support.microsoft.com/gp/customer-service-phone-numbers?wa=wsignin1.0
    Best Regards,
    Jambor
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • HT201250 I had files stored on a hard drive that were not on my Mac. I used the hard drive for my first Time Machine back up, but it was not enough hard drive space to finish. Now those stored files are gone. Is there any way I can recover them?

    I had files stored on a hard drive that were not on my Mac. I used the hard drive for my first Time Machine back up, but it was not enough hard drive space to finish. Now those stored files are gone. Is there any way I can recover them?  No, they were not part of previous Time Machine backups, and I have checked both the hard drive the documents were lost on and the new one that I now use for backups. Any suggestions would be helpful, as the lost files are old pictures that are gone forever. :[ Thanks!

    1. Yes, if both drives are formatted as Mac OS Extended (Journaled).
    2. Reformat the drives if needed, open the Time Machine pane of System Preferences, and remove the drive with the pictures from the list of items set to be excluded.
    (110331)

  • I am not able to login to the Management Server from the Management Server dialog from FlexBuilder

    hi,
      I am trying to setup the flex builder project for the demo host sample and am running into issues with the login. I have my OEM setup in https://<ip-address>:7801/em and am able to login with the credentials. Now, when I try to launch the HostSample.html from the flex builder project and the details are provided to my Management Server dialog, the same credentials fail with some IO Error. Please help
    Error during operation: Logging in to Management Server
    [FaultEvent fault=[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032"]. URL: https://10.105.219.188:7801/em/websvcs/mpws/LoginService"] messageId=null type="fault" bubbles=true cancelable=true eventPhase=2]
    The LoginService.login is failing.
    Here is the Item details
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Header>
        <ns0:TraceRequest xmlns:ns0="http://em.oracle.com/tracing/xsd">
          <ns0:ecid>15D0C25A-51F9-B29F-EC74-DDD780ACCCEE</ns0:ecid>
        </ns0:TraceRequest>
        <ns1:RslVersion xmlns:ns1="http://em.oracle.com/auth/xsd">
          <ns1:rslVersion>12.1.0.3.0</ns1:rslVersion>
        </ns1:RslVersion>
        <ns1:InternalToken xmlns:ns1="http://em.oracle.com/auth/xsd">
          <ns1:intToken>secret-token</ns1:intToken>
        </ns1:InternalToken>
      </SOAP-ENV:Header>
      <SOAP-ENV:Body>
        <tns:loginRequest xmlns:tns="oracle.sysman.emx.LoginService">
          <loginInfo>
            <username>sysman</username>
            <password><my password text in plain text format></password>
            <role xsi:nil="true"/>
          </loginInfo>
        </tns:loginRequest>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

    When running with HTTPS, FlexBuilder enforces security restrictions on same domain policy and verifies security certificate.  To workaround this you either have to disable security on your OMS and use HTTP for your development (using emctl secure unlock), or you have to install the security certificate from your OMS in the IE browser you are launching from FlexBuilder.
    To install the certificate in Firefox:  go to the EM website using Firefox, and you will see "The Connection is Untrusted", expand "I Understand the Risks" and click "Add Exception".  On the dialog that appears leave all the defaults and click "Confirm Security Exception".  At that point if you close/reopen the browser you can go back to the EM website and you should see no security exception.
    To install the certificate in IE:  go to the EM website using IE and you should see "There is a problem with this website's security certificate", click "Continue to this Website (not recommended)", the address bar will then change to show "Certificate error" on the right side of the URL.  Click that icon and the "View certificates" on the "Untrusted Certificate" popup.  On the dialog that appears, click the "Certification Path" tab, then click the root node (root certificate) in the path and click "View Certificate".  In the new dialog that appears, click "Install Certificate...".  Then click "Next>", click "Place all certificates in the following store", click "Browse..."., select "Trusted Root Certification Authorities" and click "OK".  Then click "Next>" and click "Finish".  On the "Security Warning" dialog, click "Yes" to install the certificate and then "OK on the confirmation dialog.  Click "OK" on the "Certificate" dialog (there should be two) that was launched to install the root certificate.  Now on the original "Certificate" dialog click "View Certificate".  Then click "Next>", click "Place all certificates in the following store", click "Browse..."., select "Trusted Root Certification Authorities" and click "OK".  Then click "Next>" and click "Finish" and then "OK on the confirmation dialog. Click "OK" and "OK". At that point if you close/reopen the browser you can go back to the EM website and you should see no security exception.

  • Is there any way changing the priviledge after starting the managed server with the other user

    Hi,
    is there any way to change the user privilege after i have started the managed
    server with one user.....say for example ....i have started one of my Managed
    server as "root" ...but after that i wanted to make this instance work under as
    "inet"
    how do i do this OR is it possible ????
    please advise ....
    sangita

    Thanks again Rob.
    Rob Woollen <[email protected]> wrote:
    >
    >
    sangita wrote:
    Thanks Rob for been so quick in responding.
    I have 3 questions for you:
    Running a server under root is a huge security hole.My Question: 1) what are the probable security issues while runninga server under
    root ?
    are these security issues external(from outside world) or internal(internally
    within a company) ?
    Iam basically curious to know external threats.
    The problem is the root user can do anything. So if someone finds a
    security hole in your server, then they have complete control of your
    system.
    The usual reason people want to do this is so they can bind to a port
    <
    1024. ie they want their web server to listen to 80.My Question: 2) What is the harm in using port 80 for webserver andwhy do the
    people wanted to bind to a port < 1024 ?
    People normally use 80 for web servers because that's the well-known
    port.
    Personally I would not recommend that you go that route. I would
    recommend that you start the server as a very unprivileged user andbind
    it to some port (say 7001).
    Most firewalls support redirecting ports. Your firewall can redirect
    80
    on the external net to 7001 on the internal net. That's the solution
    I
    would recommend.My Question: 3) Suppose iam having a cluster of 2 Managed servers runningon port
    7070. And Iam having a Iplanet server working as a Webserver that basicallyproxies
    requests to this cluster. Then what is the best approach that i shouldfollow
    in this context.....to be honest with you ....i still couldnot understandwhat
    does "binding" the webserver port to a managed server in weblogic mean.
    I would have your firewall redirect 80 to whatever port Iplanet is
    listening on and then have iplanet proxy to WLS.
    Do not run your WLS servers as root.
    -- Rob
    Iam sorry for asking these "silly" questions(in your opinion) ...butiam a bit
    confused.
    thanks, sangita
    Rob Woollen <[email protected]> wrote:
    Running a server under root is a huge security hole.
    The usual reason people want to do this is so they can bind to a port
    <
    1024. ie they want their web server to listen to 80.
    There is a set uid option in WLS where you start the server as root
    and
    then after it binds to the low port, it will switch to another userthat
    you specify.
    Personally I would not recommend that you go that route. I would
    recommend that you start the server as a very unprivileged user andbind
    it to some port (say 7001).
    Most firewalls support redirecting ports. Your firewall can redirect
    80
    on the external net to 7001 on the internal net. That's the solution
    I
    would recommend.
    -- Rob
    sangita wrote:
    <Sure, it's possible to do this, >
    how to do this?
    <but why do you want to do it? >
    Iam not sure why this group (the other group than me) does start theirserver
    as "root"...but somebody from that group asked me about this today.
    I would not recommend that you start WLS as root on your production
    system ever under any cirucmstance.then what is the best approach and what are the pros and cons if westart the
    server as "root" OR as different user ????
    please advise ....
    thanks again.
    Rob Woollen <[email protected]> wrote:
    Sure, it's possible to do this, but why do you want to do it?
    I would not recommend that you start WLS as root on your production
    system ever under any cirucmstance.
    -- Rob
    sangita wrote:
    Hi,
    is there any way to change the user privilege after i have startedthe managed
    server with one user.....say for example ....i have started one
    of
    my Managed
    server as "root" ...but after that i wanted to make this instance
    work
    under as
    "inet"
    how do i do this OR is it possible ????
    please advise ....
    sangita

  • Can I run a different user as the managed server than the admin server?

    Under unix, can I run a Weblogic 7 managed instance as a different user than the
    admin server in the same domain? If not, any reference docs on BEAs site?

    You mean a different UNIX user? Yes, that should be fine.
    -- Rob
    Frank wrote:
    Under unix, can I run a Weblogic 7 managed instance as a different user than the
    admin server in the same domain? If not, any reference docs on BEAs site?

  • Can you run a different user on the managed server than the admin server?

    Under unix, can I run a Weblogic 7 managed instance as a different user than the
    admin server in the same domain? If not, any reference docs on BEAs site?

    That shouldnt pose a problem.
    anand
    In article <3f679e4d$[email protected]>, Frank wrote:
    >
    Under unix, can I run a Weblogic 7 managed instance as a different user than the
    admin server in the same domain? If not, any reference docs on BEAs site?

  • Error while starting the managed server using nodemanager

    HI ,
    I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
    Below is the error in the managed server log,
    startWebLogic.sh: grep: not found
    startWebLogic.sh: uname: not found
    startWebLogic.sh: test: argument expected
    can you help me to solve the problem please. i am using weblogic 10.3.3
    thanks
    Arun

    I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

  • Errors while starting the manager server

    Hi
    I have created a manager server under weblogic 6.1 with sp2.
    I am trying to start the managed server using the command file provided by weblogic. And I am getting the following exceptions.... The Admin server is up and running.
    Configuration for the managed server
    Name: MngdServer
    Machine: None
    ListenPort: 9001
    ListenAddress: <null>
    External DNSName: <null>
    The exception I am getting is ....
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
    at java.net.Socket.<init>(Socket.java:273)
    at java.net.Socket.<init>(Socket.java:127)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:201)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
    at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
    at weblogic.net.http.HttpClient.New(HttpClient.java:156)
    at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
    at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
    at weblogic.management.Admin.initialize(Admin.java:326)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001'
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:210)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:261)
    at weblogic.net.http.HttpClient.<init>(HttpClient.java:121)
    at weblogic.net.http.HttpClient.New(HttpClient.java:156)
    at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:283)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
    at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1019)
    at weblogic.management.Admin.initialize(Admin.java:326)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: connecting to http://localhost:9001/wl_management_internal2/Bootstr
    ap - with nested exception:
    [java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '9001']
    at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1110)
    at weblogic.management.Admin.initialize(Admin.java:326)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    ***************************************************************************

    startManagedWebLogic.cmd MngdServer
    http://localhost:9001
    You should give the url for the admin server and name of the managed server as arguments for this command. you seem like giving the url for the managed server.
    this command needs url for the admin server so that it can connect to that admin server and add this managed server to that domain.
    Good luck

  • Start managed server on the console problem

    I use the weblogic server 6.1 sp1 on the microsoft NT 4.0 and 2000 server
    sp2, But i have a problem.
    When i use the default setting to start the administration server and node
    managed, Then i try to start the managed server on the console, Then
    <2002/1/8 H07B3745?gt; <Error> <NodeManager> <Could not start
    server'server622' via Node Manager - reason: '[SecureCommandInvoker: Could
    not create a socket to the NodeManager running on host 'myIPAddress:5555' to
    execute command 'online null', reason: Connection refused: connect. Ensure
    that the NodeManager on host 'myIPAddress' is configured to listen on port
    '5555' and that it is actively listening]'>
    All of the configuration setting ( include the startWeblogic and
    startNodeManagerWeblogic ) is defuault.
    But when i install the Sun JDK 1.3.1_20 on those machines, It's fine to
    start the managed server on the console, Although it's failure now again, i
    don't know why ( coz, i uninstall weblogic and jdk then install it again ).
    Anyone have this problem, could tell me how to solve it, Thx.

    Chris,
    I want to be sure I understand because I was a little unclear at the end. You
    did successfully get the managed server to start from the console after you
    installed jdk1.3.1? Be sure your PATH variable contains the correct java bin
    directory. Are you failing again now that you reinstalled WLS and the JDK?
    Regards,
    Velvet
    Developer Relations Engineer
    BEA Systems
    Chris Chuang wrote:
    I use the weblogic server 6.1 sp1 on the microsoft NT 4.0 and 2000 server
    sp2, But i have a problem.
    When i use the default setting to start the administration server and node
    managed, Then i try to start the managed server on the console, Then
    <2002/1/8 H07B3745?gt; <Error> <NodeManager> <Could not start
    server'server622' via Node Manager - reason: '[SecureCommandInvoker: Could
    not create a socket to the NodeManager running on host 'myIPAddress:5555' to
    execute command 'online null', reason: Connection refused: connect. Ensure
    that the NodeManager on host 'myIPAddress' is configured to listen on port
    '5555' and that it is actively listening]'>
    All of the configuration setting ( include the startWeblogic and
    startNodeManagerWeblogic ) is defuault.
    But when i install the Sun JDK 1.3.1_20 on those machines, It's fine to
    start the managed server on the console, Although it's failure now again, i
    don't know why ( coz, i uninstall weblogic and jdk then install it again ).
    Anyone have this problem, could tell me how to solve it, Thx.

  • Office Professional Plus 2010 - Fails to Install - Error 25004 - "System error: -1073418209" - Microsoft Key Management Server

    I am receiving an error when attempting to install a site license copy of Microsoft Office Professional Plus 2010. The enterprise environment that I am in is using a Microsoft Key Management Server for the authentication of all Office 2010 and Windows 7
    installations. The error that I receive at the end of the installation is: "Error 25004. The product key you entered cannot be used on this machine. This is most likely due to previous Office 2010 trials being installed. (System error: -1073418209)".
    I have never installed a trial of Office 2010, nor did I ever install the beta of Office 2010. I do have a copy of Microsoft Office Projects 2010 installed. Before attempting to install Office 2010, I had Office 2007 installed. I used the Upgrade option
    to install 2010, instead of removing 2007 (which apparently I should have done instead) first. I have tried using the Microsoft FixIt tool to remove both Office 2007 AND Office 2010. Neither of those tools has fixed my problem. Office 2010 also does not show
    up in my Add/Remove Programs list.
    Any ideas on how to fix this? I do not have time to reformat until after the Holiday seasons, and need to have Office working!

    Hi,
    The full error text is as follows: Error 25004: The product key you entered cannot be used on this machine. 
    This is most likely due to previous Office 2010 trials being installed. (System error: 1073422308)
    The key you are currently trying to install with, is an Office Professional Plus Trial key. A machine will allow one Professional Plus Trial key installed on it ever. Meaning you can
    install a trial on a machine, used it for some time, uninstall Office. When you go back to the Microsoft website and get a new key, the second installation will be rejected with the above error message.
    If this is not the situation, try to completely uninstall all the versions of the Office programs from control panel, and then use the suggestions in this KB
    article to uninstall it:
    How do I uninstall Office 2003, Office 2007 or Office 2010 suites if I cannot uninstall it from Control Panel?
    http://support.microsoft.com/kb/290301
    Then, reinstall the Office 2010 program.
    Best Regards,
    Sally Tang

  • Error while running the Managed server

    Hi
    i am getting the below error while running the Managed server.
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    can anyone help

    Srinath is 100% correct.
    If the deployment failed, then there will very likely be some mention in the log.
    You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
    I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
    Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
    Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
    I hope that helps,
    -ryan

  • We are using the Azure server for our web services. Server is generating an error "Unable to connect to the remote server". What is this error means

    We are using the Azure server for our web services. Server is generating an error "Unable to connect to the remote server". What is this error means  

    Hello,
    Did you means that you use the Windows Azure Virtual Machine DNS name as the server name in the Reporting Server Web Services URL?
    For example:
    Report server:http://uebi.cloudapp.net/reportserver
    Report manager:http://uebi.cloudapp.net/reports
    If you want to connect to Report Manager on the virtual machine from a remote computer, you should create a  virtual machine TCP Endpoint and open the port in the virtual machine’s firewall. By default, the report server listens for HTTP requests
    on port 80.
    Reference:http://msdn.microsoft.com/en-us/library/jj992719.aspx#bkmk_ssrs_connect_2_remote_RM
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • JMX Connectivity has been discontinued with the managed server

    Dear all,
    I am getting following msg in my weblogic 11g manage server and admin server.
    Namage Server Log
    ####<Nov 22, 2010 2:15:39 PM IST> <Warning> <Log Management> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415539687> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    Admin Server Log
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <JMX> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-149507> <JMX Connectivity has been discontinued with the managed server NewTradeServer.>
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-002634> <The server "NewTradeServer" disconnected from this server.>
    ####<Nov 22, 2010 2:51:32 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417692374> <BEA-002635> <The server "NewTradeServer" connected to this server.>
    During this time my admin server in running, i can able to loggin to admin server console,
    Problem which i am faceing is that, i am not able to see the server status of that particular
    manage server, i am not able to see the any sub tabs statistic in Monitoring TAB of manage server, and after 1/2 and hours the manage server stop responding, then i restart the manage server and after that every thing work fine..
    any one have the solution for this error????///
    Regds
    Amar Shaw

    Kindly fing the log for the server problem time.
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.177.97.179:21,557 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.206.128.110:1,069 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 203.123.173.169:50,920 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.180.84.228:50,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,297 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.166.48.41:21,631 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.22.34.38:39,481 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 113.193.25.104:52,294 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.122:18,934 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.241.80.244:24,575 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 196.15.16.20:38,791 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 202.65.136.252:4,055 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,777 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 110.227.109.138:64,362 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.223.187:1,046 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 114.30.77.228:50,110 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.164.238.6:1,935 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 192.20.251.68:41,430 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 195.189.142.85:51,932 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:3,974 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 82.178.3.115:11,545 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.21.153.192:7,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.177.2.33:50,437 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.201.90.244:5,725 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 220.227.95.145:17,067 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.248.137.70:33,786 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:6,260 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.55.98:6,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.162.145.253:1,603 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,443 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,298 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 121.243.135.163:2,342 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,451 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 204.194.141.28:15,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.215.198.169:2,108 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:40,204 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,044 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.241.82.55:50,090 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.134.134:1,079 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.162.69.77:4,185 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:60,708 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 121.245.188.43:1,262 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 125.17.188.19:45,490 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.165.58.249:49,239 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.17.215.126:4,085 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 124.125.27.11:2,992 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:7,639 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.246.47.199:2,426 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.169.70.18:14,392 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:42,408 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.197.237.98:51,852 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.163.89.69:64,984 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 192.20.246.168:13,547 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:37,198 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:39,842 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,450 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.90.72.203:3,972 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:58,671 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,043 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.163.163.25:1,957 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 115.240.50.203:1,059 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.197.42.2:34,187 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.124.135.246:21,650 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 93.186.23.240:11,235 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.133:4,215 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.161.99.67:20,466 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <WebLogicServer> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576578> <BEA-000000> <WebLogic Server "NewTradeServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Notice> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576703> <BEA-170019> <The server log file D:\BEA11G\user_projects\domains\IndiabullsWLS\servers\NewTradeServer\logs\NewTrade_%yyyy%_%MM%_%dd%_%hh%_%mm%.log is opened. All server side log events will be written to this file.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576718> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Diagnostics> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576812> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "http" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "https" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:80
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576968> <BEA-002609> <Channel Service initialized.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576999> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000436> <Allocating 4 reader threads.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000446> <Native IO Enabled.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <IIOP> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577281> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578718> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578796> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_KNcrxQIcWPsGUMqWWNL3mWV+Tkc=>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579203> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579390> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Securit

  • I am trying to download the update IOS 5 version for mi ipad 2 and at the end when it finishes downloading it shows an error "connection has been interrupted and that the task could not be completed", my internet service is fine, what can it be?

    I am trying to download the update IOS 5 version for mi ipad 2 and at the end when it finishes downloading it shows an error "connection has been interrupted and that the task could not be completed", my internet service is fine, what can it be?

    The 2nd generation can not be upgraded beyond 4.2.1.

Maybe you are looking for