Change log.properties without restarting server

Hi ,
Am using OIM9102 with App server WebSphere6.1
How can I handle changing log level in xellerate/config/log.properties file with out restarting server.
Thanks

I don't think this is possible.

Similar Messages

  • How to view the change immediately after a java file is modified without restarting server or redeploy?

              Hi All,
              How to view the change immediately after a java file that is used in jsp is modified
              without restarting server or redeploy?
              Moreover, it is better to keep the original session.
              Any suggestion is appreciated.
              Kammau
              

              Hi,
              In order to have a new version of a java class, the current classloader must be
              deleted and a new one created. This is what redeployment does. I believe that
              this is more of an issue with Sun's implementation of classloaders. You could
              ask BEA support (719.232.7878) and see if they have any plans to periodically
              check jar files to see if java class file timestamps and destroy and re-create
              classloaders on the fly.
              1) You will still have to accept the performance hit of destroying classloaders
              and creating new ones. There isn't any way around that.
              2) I would think you would want to have more explicit control in production and
              integration anyway.
              You can redeploy applications from the command line (script) file not just the
              console.
              Hope this helps,
              pat
              "Kammau" <[email protected]> wrote:
              >
              >Hi All,
              >How to view the change immediately after a java file that is used in
              >jsp is modified
              >without restarting server or redeploy?
              >Moreover, it is better to keep the original session.
              >Any suggestion is appreciated.
              >
              >Kammau
              

  • Can we change VI properties without actually opening it?

    Hi
    I am making executable out of my VI. I wished that the window should close once we exit the program through exit button. Hence I used "Quit Labview" function from Application Control pallette. At the same time inadvertantly I have set the VI properties as "Run when opened" and also disabled "Show run button" and "Show Abort button" options. Now when I open the VI, it starts running, it doesn't show run or abort buttons and when I press exit button to quit the program, it closes the Labview. Now I am unable to edit it's properties. Can any body tell me if there is any way of editing VI properties without actually openig the VI? Thanks and regards.
    Sreedhar Nyapathi

    Alternatively, if you have LabVIEW 8.0 or higher, open the VI from within a LabVIEW project. It will open in edit mode.
    LabVIEW Champion . Do more with less code and in less time .

  • Changing Weblogic Server properties without restarting Weblogic Server

    I have an application that requires a few things to be set at the start of the
    Weblogic server (email addresses,criteria settings, etc.). These are contained
    in a properties file that is referenced in the Weblogic properties file. The
    problem is when I want to make a change in the application property file (change
    an email address, increment a criteria) I have to "reboot" the Weblogic server.
    These defeats the whole purpose of property files. Is there anyway to get Weblogic
    to "recache" the properties files without a Weblogic server "reboot"?
    Thanks,
    Bryan

    I very much doubt that you would be able to refresh the WebLogic properties
    file at run-time (is this WebLogic 5.1 or 6.0 you are talking a about?).
    If you want to be able to update properties run-time (as opposed to
    boot-time) then don't use WebLogic's property file - use either your own
    properties file or store the properties elsewhere such as in the database or
    in JNDI. You will of course have to implement your own refresh algorithm.
    If you are using EJBs then a simple READ-ONLY entity bean with a refresh
    period of a few seconds may suffice.
    Myles
    "Bryan Freed" <[email protected]> wrote in message
    news:3b1e5986$[email protected]..
    >
    I have an application that requires a few things to be set at the start ofthe
    Weblogic server (email addresses,criteria settings, etc.). These arecontained
    in a properties file that is referenced in the Weblogic properties file.The
    problem is when I want to make a change in the application property file(change
    an email address, increment a criteria) I have to "reboot" the Weblogicserver.
    These defeats the whole purpose of property files. Is there anyway toget Weblogic
    to "recache" the properties files without a Weblogic server "reboot"?
    Thanks,
    Bryan

  • How to rotate Apache2.2/logs/access_log without restarting AMS 5.0.1 on AWS.

    The Adobe Media Server 5.0.1 docs say that Logging.xml controls rotating of the Apache access_log file but its not rotating and I don't see how to configure it in Logging.xml.
    Logging.xml takes care of the AMS log files like Access.log but it doens't seem to handle the Apache logs. I've seen where you use logrotated to rotate the Apache logs, then issue a "reload" to the service, but AMS controls Apache and the AMS service only supports start, stop, and reload which takes a minimum of 5 to 10 seconds to reload the server. How can I rotate the Apache logs using Logger.xml or how can I issue a reload directly to Apache when the AMS scripts control it?
    http://help.adobe.com/en_US/adobemediaserver/configadmin/WS5b3ccc516d4fbf351e63e3d119f2926 0bd-7ffa.2.3.html

    To rotate the apache logs you need to pipe them through a third party tool (i saying that there may be something in apache I may have read once, however here is a tried and tested solution assuming you are on linux), Logging.xml is only for FMS (well it was for 4.5.5 and before).
    Download cronolog (http://cronolog.org/)
    Change your log directive
    From: CustomLog "logs/access.log" combined
    To: CustomLog "| /mnt/apps/cronolog/sbin/cronolog -S /mnt/fms/Apache2.2/logs/access_log /mnt/fms/Apache2.2/logs/%Y%m%d_access.log" combined
    Restart apache
    You logs will now roll daily on the first time they are written toie the logs dont roll at midnight, but the first time they are written to after midnight (so if no one access your server on a day, there will be no log for that day)
    The above example makes the assumptiosn:
    FMS apache is installed in /mnt/fms/Apache2.2 and you want to use its log dir
    cronolog installed in /mnt/apps/cronolog/

  • Reloading weblogic.properties without restarting

    Hi,
    I would like to know how to reload the weblogic.properties file without
    having to restart Weblogic. I have already read that the development of a
    class responsible for loading the properties would help, but I don´t know
    how to...
    Thanks in advance,
    SERGIO.

    The easiest way to hot deploy new web-apps is to migrate to WLS 6.0...
    Sergio wrote:
    Hi Robert,
    Thank you for your answer. I´m trying to deploy new webapplications at the
    time that a new request is made and I don´t want to let the other running
    applications without connection when restarting the WebLogic Server. Do you
    know how to make that? Perhaps the solution is to make several null entries
    and deploy pseudo-generations (because they already exist, but empty) of
    webapplications by filling the content of a null entry... But perhaps
    reserves Weblogic a great amount of memory for each null entry, even when
    they are empty...
    Thanks a lot,
    SERGIO
    "Robert Patrick" <[email protected]> wrote in message
    news:[email protected]..
    The WebLogic Server will only read the weblogic.properties file atstartup.
    You cannot force WebLogic to re-read the rpoperties file withoutrestarting
    the server. What are you trying to do that requires theweblogic.properties
    file to be re-read? There may be some other way of accomplishing what you
    are trying to do...
    Sergio wrote:
    Hi,
    I would like to know how to reload the weblogic.properties file without
    having to restart Weblogic. I have already read that the development of
    a
    class responsible for loading the properties would help, but I don´tknow
    how to...
    Thanks in advance,
    SERGIO.

  • EJB Reloading without restarting server

    Does anyone know how to activate class reloading for EJBs in Weblogic
    6.1 (sp1)?
    It works for servlets, but there does not seem to be any options in
    the Admin console to set this.
    Compiling a new class file and overwriting the old one, doesn't work
    unless you restart the server.

    Production mode turns it off. Development mode turns it on.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Humphrey" <[email protected]> wrote in message
    news:[email protected]..
    Does anyone know how to activate class reloading for EJBs in Weblogic
    6.1 (sp1)?
    It works for servlets, but there does not seem to be any options in
    the Admin console to set this.
    Compiling a new class file and overwriting the old one, doesn't work
    unless you restart the server.

  • How to make changes effect in log4j.xml without restarting weblogic server

    Hi ,
    I have successfully configured log4j in my weblogic server 8.1.
    Everytime i made a change in log4j.xml i need to restart the server
    is there any configuration or parameter to set without restarting server??
    Thanks in advance,
    CK

    I don't think you need to restart the server, atleast I never needed to when making changes to jsp pages. You only need to restart when you make changes to java classes. Some might argue jsp is converted to servlet which is a java class.....
    Try refreshing the page when you make any changes. This works for me, if it doesn't work try turning reloadable="true" in your context path in tomcat's server.xml

  • Passing Properties Without Code Change and Server Bounce.

    Hi All,
    I need a way where I can specify properties/values such that I can change it on the fly, and my ADF Web App can pick it straight away without any server bounce and code change in the ADF App.
    For example, we want to send emails so we want to keep subject and mail text is some place from where ADF app can pick it up without any code change or server bounce.
    I tried Mail Session JNDI, but there I need a re-start for the app to pick up latest properties.
    Is there a way to implement it?
    Thanks.

    Hi,
    There are several ways todo this.
    The simplest would just be a database table with configuration.
    read your parameters from there, and dont cache them if you want changes to be picked up.
    Another way would be a deployment plan and specify the values as init parameters for the application.
    But an update of the plan does mean the application is not accessible for a very short time.
    -Anton

  • How to make changes runtime in ApplicationResources.prop without restarting

    hi,
    We are using Oracle App. server 10g server. Our application is so critical, we can not restart server frequently for small changes. Our client might need to change error message and other user message on regular basis. We use ApplicationResources.properties for messages. How we can update these messages at run time without restarting app server. Is it possible in Oracle App. Server. I know it is possible on JBOSS but not sure about Oracle App. Server.
    I tried to copy ApplicationResources.properties in application folder on server, but it does not give effect. Generally, we used to do this with JBoss server, but I am new to Oracle App. server, is it possible? If possible - how?
    I checked with my other team members, they are not sure. I also tried to find Java ranch and also other forums without success. your input might be very useful.
    One probable solution is to access these messages from database, but do we have any other option if we want to use ApplicationResources.properties ?
    Thanks in advance.

    Hi,
    FBZP includes many activities. Some of them could be maitained directly in production. What activity do you refer to? Anyway, if this activity is locked for customizing in production, there are, generally, two ways to deal with this:
    a) open the client through SCC4
    b) changing the maintance preferences for the table/view in question
    In both case, you should consult your BASIS team first.
    Regards,
    Eli

  • Reload a jar in weblogic server without restart

    Hi All,
    We are using weblogic version '10.0.1.0' and have 'reports.jar' file in server for reports.
    If we change any existing class file under 'reports.jar' then we are using below steps in order to recognize a modified jar by weblogic
    1) We need to recreate a jar using eclipse in local IDE and
    2) Copy the 'reports.jar' into server
    3) Need to restart server inorder to recognize the modified jar
    Is there any alternative solution to reload a jar in weblogic server without restart?
    Please do the needful.
    Thanks & Regards,
    Gangadhar

    Hi,
    If this is for weblogic running on development mode, then you can go for auto-deployment feature where weblogic will auto-deploy modified application from autodeploy directory.
    For production mode, you can go for production-redeployment feature of weblogic where it uses application versioning. So for example you deployed webapp1 with version app1.0 and then for new release you will deploy webapp1 with version app2.0 adding a retirement policy to retire old application after said time and start using webapp1 with app2.0.
    Refer to link for mode detail - http://middlewaresupport.wordpress.com/2013/03/21/production-redeployment-feature-in-weblogic/
    rank it if found useful
    Thanks,
    Ranjan

  • Modify JSP file without restarting the server

    Hi guys,
    I need to do small change in the JSP in the production.
    How can I do it without restarting the server?
    I have deployed the application as an EAR file.
    I use WLP8.1 SP3
    IS there any way?
    Ananth

    You can try expanding (use jar util) that ear into temp dir, then make the change, use jar util again to create the ear. try redepolying it. Make sure change the jsp recheck and hit that page. see if it works. Incase if it works put the jsp recheck back to -1.
    Note: This is just an idea, I never done.
    Thanks
    Srini

  • About change the resposity manager configuration without restart J2eeServer

    HI all, I have a question about deploy my resposity manager.par to the netweaver.After deployment,configuration ,my resposity manager works well .But I want to change my resposity manager configureation such as
    change the  Prefix etc,usually it needs to  restart netweaver server to take effects,is there any way I don't need to restartserver to take effects.
    For example:
    At the begin my resposity prefix is  a,then I will see the a folder in the KM content.I want to change the prefix b,but I don't want to restart the server,I hope I change to b,I will see the foled b in the KM content
    right now,can anyone tell me how to do ?Because restart j2ee server need a long time.

    Hi,
    Changes to properties that appear with a star symbol in KM Configuration need a server restart, so that these changes apply.
    So no way except to restart.
    Also check this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bb1f18be-0801-0010-ffa0-e3495f7401bc
    Regards,
    Praveen Gudapati

  • Is there any way to restart Agentry Server without restarting SMP3.0 server?

    Hello Experts,
    Is there anyway to restart Agentry server, without restarting SMP server? I want to modify the setting of Agentry app and restart the Agentry to make change effective. Each time I restart Agentry, I have to restart the SMP3.0. It is very inconvenient.
    Please assist me on this issue. Thank you very much.

    That is something I believe they are working on for the next SP release (along with multiple Agentry apps on the same SMP 3 server).  I don't know if there is an offical way to do this but will see if I can get any answer.
    --Bill

  • Deployment without restarting the server

    If we change java files,why we need to restart the server,I am using JBoss-2.2.1_Tomcat-3.2.1.Can we deploy the java file without restarting the server?Thanks in Advance

    Yes we may
    All u need to do is change
    TOMCAT: %WEBSERVER_HOME%\conf\context.xml
    JBOSS: %WEBSERVER_HOME%\server\default\deploy\jbossweb-tomcat55.sar\context.xml
    file from
    TOMCAT:
    =======
    <!-- The contents of this file will be loaded for each web application -->
    <Context >
        <!-- Default set of monitored resources -->
        <WatchedResource>WEB-INF/web.xml</WatchedResource>
        <!-- Uncomment this to disable session persistence across Tomcat restarts -->
        <!--
        <Manager pathname="" />
        -->
    </Context>To
    <!-- The contents of this file will be loaded for each web application -->
    <Context reloadable="true" >
        <!-- Default set of monitored resources -->
        <WatchedResource>WEB-INF/web.xml</WatchedResource>
        <!-- Uncomment this to disable session persistence across Tomcat restarts -->
        <!--
        <Manager pathname="" />
        -->
    </Context>JBOSS :
    ======
    <!-- The contents of this file will be loaded for each web application -->
    <Context cookies="true" crossContext="true">
       <!-- Session persistence is disable by default. To enable for all web
       apps set the pathname to a non-empty value:
       <Manager pathname="SESSIONS.ser" />
       To enable session persistence for a single web app, add a
       WEB-INF/context.xml
       -->
       <Manager pathname="" />
       <!-- Install an InstanceListener to handle the establishment of the run-as
       role for servlet init/destroy events.
       -->
       <InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener>
    </Context>to
    <!-- The contents of this file will be loaded for each web application -->
    <Context reloadable="true"  cookies="true" crossContext="true">
      <!-- Session persistence is disable by default. To enable for all web
       apps set the pathname to a non-empty value:
       <Manager pathname="SESSIONS.ser" />
       To enable session persistence for a single web app, add a
       WEB-INF/context.xml
       -->
       <Manager pathname="" />
       <!-- Install an InstanceListener to handle the establishment of the run-as
       role for servlet init/destroy events.
       -->
       <InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener>
    </Context>

Maybe you are looking for