4 Replies Latest reply: Feb 27, 2013 7:21 AM by Kishore Rout RSS

    unable to start services after installin weblogic 10.3.6

    user140307
       
        • 1. Re: unable to start services after installin weblogic 10.3.6
          Kishore Rout
          Please paste the error if you are getting anything.
          • 2. Re: unable to start services after installin weblogic 10.3.6
            user140307
            There are 1 nested errors:

            weblogic.management.ManagementException: Unable to obtain lock on /u03/app/appp/weblogic/user_projects/domains/base_domain/servers/http:/jos2.jacmel.com:7010/tmp/http:/jos2.jacmel.com:7010.lok. Server may already be running
            at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:206)
            at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:67)
            at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
            at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
            at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
            at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
            at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
            at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
            at weblogic.Server.main(Server.java:71)

            >
            • 3. Re: unable to start services after installin weblogic 10.3.6
              user140307
              Hi Kishore,

              i started using sh startWebLogic.sh and it returned the following error.

              <Feb 27, 2013 7:40:55 AM EST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
              <Feb 27, 2013 7:40:55 AM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[3]". The address 0:0:0:0:0:0:0:1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
              <Feb 27, 2013 7:40:55 AM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[2]". The address 127.0.0.1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
              <Feb 27, 2013 7:40:55 AM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 192.22.222.25 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
              <Feb 27, 2013 7:40:55 AM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[1]". The address fe80:0:0:0:2e76:8aff:fe51:f0e0 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>



              but i have changed the port from 7001 to 7010 in config.xml file as there is another service running on 7001 port.
              • 4. Re: unable to start services after installin weblogic 10.3.6
                Kishore Rout
                Hi,
                May be the server is running in previous session. Make sure that the server which started earlier shoud be properly stopped or kill the process id usig "kill -9 pid" command. For changing the port from backend please find the below steps.

                Steps:
                1. Browse to the config.xml file for the domain:
                •Within each domain you will find a config folder (for example, \Middleware_Home\user_projects\domains\<DomainName>\config, and there you will find a config.xml file.
                2. Open the config.xml file in a text editor.
                3. Browse to the <server> element.
                4. Find the AdminServer and change the listening port (between the <listen-port> element) to an unused port.
                5. Save and close the file, then restart the Admin Server domain. It will not be started on the new port configured in Step 4.

                Mark if this helps you.

                Regards,
                Kishore