Labels

Sunday, January 26, 2014

How to copy the value of a user-defined field in Test Plan to a user-defined field in Test Lab

This VBScript Workflow example will populate a test lab test instance user-defined field (TC_USER_01), with the value of a test plan user-defined field (TS_USER_01) of the corresponding test.


Sub TestSetTests_MoveTo
  TestSet_MoveTo
  TestSetTest_Fields("TC_USER_01").IsReadOnly = True
End Sub

Sub TestSet_MoveTo
    On Error Resume Next
    Dim td
    Dim testSetF
    Dim testSet1
    Dim testSetTestF
    Dim tstestL
    Dim tsTest
    Dim tFactory
    Dim tItem
    Set td = TDConnection
    Set testSetF = td.testsetFactory
    Set tFactory = td.TestFactory
    Set testSet1 = testSetF.Item(TestSet_Fields.Field("CY_CYCLE_ID").Value)
    Set testSetTestF = testSet1.TSTestFactory
    Set tstestL = testSetTestF.NewList("")
    For Each tsTest in tstestL
        'check if the UDF of the test instance is empty

        If Len(tsTest.Field("TC_USER_01")) = 0 Then
            Set tItem = tFactory.Item(tsTest.Field("TC_TEST_ID"))
            tsTest.Field("TC_USER_01") = tItem.Field("TS_USER_01")
            tsTest.Post
       End If
    Next
    On Error GoTo 0
End Sub

Thursday, January 23, 2014

SEVERE: Servlet.service() for servlet cgi threw exception

SEVERE: Servlet.service() for servlet cgi threw exception
java.io.IOException: CreateProcess: perl "E:\XXXXXc\apache-tomcat-6.0.37-windows-x64\apache-tomcat-6.0.37\webapps\ROOT\WEB-INF\cgi\xxxx.pl" error=2
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(Unknown Source)
    at java.lang.ProcessImpl.start(Unknown Source)
    at java.lang.ProcessBuilder.start(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at org.apache.catalina.servlets.CGIServlet$CGIRunner.run(CGIServlet.java:1647)
    at org.apache.catalina.servlets.CGIServlet.doGet(CGIServlet.java:609)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Unknown Source)


Weblogic Logs Rotation setup step by step

Each WebLogic Server instance writes all messages from its subsystems and applications to a server log file that is located on the local host computer. By default, the server log file is located in the logsdirectory below the server instance root directory; for example, DOMAIN_NAME\servers\SERVER_NAME\logs\SERVER_NAME.log, where DOMAIN_NAME is the name of the directory in which you located the domain and SERVER_NAME is the name of the server.


In addition to writing messages to the server log file, each server instance forwards a subset of its messages to a domain-wide log file.The domain log file provides a central location from which to view the overall status of the domain. The domain log resides in the Administration Server logs directory. The default name and location for the domain log file is DOMAIN_NAME\servers\ADMIN_SERVER_NAME\logs\DOMAIN_NAME.log, where DOMAIN_NAME is the name of the directory in which you located the domain and ADMIN_SERVER_NAME is the name of the Administration Server.




You can rotate log files - 


By size ( default)
By Time






By default, when you start a WebLogic Server instance in development mode, the server automatically renames (rotates) its local server log file as SERVER_NAME.log.n. For the remainder of the server session, log messages accumulate in SERVER_NAME.log until the file grows to a size of 500 kilobytes.
Each time the server log file reaches this size, the server renames the log file and creates a new SERVER_NAME.log to store new messages. By default, the rotated log files are numbered in order of creationfilenamennnnn, where filename is the name configured for the log file. You can configure a server instance to include a time and date stamp in the file name of rotated log files; for example, server-name-%yyyy%-%mm%-%dd%-%hh%-%mm%.log.
By default, when you start a server instance in production mode, the server rotates its server log file whenever the file grows to 5000 kilobytes in size. It does not rotate the local server log file when you start the server.



You can change these default settings for log file rotation. 


For example
you can change the file size at which the server rotates the log file or 
you can configure a server to rotate log files based on a time interval. 
You can also specify the maximum number of rotated files that can accumulate. After the number   of log files reaches this number, subsequent file rotations delete the oldest log file and create a new log file with the latest suffix.


To change log size for rotation or by time -




Login to Administration Console
click on the server
On right hand side click on logging tab
under default selected general tab


Or select By time option under rotation type drop box and enter time in begin rotation time at the you want your server rotate log file

To update for access logs

Login to Administration Console
click on the server
On right hand side click on logging tab
Select HTTP tab and follow the same above instructions.

















java.io.IOException: CreateProcess: perl

description The server encountered an internal error that prevented it from fulfilling this request.
exception
java.io.IOException: CreateProcess: perl "E:\xxxx\apache-tomcat-6.0.37-windows-x64\apache-tomcat-6.0.37\webapps\ROOT\WEB-INF\cgi\xxxx.pl" error=2
 java.lang.ProcessImpl.create(Native Method)
 java.lang.ProcessImpl.<init>(Unknown Source)
 java.lang.ProcessImpl.start(Unknown Source)
 java.lang.ProcessBuilder.start(Unknown Source)
 java.lang.Runtime.exec(Unknown Source)
 org.apache.catalina.servlets.CGIServlet$CGIRunner.run(CGIServlet.java:1647)
 org.apache.catalina.servlets.CGIServlet.doGet(CGIServlet.java:609)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:723)