Announcement

Collapse
No announcement yet.

Weblogic startup issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weblogic startup issue

    Hi All,
    I start the weblogic.It gets connected to the database.Whenever I click on any link in the UI, i get the results like this(or similar to it.this is one example):
    <Sep 25, 2007 12:02:12 PM PDT> <Warning> <EJB> <BEA-010212> <The EJB 'ejb.ActionDef(Application: ActionDef.jar, EJBComponent: ActionDef)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: home[findByPrimaryKeys(java.util.Vector,java.lang.Objec t), getDataNoLock(glog.util.jdbc.Pk), updateMaxCacheSize(int), onUpdate(glog.ejb.action.db.ActionDefPK,glog.ejb.a ction.db.ActionDefData), findByPrimaryKey(glog.ejb.action.db.ActionDefPK), getLockData(glog.util.jdbc.Pk), listLocks(), findAll(java.lang.Object), listBeansInCache(), getMaxCacheSize(), findByPrimaryKeys(java.util.Vector), findAll(), findInCache(glog.ejb.action.db.ActionDefPK), onCreate(glog.ejb.action.db.ActionDefPK,glog.ejb.a ction.db.ActionDefData), unlock(glog.util.jdbc.Pk), onRemove(glog.ejb.action.db.ActionDefPK,glog.ejb.a ction.db.ActionDefData)] >
    <Info : Runtime deploy producer.Producer>

    Can anyone please tell me whats the error or how to rectify it.
    Thanking and Regards,
    Nikesh.

  • #2
    Re: Weblogic issue

    Nikesh,

    From the error, it isn't possible to tell you exactly what issues you're encountering, but it is likely related to either DB security, your OTM App server installation or the DB schema configuration.

    Did you run the insert_security_roles.sql script after installation? Does the patch level of your OTM installation match that of your database (i.e., have you run the dbpatch_55.sql script after install)?

    Moving forward, I'd do the following:
    • Ensure that you aren't receiving any errors when starting up WebLogic. These would occur in $OTM_HOME/logs/weblogic/console.log and $OTM_HOME/logs/weblogic/weblogic.log
    • Check for errors in your OTM WebLogic console.log file when you click the links.
    • Post more configuration details and error messages here to the forums, so that we can better help you.
    Thanks!
    --Chris
    Last edited by chrisplough; September 25, 2007, 16:45.

    Comment


    • #3
      Weblogic startup issue

      Hi,

      Urgent:Yes.
      Version:5.5 Cu3

      As suggested I have made changes in the 'glog.properties' file.When I enter http://webservername on the browser, I am able to see the error which is displayed in the attached document.
      Also sending you the log files of Weblogic for reference.

      Any help will be highly appreciated.

      Regards,
      Nikesh.
      Attached Files

      Comment


      • #4
        Re: Weblogic issue

        Chris,

        Actually we have a installed environment of 5.5 cu3 .We created a jar file and then installed the jar file on the desktop,to suit the client's requirements.I changed the Db entries in 'glog.properties' file .After that I restarted all the OTM services.And then I get the errorwhich is in the word document.

        Any help will be sincerely appreciated.

        Regards,
        Nikesh.

        Comment


        • #5
          Re: Weblogic issue

          Nikesh,

          I want to ensure that I'm following the details. Can you verify that my understanding is correct:
          1. You installed OTM v5.5 CU3 onto a server, following all of the steps listed in the Administration Guide.
            1. Did the OTM installation work at this point?
          2. You created a jar file of the OTM installation and extracted this onto a clients desktop computer.
            1. What are you and the client trying to accomplish at this point?
          3. You modified OTM's glog.properties file to point towards the OTM database and the listed error occurs.
          If my understanding is correct - then there are multiple issues at hand here:
          1. Each installation of an OTM instance must be done using the OTM installer and moving an install from one computer to another isn't a recommended option. OTM configures itself to many machine-specific variables, including IP address, installation directory, hostnames, platform/architecture, etc.
          2. Most desktop computers don't have enough resources to handle OTM. If running both the OTM Web and App servers on a single box, the minimum amount of recommended memory is 4GB and I highly recommend 8GB.
          Thanks,
          Chris

          Comment


          • #6
            Re: Weblogic startup issue

            Looking at the log files, I can identify a few issues:
            1. Not enough physical memory is installed on the server and it is heavily swapping. You need at least 4GB of memory on this server. (Warning: Your computer has generated 202433 page faults during the last garbage collection. If you find this swapping problematic, please consider running JRockit with a smaller heap.)
            2. Not enough memory is allocated to WebLogic, causing serious performance and functionality issues. (JVM Process has not received any CPU time for 851 seconds. Extending timeouts.)
            3. The same applies to Tomcat
            4. Your app.server property in the glog.properties file may not be correct. The following error indicates that Tomcat is trying to connect to the WebLogic instance on port 7001 and is unable to do so. This may be related tot he above issues. (Machine t3://ossib0069.idc.oracle.com:7001 is not responding)
            I recommend getting more appropriate hardware for the OTM installation first, to resolve the base memory issues and then moving forward from there. Otherwise, you'll have too many simultaneous issues occurring to effectively filter them out.

            Thanks,
            Chris

            Comment


            • #7
              Re: Weblogic startup issue

              Hi All,

              Many thanks for the help.Actually the problem was I started tomcat before the Weblogic started up completely.

              The issue is closed.
              Regards,
              Nikesh.

              Comment

              Working...
              X