WTC Trace level without server restart

Hi,
I am using WLI/WLS7.0SP2 to connect to eLink1.2/Tuxedo6.5 through WTC. Is there a way to enable WTC trace level without having a server restart ?
Thanks,
Suresh

Hi Suresh,
If you could open a support case and ask the support engineer to contact me, I believe I can provide an unsupported mechanism to do this.
Regards,
Todd Little
BEA Tuxedo Engineering

Similar Messages

Updating policies and Policy Database or Policy Updates without server restart

Hi again,
I have implemented the flash access reference implementation server including setting up all example database tables (so we have a central database server). I have started updating policies for the application "whitelist" features and have run into some questions below.
The Protecting Content documentation states:
 "If your license server has access to a database for storing policies, you can retrieve the updated policy from the database and call LicenseRequestMessage.setSelectedPolicy()"
This leads to two questions:
1) The reference implementation doesn't store any Policies in the database (it stores them on the filesystem in the Resources Directory). I can not find any documentation or examples of how to "retrieve the updated policy from the database". Can somebody please point me to an example or documentation on how to store policies in the database so I can simply LicenseRequestMessage.setSelectedPolicy()?
2) As the reference implementation stores policies on the disk I had to use policy update lists when I whitelisted an AIR app. However, the reference server did not honor the policy update list till I restarted the flash access reference server. How can I notify the flash access server of the change to the update policy list without restarting the server?
Thank you,
-R

Hello,
Please see my answers below.
Answer 1>
If you want to store the binary representation of the policy in the database, you can invoke Policy.getBytes() and store the returned byte[] as a blob in the database. For details on how to store such binary data in a database, you should consult the documentation for you database. Then, to rebuild a policy that had been stored in a database, you can obtain the byte[] stored in the database, and invoke new Policy(byte[]) with it to reconstruct that policy instance.
See the following javadocs:
 * Retrieves an encoded byte array representation of the policy.
 * If this <code>Policy</code> was created from an empty constructor, the revision number
 * will be <code>1</code>. If this was an existing policy and changes were made to the policy,
 * the revision number will be incremented by one. Otherwise, the revision number will not change.
 * The validity of the policy is first checked before encoding into a byte array. Encoding will fail
 * if {@link #checkValidity()} throws an exception.
 * @return A serialized representation of the policy.
 * @throws PolicyModificationException The <code>Policy</code> cannot be serialized because it was created with a newer version and was modified.
 * @throws PolicyException The <code>Policy</code> is missing required fields or contains conflicting entries.
 * @throws EncodingException Unable to encode the <code>Policy</code> to a byte array.
 public byte[] getBytes() throws PolicyException, EncodingException;
 * This constructor parses an existing policy from the given byte array.
 * @param policy The policy from which to construct this <code>Policy</code>.
 * @throws EncodingException Unable to parse the byte array into a <code>Policy</code>.
 * @throws PolicyException The <code>Policy</code> is missing required fields or contains conflicting entries.
 public Policy( byte[] policy ) throws PolicyException, EncodingException;
Answer 2>
In order to implement automatic configuration updates of policy update lists on the flash access server, you will need to tweak the Reference Implementation code, to monitor the file update state and re-load the PolicyUpdateList if it changes. The code snippet below, taken from the com.adobe.flashaccess.refimpl.util.ParamsReader.buildHandlerConfiguration() method, should serve as an example of how the PolicyUpdateList is loaded and then set on the HandlerConfiguration instance for it to take effect for a particular license acquisition request. In the case of the reference implementation, this code (below) is only invoked once, during server initialization. That is why a server restart is necessary for subsequent changes to take effect. However, nothing prevents this code form being invoked elsewhere, and that implementation is entirely upto the customer, to achieve the desired outcome.
 PolicyUpdateList pul = PolicyUpdateListFactory.loadPolicyUpdateList(pulInputStream);
 if (pul != null)
 X509Certificate issuerCert = null;
 if (hsmEnabled)
 issuerCert = getHSMCertificate(props, hsmUtils, "RevocationList.verifySignature.X509Certificate");
 else
 String pulSignatureCertFile = props.getProperty("RevocationList.verifySignature.X509Certificate");
 if (pulSignatureCertFile != null)
 InputStream pulSignerInputStream = new FileInputStream(resourcesDir + pulSignatureCertFile);
 issuerCert = CertificateFactory.loadCert(pulSignerInputStream);
 if (issuerCert != null)
 pul.verifySignature(issuerCert);
 context.setPolicyUpdateList(pul);
Regards,
Safdar

Par application - Trace level=all after j2ee restart

Hello,
I'm not sure that is the right place to post this question so, don't hesitate to root me to another thread.
We use the SAP Enterprise Portal EP6 base on NW2004 SPS16.
We have developped some Portal Application. (par). Those applications contain a logger.xml file to describe the trace settings.
In visual Admin\Log configurator, we define the trace level to "Error" for those applications nodes. But, after application deployment, or after j2ee engine restart, the trace level level is automaticaly set to "All". It only appens to our applications and not to other WAS traces.
I think problem is due to the logger.xml but, after lookup on a lot of thread, it seems we use it in the good way.
eg:
<Server>
<Logger name="corp.mycompany.application.myApplicationName.logger"
 loggerInterface="com.sapportals.portal.prt.logger.ILogger"
 locationName="corp.mycompany.application.myApplicationName"
 pattern="%d # %20t %15s %m #"
 isActive="true">
 <LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="Error">
 </LoggerClass>
</Logger>
</Server>
Did we miss something ? Do we manage our traces in thge good way ?
Please advice.
Thanks for your support
Laurent

Laurent,
Do have a look at this<a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1794">weblog</a>
check this
<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f04b290-0201-0010-1387-d2df53065422">pdf</a>
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e2/75a74046033913e10000000a155106/frameset.htm">Active Tracing</a>
Are all the configurations nd settings done are accordingly?
Thanks,
Swathi

How do I increase the trace level of the dev_server file?

I have a dual stack SCM system and the java stack will no longer start. I'm seeing some messages in the dev_server0 and dev_server1 files, in the work directory. But at the top of those files, it says the current trace level is at 1. I would like to have some further details as to the error. How do I increase the trace level of these files? Thank you.
~TJ

You can increase the trace level by changing the instance profile
set "jstart/TRACE = 3", (this affects the server0 process)
set "rdisp/TRACE = 2" (this affects the ICM).
Then Restart the ICM and the server process (e.g. from the SAP MMC -
there is no need to restart the entire instance),
hope this helps.
Regards
SuneeL

Reload of composite on server restart

Hi,
We have a processes which is invoking some 5 to 6 other bpel processes.On server restart this dependent process is getting loaded first ,i.e prior to the load of other bpel processes.So the reload is failing with :
The composite OrderRespOAppProcessSrvc (1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.
Error occurred during deployment of component: OrderRespOAppProcessSrvc to service engine: implementation.bpel, for composite: OrderRespOAppProcessSrvc: ORABPEL-05250 Error deploying BPEL suitcase. error while attempting to deploy the BPEL component file "D:\SOA_Middleware\user_projects\domains\dev_domain\servers\soa_server1\dc\soa_4b0a73b3-5a1e-4ab2-b7b7-41bb8f392586"; the exception reported is: java.lang.IllegalStateException: this is only a psuedo object This error contained an exception thrown by the underlying deployment module. Verify the exception trace in the log (with logging level set to debug mode). 
oracle.sysman.emSDK.app.exception.EMSystemException
 at oracle.sysman.emai.model.sca.composite.core.impl.EMCompositeModel.handleErrorDetails(EMCompositeModel.java:83)
 at oracle.sysman.emai.model.sca.share.composite.CompositeCoreModel.initialize(CompositeCoreModel.java:122)
 at oracle.sysman.emai.model.sca.composite.core.impl.CompositeModel.initialize(CompositeModel.java:46)
 at oracle.sysman.emai.model.sca.EMEntityModel._initializeEntityData(EMEntityModel.java:28)
 at oracle.sysman.emai.model.sca.common.SCAEntityObject.initializeSCAData(SCAEntityObject.java:124)
 at oracle.sysman.emai.model.sca.composite.core.impl.EMCompositeModel.initializeSCAData(EMCompositeModel.java:31)
 at oracle.sysman.emai.model.sca.SCAObject.initializeData(SCAObject.java:62)
 at oracle.sysman.emSDK.model.EMObject.reset(EMObject.java:216)
 at oracle.sysman.core.model.util.ModelUtil$EMObjectResetter.initOrResetEMObject(ModelUtil.java:328)
 at oracle.sysman.core.model.util.ModelUtil$EMObjectResetter.access$000(ModelUtil.java:280)
 at oracle.sysman.core.model.util.ModelUtil.initializeMBEMObjects(ModelUtil.java:231)
 at oracle.sysman.core.model.util.ModelUtil.initializeAllEMObjects(ModelUtil.java:128)
 at oracle.sysman.core.model.util.ModelUtil.initializeAllEMObjects(ModelUtil.java:101)
 at oracle.sysman.emSDK.view.util.RefreshBean.refreshPageData(RefreshBean.java:91)
 at oracle.sysman.emSDK.view.util.RefreshBean.refreshPage(RefreshBean.java:73)
 at oracle.sysman.emai.view.sca.common.EMNavigationHandler.refreshPage(EMNavigationHandler.java:677)
 at oracle.sysman.emai.view.sca.composite.core.EMCompositeInstancesView.dataChanged(EMCompositeInstancesView.java:119)
 at oracle.sysman.emai.model.sca.share.composite.CompositeInstances._fireDataChangedEvent(CompositeInstances.java:194)
 at oracle.sysman.emai.model.sca.share.composite.CompositeInstances.getDataModel(CompositeInstances.java:158)
 at sun.reflect.GeneratedMethodAccessor971.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at javax.el.BeanELResolver.getValue(BeanELResolver.java:261)
 at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:173)
 at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:200)
 at com.sun.el.parser.AstValue.getValue(Unknown Source)
 at com.sun.el.ValueExpressionImpl.getValue(Unknown Source)
 at org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty(FacesBeanImpl.java:68)
 at org.apache.myfaces.trinidad.component.FacesBeanWrapper.getProperty(FacesBeanWrapper.java:58)
 at org.apache.myfaces.trinidad.component.UIXTable$RowKeyFacesBeanWrapper.getProperty(UIXTable.java:594)
 at org.apache.myfaces.trinidad.component.UIXComponentBase.getProperty(UIXComponentBase.java:1194)
 at org.apache.myfaces.trinidad.component.UIXIterator.getValue(UIXIterator.java:706)
 at org.apache.myfaces.trinidad.component.UIXCollection._flushCachedModel(UIXCollection.java:1386)
 at org.apache.myfaces.trinidad.component.UIXCollection.encodeBegin(UIXCollection.java:515)
 at javax.faces.component.UIComponent.encodeAll(UIComponent.java:928)
 at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
 at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
 at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
 at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeCenterFacet(PanelStretchLayoutRenderer.java:769)
 at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeCenterPane(PanelStretchLayoutRenderer.java:1140)
Is there any way to control the reload of processes when server is restarted.

Hi sab2,
There seems to be no reason for error if you have used correct Abstract WSDLs from the MDS in your composite.xml. The best way to check this is to do a Search for hostname in the entire project and ensure that the host-specific URLs exist only in the composite.xml that too in tags starting with *<binding.ws*. Any other WSDL references e.g. in composite namespaces, in Transformation files Source/target namespaces etc. can be replaced with the abstract WSDLs references.
The task is not done yet. You need to further create the configuration plans corresponding to each server environment where your composite would be deployed e.g. DEV_config_plan.xml, PROD_config_plan.xml. These config plans would replace the concrete locations in your composite.xml at the deployment time.
Also have another issue when we move the jars from dev to prod i see the endpoint on MDS is modified
PROD endpoints but after the process is deployed it still has the Endpoint pointing to Dev URL.
I dont see it any where on the MDS and the Composite WSDL.Are you using proper config plans? If not please use one.
The Process we use to migrate the code from DEV to PROD is by exporting jars from the
DEV instance and deploying them on PRD instance, does this have any effect on the endpoint pointing to the DEV URLI'm not sure about this approach as per the recommended approaches. You can however, use the same deployable JARs and deploy from the FMW console by selecting the appropriate configuration plan.
Regards,
Neeraj Sehgal

JDBC Connection pool recovery after DB server restart

I am finding that Kodo is throwing the following exception after I restart
my database server (mysql). I am doing the database server restart while my
application server is idle, so it is not during a transaction.
Communication link failure: java.net.SocketException [code=0;state=08S01]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code? For example, WebLogic Server's JDBC connection pool has a setting that
enables testing a connection and recovering from such failures before
allocating it from the pool.
Ben

This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code?Not right now. You can log an enhancement request with our bug database:
http://bugzilla.solarmetric.com/

Missing data after server restart

Hi,
We restarted our MDM server at the OS level last night. Everything seemed okay after the restart. However, when our users came in this morning, they found that some data was missing from a table. We have a Material repository with 3 main tables. Some data which have previously been populated was not appearing in our Products Detail table, the largest of the three. A large number of rows in the table had columns that failed to load with data on the repository auto-start that occured after the server restart. The auto start value in the mds.ini file was set at 300 (5 minutes) as we had seen this iisue happen once before, and thought that may help.
A stop and restart of the repository corrected the issue. Is there anything we could have done to prevent this? Is it worthwhile to try increasing the auto start delay again? Validating detail data after every server restart is not an effective option.
MDM version: 7.1 SP08
OS: AIX DB: Oracle 11g
Thanks!
Dave

Hi Dave,
I meant that when you load repository using Immediate data is loaded from .acl files (accelerator files) in a async manner.
Whereas when you load by Update Indices new acl files are generated.
Below men6tioned is a comparision between the 2 ways of laoding repository:
Load Repository Immediate
o Loads indexes from accelerator files instead of being regenerated by reading the data them from the DB and creating the index.
o Automatically builds indexes stored in out-of-date accelerator files.
o Is usually fast.
 Load Repository with Update Indices
o Rebuilds all MDM indexes files by reading and indexing data stored in the DB. The results are flushed on disk as accelerator files.
o Necessary by repository schema changes or if any error occurs.
o Might take significant amount of time to complete.
So when you observe some visual data impact in your repository it is good idea to rebuild indexes.
I guess we cannot schedule this as default behavior is to load by immediate even through the inin parameter.
as a best practice one can do this by fixing a time frame eg monthly depending on data/schema changes.
Thanks,
Ravi

Best Practice to troubleshoot a Crawler Issue after SQL Server restarts

Hi Everyone
I am after some general advice or a suggested place to start when troubleshooting crawler issues after an unplanned, out-of-sequence server restart.
Specifically, the SQL Database in the SharePoint 2010 farm. Better yet, is there a standard practice way of resolving such issues?<o:p></o:p>
So far articles I have found suggest options from reviewing the crawl logs, creating a new crawl component, right through to using fiddler to monitor the crawler.
Are these sufficient places to start / methodologies to follow, what else should be considered?
Any advice greatly appreciated.
Thanks,
Mike

Well, as I said before, there are lots of different potential issues & resolutions for crawlers. It really depends on the issue. I would say that the base troubleshooting steps start the same no matter which service/feature you are looking
at. So, I'll try to keep this sort of generic, but beyond finding the details of the problem, the SOP or process will vary greatly based on what the error is. I hope this helps, and sorry if it's not specific enough.
1 - check the ULS logs
2 - check the windows application logs
3 - verify related services are running (get-spserviceinstance), possibly stop/start them to reprovision the instance on the affected server
4 - clear the config cache (this alone will clear about 30% of your basic problems)
6 - verify disk space & resource consumption on affected server (& SQL, SQL is always the potential to be the true "affected" server)
7 - iisreset
8 - verify connectivity between all servers in the farm and SP
9 - verify requir3ed features activated
10- check if any changes were made to environment recently (new hardware, updates to OS or apps, updates to GPOs, new solutions, etc)
11- check if the issue is reproducible in another environment (only reliable if this is a similar environment, i.e. same patch level test farm or dr farm). see if it occurs in other site collections within the web app, different web apps, different
servers/browsers, etc, basically just try to nail down the scope of the problem
There is a whole slew of thiings you could check from verifying certificates & perms, to rerunning psconfig, to checking registry keys, again I go back to it depends. hopefully this can get you started though. in the end ULS is where all
the real info on the issue is going to be, so make sure you check there. don't go in with tunnel vision either. if you see other errors in ULS, check them out, they may or may not be related; SharePoint is an intricate product with way more moving
parts than most systems. fix the little quick ones that you know you can handle, this will help to keep the farm clean and healthy, as well as crossing them off the list of potential suspects for your root cause.
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Unable to set trace level

Hello,
I have a problem with the trace level (by trace level I mean this one: http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/tracing_logging.html) in the Java Console when deploying a Java Applet.
With "Next Generation Java Plugin" (JPI >= 1.6.0_10) disabled I am able to set a trace level (0-5) in the java console; if it is enabled I am not able to set a trace level. The Problem is: it seems all outputs written to the Java Console seem to be added to one string, so if there are many trace messages in the java console you'll get a OutOfMemoryException.
And to make things even better: with JPI 1.6U19 and U20 I am not even able to disable the "Next Generation Java Plugin" (well theoretically I am but it seems to ignore my settings).
Also adding Applet Parameters (-Djavaplugin.trace=false -Djavaplugin.trace.option=off) for setting tracelevels has no effect, I get trace messages for loading resources etc. in the java console (Stating "image loaded: jar:http://what.ever.else/some.jar!some.image").
I tested with various Java Plugins (1.6U17, U19 and U20) and various Browsers (IE6 and Firefox 3.5) on WinXP SP2 with no difference.
Does anybody have a clue how to turn off this tracing permanently as it fills up my heap?!?
cheers
Christian

Where exactely did you change the localisation to US and has this to be done on every client running the web interface or just the server it's running on?

XSJS Tracing - Trace files do not show trace levels other than 'error'

Hi!
I'm doing some experiments with server side javascript tracing on Hana. I created a small xsjs file that searches for some parameters on the web request (first name, last name and email) so I can call a DB procedure later. As I wanted to make sure that client data was arriving to the server properly, I added some trace calls using $.trace as you can see in the snipped below.
After some time I noticed that just $.trace.error calls were added to xsengine*trc trace files. In other words, information, debug and warnings were not being included on the trace files.
$.trace.info("INFO: Register_user.xsjs called");
$.trace.error("ERROR: Register_user.xsjs called");
if($.request.method === $.net.http.POST || $.request.method === $.net.http.GET) {
    var first_name = $.request.parameters.get("first_name");
    var last_name = $.request.parameters.get("last_name");
    var email = $.request.parameters.get("email");
    $.trace.error("ERROR: First Name:" + first_name);
    $.trace.error("ERROR: Last Name:" + last_name);
    $.trace.error("ERROR: Email:" + email);
    $.trace.warning("WARNING: First Name:" + first_name);
    $.trace.warning("WARNING: Last Name:" + last_name);
    $.trace.warning("WARNING: Email:" + email);
    // send response
    $.response.contentType = "application/json";
    $.response.status = $.net.http.OK;
    $.response.setBody(" { \"message\" : \"User registered successfully\"} ");
} else {
    // unsupported method
$.trace.error("ERROR: Method was not POST");
    $.response.status = $.net.http.INTERNAL_SERVER_ERROR;
A small piece of a xsengine*.trc file is shown below.
[4940]{-1}[-1/-1] 2014-09-08 20:37:10.453384 e xsa: demo.user_c register_user.xsjs(00026) : ERROR: Register_user.xsjs called
[4940]{-1}[-1/-1] 2014-09-08 20:37:10.453690 e xsa: demo.user_c register_user.xsjs(00037) : ERROR: First Name:war
[4940]{-1}[-1/-1] 2014-09-08 20:37:10.453710 e xsa: demo.user_c register_user.xsjs(00038) : ERROR: Last Name:ning
[4940]{-1}[-1/-1] 2014-09-08 20:37:10.453796 e xsa: demo.user_c register_user.xsjs(00039) : ERROR: Email:[email protected]
[4940]{-1}[-1/-1] 2014-09-08 20:58:21.854254 e xsa: demo.user_c register_user.xsjs(00024) : ERROR: request path: /demo/user_creation/logic/register_user.xsjs
[4940]{-1}[-1/-1] 2014-09-08 20:58:21.854285 e xsa: demo.user_c register_user.xsjs(00026) : ERROR: Register_user.xsjs called
Here are my doubts:
Is there any standard filter for trace calls (which for example would show just error messages as default)? If there is, where to change it?
Are there separate trace files for each trace level?
Looking at the beginning of each row on the trace file, are the numbers from the left side of the timestamp somehow relevant to determine what kind of trace leve is shown? What do they mean? (the sequence of [4635]{-1}[-1/-1] )
Related (and useful) links which couldn't solve the problem:
How to print from XSJS to Console
JSDoc: Namespace: trace
I'm using:
Cloudshare (SAP HANA SPS6 server)
Hana Studio Version: 1.80.3
Thanks for the support!

Hi Fabio,
You need to do some configurations. Please have a look at Trace Server-Side JavaScript Applications - SAP HANA Developer Guide - SAP Library and View XS JavaScript Application Trace Files - SAP HANA Developer Guide - SAP Library
Best regards,
Wenjun

Configuration variable for menu changes avoiding server restart

Hi,
After editing/hiding a menu item (in coremenuitems()), is there a configuration variable that helps to immediately reflect the same thereby avoiding server restart.
Thanks in advance
Ramesh
Edited by: 845556 on 30 Aug, 2012 1:45 AM
Edited by: 845556 on 30 Aug, 2012 1:50 AM

Hi Atheek,
There is no way to do this without restarting the Server...
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

OSB Server restart

Hello,
I made some changes to WSDLs and Service using OSB web console in Admin server. The Admin Server has two managed servers.
When I activated the changes, it says "Server(s) require restart before session can be activated."
Similar action I performed in other env got immediate effect without prompting for server restart.
Could you please tell me what are the cases that server(s) restart are required when changes are made via osb console.
Thanks

You would get that message in Service Bus Console if you made any non-dynamic configuration changes earlier through Weblogic Console and didn't restart the server. The reason for this behavior is as follows:
Changes to non-dynamic configuration attributes require that the affected servers or system resources be restarted before they become effective. If a change is made to a non-dynamic configuration setting (For exampl, certain JMS configuration modification), no changes to dynamic configuration settings will take effect until after restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated.
For details, please refer to Weblogic Administration guide in the link below and look at the section for dynamic and non-dynamic changes.
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/intro/console.html
Hope this helps.

Production server restarted automatically

Hi ,
I am new to the production enviorment .
Our production server restarted automatically ,i am unable to find out the reason.
Where we can see the log for cause of restart .
IN SAP SERVER/OPERATING SYSTEM LEVEL .
Ths is on very urgent basis
Hoping earliest response.
Thanks in advance .
RohitK

Message was edited by:
Rohit Kawankar

Hi Manoj,
Thanks for your reply ,
My current configuration is ecc 5 ,oracle 9i ,win2k3 .
I had checked in sm21 ,but i did not found anything related to restart of server .
What are all checks where i can find the log to analysis the problem.
Thanx & Regards
RohitK

Work Porcess Trace level - 2 - Any little penalty on Performnace due to it?

Hello......Experts
We normally observe , Incidentally on some application server, some one work process Trace level is switched to "2" which in turn shows "YELLOW" in SM50.
Q1 - When this automatic Trace level is increased of a Work Process ?
Q2 - When work process Trace level increased, some extra logging will take place...Will it create any little penalty ( negotiable) on over all application server performance ?
Rgds
PR

Hi PR,
Q1) The trace level should not increase automatically for a long time. When some processes crashes, the trace is increased automatically just to log this error and then is switched back to 1 (this should not take more than 1 or 2 seconds). There is also a known issue described in note 1515602 where the traces increase automatically.
Q2) It could have some impact as the system will be constantly recording data on the OS level, you could have some performance degradation due to excessive I/O and also some penalty about disk space.
Cheers,
Maurício

ITS Trace level

Hi,
We have a dual-host ITS instance 6.20. The Wgate is placed in the DMZ and can't be managed by ITS Administrator (ITS Administrator is behind the firewall)
How can I change ITS Trace Level for the Wgate in DMZ?
Is there some kind of config file?
Thx in advance.

Hi Brian,
you can change the tracelevel in .../SAP/ITS/6.20/config/ItsRegistryWGATE.xml in section Traces. Make sure to restart wgate.
Best regards,
Klaus

WTC Trace level without server restart

Similar Messages

Maybe you are looking for