Is my test suite configured properly?
I am building db-4.6.19 from source on Novell SuSE Linux 9.2 on ia64 (Intel Itanium2) hardware, then running the test suite with tclsh 8.4. Here’s my configuration line:
cd build_unix
../dist/configure prefix=/home/mark/WORKAREAS/webplatform/build/dev/20070924 with-test --with-tcl=/usr/lib
I run make and that goes well, then I run the standard test in tclsh via:
echo 'info tclversion; source ../test/test.tcl; run_std; exit' | tclsh; tail ALL.OUT
Most of the tests pass, but the tail of ALL.OUT is at db-4.6.19/build_unix/ALL.OUT (below) produces many error messages for a few tests. They seem to be variations on the same issue, and I’m not sure how to fix it at this point – can someone point me to help? It appears that a command isn't parsing properly.
I'm not sure how to troubleshoot further, it seems to be a syntax error.
Thanks!
eval test119 -hash "119" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test119: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test120 -hash "120" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test120: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test121 -hash "121" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test121: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test122 -hash "122" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test122: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
Regression Tests Failed
Test suite run completed at: 14:29 09/24/07
Thanks, I have built in a new directory and ammended my configuration line to:
../dist/configure prefix=/home/mark/WORKAREAS/webplatform/build/dev/20070926 with-test enable-tcl with-tcl=/usr/lib
Results in:
checking build system type... ia64-unknown-linux-gnu
checking host system type... ia64-unknown-linux-gnu
checking if building in the top-level or dist directories... no
checking if --disable-cryptography option specified... no
checking if --disable-hash option specified... no
checking if --disable-mutexsupport option specified... no
checking if --disable-queue option specified... no
checking if --disable-replication option specified... no
checking if --disable-statistics option specified... no
checking if --disable-verify option specified... no
checking if --enable-compat185 option specified... no
checking if --enable-cxx option specified... no
checking if --enable-debug option specified... no
checking if --enable-debug_rop option specified... no
checking if --enable-debug_wop option specified... no
checking if --enable-diagnostic option specified... no
checking if --enable-dump185 option specified... no
checking if --enable-java option specified... no
checking if --enable-mingw option specified... no
checking if --enable-fine_grained_lock_manager option specified... no
checking if --enable-o_direct option specified... no
checking if --enable-posixmutexes option specified... no
checking if --enable-pthread_api option specified... no
checking if --enable-rpc option specified... no
checking if --enable-smallbuild option specified... no
checking if --enable-tcl option specified... yes
checking if --enable-test option specified... no
checking if --enable-uimutexes option specified... no
checking if --enable-umrw option specified... no
checking if --with-mutex=MUTEX option specified... no
checking if --with-tcl=DIR option specified... /usr/lib
checking if --with-uniquename=NAME option specified... no
checking for chmod... chmod
checking for cp... cp
checking for ln... ln
checking for mkdir... mkdir
checking for rm... rm
checking for sh... /bin/sh
checking for a BSD-compatible install... /usr/bin/install -c
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether we are using gcc version 2.96... no
checking whether g++ requires -fhandle-exceptions... no
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ld used by cc... /usr/ia64-suse-linux/bin/ld
checking if the linker (/usr/ia64-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/ia64-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... cc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 131072
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/ia64-suse-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
checking SOSUFFIX from libtool... .so
checking MODSUFFIX from libtool... .so
checking JMODSUFFIX from libtool... .so
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be included... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for struct stat.st_blksize... yes
checking for inttypes.h... (cached) yes
checking for stdint.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for unistd.h... (cached) yes
checking for char... yes
checking size of char... 1
checking for unsigned char... yes
checking size of unsigned char... 1
checking for short... yes
checking size of short... 2
checking for unsigned short... yes
checking size of unsigned short... 2
checking for int... yes
checking size of int... 4
checking for unsigned int... yes
checking size of unsigned int... 4
checking for long... yes
checking size of long... 8
checking for unsigned long... yes
checking size of unsigned long... 8
checking for long long... yes
checking size of long long... 8
checking for unsigned long long... yes
checking size of unsigned long long... 8
checking for char *... yes
checking size of char *... 8
checking for u_char... yes
checking for u_short... yes
checking for u_int... yes
checking for u_long... yes
checking for u_int8_t... yes
checking for u_int16_t... yes
checking for int16_t... yes
checking for u_int32_t... yes
checking for int32_t... yes
checking for u_int64_t... yes
checking for int64_t... yes
checking for FILE... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for time_t... yes
checking for size_t... (cached) yes
checking size of size_t... 8
checking for ssize_t... yes
checking for uintmax_t... yes
checking for uintptr_t... yes
checking for socklen_t... yes
checking for ANSI C exit success/failure values... yes
checking for mutexes... POSIX/pthreads/library
checking for main in -lpthread... yes
checking for library containing sched_yield... none required
checking for library containing fdatasync... none required
checking for library containing getaddrinfo... none required
checking for library containing hstrerror... none required
checking for main in -lm... yes
checking for main in -lnsl... yes
checking for main in -lpthread... (cached) yes
checking for main in -lsocket... no
checking for abort... yes
checking for atoi... yes
checking for atol... yes
checking for getcwd... yes
checking for getenv... yes
checking for getopt... yes
checking for isalpha... yes
checking for isdigit... yes
checking for isprint... yes
checking for isspace... yes
checking for memcmp... yes
checking for memcpy... yes
checking for memmove... yes
checking for printf... yes
checking for qsort... yes
checking for raise... yes
checking for rand... yes
checking for strcasecmp... yes
checking for strcat... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for strncat... yes
checking for strncmp... yes
checking for strrchr... yes
checking for strsep... yes
checking for strtol... yes
checking for strtoul... yes
checking for _fstati64... no
checking for directio... no
checking for fchmod... yes
checking for fclose... yes
checking for fcntl... yes
checking for fdatasync... yes
checking for fgetc... yes
checking for fgets... yes
checking for fopen... yes
checking for fwrite... yes
checking for getaddrinfo... yes
checking for getrusage... yes
checking for gettimeofday... yes
checking for getuid... yes
checking for hstrerror... yes
checking for localtime... yes
checking for mprotect... yes
checking for pstat_getdynamic... no
checking for pthread_yield... yes
checking for sched_yield... yes
checking for select... yes
checking for sigaction... yes
checking for snprintf... yes
checking for stat... yes
checking for strftime... yes
checking for sysconf... yes
checking for time... yes
checking for vsnprintf... yes
checking for yield... no
checking for ftruncate... yes
checking for clock_gettime... no
checking for ctime_r... yes
checking for 2 or 3 argument version of ctime_r... 2-argument
checking for pread... yes
checking for pwrite... yes
checking for fcntl/F_SETFD... yes
checking for special C compiler options needed for large files... no
checking for FILEOFFSET_BITS value needed for large files... no
checking for mlock... yes
checking for munlock... yes
checking for mmap... yes
checking for munmap... yes
checking for shmget... yes
checking for existence of /usr/lib/tclConfig.sh... loading
checking for 64-bit integral type support for sequences... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating db_cxx.h
config.status: creating db_int.h
config.status: creating clib_port.h
config.status: creating include.tcl
config.status: creating db.h
config.status: creating db_config.h
So I believe configuration is fine. Make also completes fine.
~/WORKAREAS/webplatform/build/dev/20070926/db-4.6.19/build_unix> tclsh
% source ../test/test.tcl
% run_std
Test suite run started at: 09:51 09/26/07
Berkeley DB 4.6.19: (August 10, 2007)
Running environment tests
Running archive tests
Running backup tests
Running file operations tests
Running locking tests
Running logging tests
Running memory pool tests
Running transaction tests
Running deadlock detection tests
Running subdatabase tests
Running byte-order tests
Running recno backing file tests
Running DBM interface tests
Running NDBM interface tests
Running Hsearch interface tests
Running secondary index tests
Running replication tests
Running security tests
Running recovery tests
FAIL:09:51:09 (00:00:00) r: recd: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
Running join test
Running btree tests
Running rbtree tests
Running queue tests
Running queueext tests
Running recno tests
Running frecno tests
Running rrecno tests
Running hash tests
UNEXPECTED OUTPUT: Berkeley DB 4.6.19: (August 10, 2007)
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: env: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: archive: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: backup: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: fop: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: lock: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
...and so on to the end. This seems to be the same issue I'd originally reported in this thread. Is there anything else I can do to troubleshoot this? I'm not a tcl expert, unfortunately.
Thanks again for your help or pointers!
--Mark
Similar Messages
-
Components configuration page gives bug in provider test suite
Hi there,
I am testing my component http://testby1234.herokuapp.com/
in Provider Test Suite
But I got error on "Cannot GET /components/configure/235707b5-99ae-b7b5-a34d-3bf3023adb02?assetId=1337&contactId=" on configuration button click
ThanksThanks a lot.
Cloud components is developed in NodeJS and My Configuration File is in PHP. My Configuration PHP File is in components NodeJS's public folder.
and my code is like
createInstance: BASE_COMP_URL + '/create/{Id}',
removeInstance: BASE_COMP_URL + '/remove/{Id}',
configurationUrl: BASE_COMP_URL + '/configure/index.php?{Id}&assetId={AssetId}&contactId={ContactId}',
renderInstance: BASE_COMP_URL + '/render/{Id}?assetId={AssetId}&contactId={ContactId}&visitorId={VisitorId}',
instanceImage: BASE_COMP_URL + '/preview/{Id}?assetId={AssetId}&contactId={ContactId}&visitorId={VisitorId}'
my BASE_COMP_URL is diff server for php files because php files are not run on herokuapp.com
create and remove is working fine. I have created configuration folder in My PHP File Server. So Configuration is also running perfectly. but render and preview is not working.
So will I have to create all folders on my PHP File Server or in my Components server? Or any other way ?
Please help me. -
Phoronix Test Suite released and Result collection
So this might be "similar" to 3Dmark but for linux:
http://www.phoronix.com/scan.php?page=a … _pts&num=1
Also we could post some test results for referance,
Include Computer specs, and Distro you tested in.
We should run ./phoronix-test-suite benchmark universe but since it takes some time, ill post mine later.
Ugh and ofcourse it wont find time command
Edit:If someone gets this to work, please do give a shout.
Last edited by Mikko777 (2008-04-03 18:16:14)Actually, I got it to work.........mostly. Some of the tests still don't work for whatever reason, but most of the one's that I've tried do work. I modified my php.ini file as described above. In addition, I modified the open_basedir in php.ini as follows.
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/:/usr/bin/gcc:/usr/bin/wget:/proc/
I'm attaching my php.ini file for posterity.
[PHP]
; About php.ini ;
; This file controls many aspects of PHP's behavior. In order for PHP to
; read it, it must be named 'php.ini'. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; The path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
; foo = ; sets foo to an empty string
; foo = none ; sets foo to an empty string
; foo = "none" ; sets foo to the string 'none'
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
; About this file ;
; This is the recommended, PHP 5-style version of the php.ini-dist file. It
; sets some non standard settings, that make PHP more efficient, more secure,
; and encourage cleaner coding.
; The price is that with these settings, PHP may be incompatible with some
; applications, and sometimes, more difficult to develop with. Using this
; file is warmly recommended for production sites. As all of the changes from
; the standard settings are thoroughly documented, you can go over each one,
; and decide whether you want to use it or not.
; For general information about the php.ini file, please consult the php.ini-dist
; file, included in your PHP distribution.
; This file is different from the php.ini-dist file in the fact that it features
; different values for several directives, in order to improve performance, while
; possibly breaking compatibility with the standard out-of-the-box behavior of
; PHP. Please make sure you read what's different, and modify your scripts
; accordingly, if you decide to use this file instead.
; - register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long predefined array
; variables ($HTTP_*_VARS). Instead, use the superglobals that were
; introduced in PHP 4.1.0
; - display_errors = Off [Security]
; With this directive set to off, errors that occur during the execution of
; scripts will no longer be displayed as a part of the script output, and thus,
; will no longer be exposed to remote users. With some errors, the error message
; content may expose information about your script, web server, or database
; server that may be exploitable for hacking. Production sites should have this
; directive set to off.
; - log_errors = On [Security]
; This directive complements the above one. Any errors that occur during the
; execution of your script will be logged (typically, to your server's error log,
; but can be configured in several ways). Along with setting display_errors to off,
; this setup gives you the ability to fully understand what may have gone wrong,
; without exposing any sensitive information to remote users.
; - output_buffering = 4096 [Performance]
; Set a 4KB output buffer. Enabling output buffering typically results in less
; writes, and sometimes less packets sent on the wire, which can often lead to
; better performance. The gain this directive actually yields greatly depends
; on which Web server you're working with, and what kind of scripts you're using.
; - register_argc_argv = Off [Performance]
; Disables registration of the somewhat redundant $argv and $argc global
; variables.
; - magic_quotes_gpc = Off [Performance]
; Input data is no longer escaped with slashes so that it can be sent into
; SQL databases without further manipulation. Instead, you should use the
; database vendor specific escape string function on each input element you
; wish to send to a database.
; - variables_order = "GPCS" [Performance]
; The environment variables are not hashed into the $_ENV. To access
; environment variables, you can use getenv() instead.
; - error_reporting = E_ALL [Code Cleanliness, Security(?)]
; By default, PHP suppresses errors of type E_NOTICE. These error messages
; are emitted for non-critical errors, but that could be a symptom of a bigger
; problem. Most notably, this will cause error messages about the use
; of uninitialized variables to be displayed.
; - allow_call_time_pass_reference = Off [Code cleanliness]
; It's not possible to decide to force a variable to be passed by reference
; when calling a function. The PHP 4 style to do this is by making the
; function require the relevant argument by reference.
; - short_open_tag = Off [Portability]
; Using short tags is discouraged when developing code meant for redistribution
; since short tags may not be supported on the target server.
; Language Options ;
; Enable the PHP scripting language engine under Apache.
engine = On
; Enable compatibility mode with Zend Engine 1 (PHP 4.x)
zend.ze1_compatibility_mode = Off
; Allow the <? tag. Otherwise, only <?php and <script> tags are recognized.
; NOTE: Using short tags should be avoided when developing applications or
; libraries that are meant for redistribution, or deployment on PHP
; servers which are not under your control, because short tags may not
; be supported on the target server. For portable, redistributable code,
; be sure not to use short tags.
short_open_tag = Off
; Allow ASP-style <% %> tags.
asp_tags = Off
; The number of significant digits displayed in floating point numbers.
precision = 14
; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
y2k_compliance = On
; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit. You can enable output buffering during runtime by calling the output
; buffering functions. You can also enable output buffering for all files by
; setting this directive to On. If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = 4096
; You can redirect all of the output of your scripts to a function. For
; example, if you set output_handler to "mb_output_handler", character
; encoding will be transparently converted to the specified encoding.
; Setting any output handler automatically turns on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
; directive. Instead, explicitly set the output handler using ob_start().
; Using this ini directive may cause problems unless you know what script
; is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
; and you cannot use both "ob_gzhandler" and "zlib.output_compression".
; Note: output_handler must be empty if this is set 'On' !!!!
; Instead you must use zlib.output_handler.
;output_handler =
; Transparent output compression using the zlib library
; Valid values for this option are 'off', 'on', or a specific buffer size
; to be used for compression (default is 4KB)
; Note: Resulting chunk size may vary due to nature of compression. PHP
; outputs chunks that are few hundreds bytes each as a result of
; compression. If you prefer a larger chunk size for better
; performance, enable output_buffering in addition.
; Note: You need to use zlib.output_handler instead of the standard
; output_handler, or otherwise the output will be corrupted.
zlib.output_compression = Off
;zlib.output_compression_level = -1
; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
;zlib.output_handler =
; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block. This is equivalent to calling the
; PHP function flush() after each and every call to print() or echo() and each
; and every HTML block. Turning this option on has serious performance
; implications and is generally recommended for debugging purposes only.
implicit_flush = Off
; The unserialize callback function will be called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instantiated.
; A warning appears if the specified function is not defined, or if the
; function doesn't include/implement the missing class.
; So only set this entry, if you really want to implement such a
; callback-function.
unserialize_callback_func=
; When floats & doubles are serialized store serialize_precision significant
; digits after the floating point. The default value ensures that when floats
; are decoded with unserialize, the data will remain the same.
serialize_precision = 100
; Whether to enable the ability to force arguments to be passed by reference
; at function call time. This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend. The encouraged method of
; specifying which arguments should be passed by reference is in the function
; declaration. You're encouraged to try and turn this option Off and make
; sure your scripts work properly with it in order to ensure they will work
; with future versions of the language (you will receive a warning each time
; you use this feature, and the argument will be passed by value instead of by
; reference).
allow_call_time_pass_reference = Off
; Safe Mode
safe_mode = Off
; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = Off
; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir =
; When safe_mode is on, only executables located in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
safe_mode_exec_dir =
; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes. In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here. By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
; Note: If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_
; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv(). These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH
; open_basedir, if set, limits all file operations to the defined directory
; and below. This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/:/usr/bin/gcc:/usr/bin/wget:/proc/
; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =
; This directive allows you to disable certain classes for security reasons.
; It receives a comma-delimited list of class names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_classes =
; Colors for Syntax Highlighting mode. Anything that's acceptable in
; <span style="color: ???????"> would work.
;highlight.string = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.bg = #FFFFFF
;highlight.default = #0000BB
;highlight.html = #000000
; If enabled, the request will be allowed to complete even if the user aborts
; the request. Consider enabling it if executing long request, which may end up
; being interrupted by the user or a browser timing out.
; ignore_user_abort = On
; Determines the size of the realpath cache to be used by PHP. This value should
; be increased on systems where PHP opens many files to reflect the quantity of
; the file operations performed.
; realpath_cache_size=16k
; Duration of time, in seconds for which to cache realpath information for a given
; file or directory. For systems with rarely changing files, consider increasing this
; value.
; realpath_cache_ttl=120
; Misc
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header). It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = Off
; Resource Limits ;
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 32M ; Maximum amount of memory a script may consume (32MB)
; Error handling and logging ;
; error_reporting is a bit-field. Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings (doesn't include E_STRICT)
; E_ERROR - fatal run-time errors
; E_RECOVERABLE_ERROR - almost fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
; Examples:
; - Show all errors, except for notices and coding standards warnings
;error_reporting = E_ALL & ~E_NOTICE
; - Show all errors, except for notices
;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
; - Show only errors
;error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
; - Show all errors, except coding standards warnings
error_reporting = E_ALL
; Print out errors (as a part of the output). For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
; possible values for display_errors:
; Off - Do not display any errors
; stderr - Display errors to STDERR (affects only CGI/CLI binaries!)
; On or stdout - Display errors to STDOUT (default)
; To output errors to STDERR with CGI/CLI:
;display_errors = "stderr"
; Default
display_errors = Off
; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed. It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off
; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = On
; Set maximum length of log_errors. In error_log information about the source is
; added. The default is 1024 and 0 allows to not apply any maximum length at all.
log_errors_max_len = 1024
; Do not log repeated messages. Repeated errors must occur in same file on same
; line unless ignore_repeated_source is set true.
ignore_repeated_errors = Off
; Ignore source of message when ignoring repeated messages. When this setting
; is On you will not log errors with repeated messages from different files or
; source lines.
ignore_repeated_source = Off
; If this parameter is set to Off, then memory leaks will not be shown (on
; stdout or in the log). This has only effect in a debug compile, and if
; error reporting includes E_WARNING in the allowed list
report_memleaks = Off
;report_zend_debug = 0
; Store the last error/warning message in $php_errormsg (boolean).
track_errors = Off
; Turn off normal error reporting and emit XML-RPC error XML
;xmlrpc_errors = 0
; An XML-RPC faultCode
;xmlrpc_error_number = 0
; Disable the inclusion of HTML tags in error messages.
; Note: Never use this feature for production boxes.
;html_errors = Off
; If html_errors is set On PHP produces clickable error messages that direct
; to a page describing the error or function causing the error in detail.
; You can download a copy of the PHP manual from http://www.php.net/docs.php
; and change docref_root to the base URL of your local copy including the
; leading '/'. You must also specify the file extension being used including
; the dot.
; Note: Never use this feature for production boxes.
;docref_root = "/phpmanual/"
;docref_ext = .html
; String to output before an error message.
;error_prepend_string = "<font color=#ff0000>"
; String to output after an error message.
;error_append_string = "</font>"
; Log errors to specified file.
;error_log = filename
; Log errors to syslog.
error_log = syslog
; Data Handling ;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3
; The separator used in PHP generated URLs to separate arguments.
; Default is "&".
;arg_separator.output = "&"
; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&".
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"
; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC). Registration is done from left to right, newer
; values override older values.
variables_order = "GPCS"
; Whether or not to register the EGPCS variables as global variables. You may
; want to turn this off if you don't want to clutter your scripts' global scope
; with user data. This makes most sense when coupled with track_vars - in which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
; You should do your best to write your scripts so that they do not require
; register_globals to be on; Using form variables as globals can easily lead
; to possible security problems, if the code is not very well thought of.
register_globals = Off
; Whether or not to register the old-style input arrays, HTTP_GET_VARS
; and friends. If you're not using them, it's recommended to turn them off,
; for performance reasons.
register_long_arrays = Off
; This directive tells PHP whether to declare the argv&argc variables (that
; would contain the GET information). If you don't use these variables, you
; should turn it off for increased performance.
register_argc_argv = Off
; When enabled, the SERVER and ENV variables are created when they're first
; used (Just In Time) instead of when the script starts. If these variables
; are not used within a script, having this directive on will result in a
; performance gain. The PHP directives register_globals, register_long_arrays,
; and register_argc_argv must be disabled for this directive to have any affect.
auto_globals_jit = On
; Maximum size of POST data that PHP will accept.
post_max_size = 8M
; Magic quotes
; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = Off
; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_runtime = Off
; Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off
; Automatically add files before or after any PHP document.
auto_prepend_file =
auto_append_file =
; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header. To disable sending of the charset, simply
; set it to be empty.
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"
; Always populate the $HTTP_RAW_POST_DATA variable.
;always_populate_raw_post_data = On
; Paths and Directories ;
; UNIX: "/path1:/path2"
include_path = ".:/usr/share/pear"
; The root of the PHP pages, used only if nonempty.
; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
; if you are running php as a CGI under any web server (other than IIS)
; see documentation for security issues. The alternate is to use the
; cgi.force_redirect configuration below
doc_root =
; The directory under which PHP opens the script using /~username used only
; if nonempty.
user_dir =
; Directory in which the loadable extensions (modules) reside.
extension_dir = "/usr/lib/php/20060613/"
; Whether or not to enable the dl() function. The dl() function does NOT work
; properly in multithreaded servers, such as IIS or Zeus, and is automatically
; disabled on them.
enable_dl = Off
; cgi.force_redirect is necessary to provide security running PHP as a CGI under
; most web servers. Left undefined, PHP turns this on by default. You can
; turn it off here AT YOUR OWN RISK
; **You CAN safely turn this off for IIS, in fact, you MUST.**
; cgi.force_redirect = 1
; if cgi.nph is enabled it will force cgi to always sent Status: 200 with
; every request.
; cgi.nph = 1
; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape
; (iPlanet) web servers, you MAY need to set an environment variable name that PHP
; will look for to know it is OK to continue execution. Setting this variable MAY
; cause security issues, KNOW WHAT YOU ARE DOING FIRST.
; cgi.redirect_status_env = ;
; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI. PHP's
; previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok
; what PATH_INFO is. For more information on PATH_INFO, see the cgi specs. Setting
; this to 1 will cause PHP CGI to fix it's paths to conform to the spec. A setting
; of zero causes PHP to behave as before. Default is 1. You should fix your scripts
; to use SCRIPT_FILENAME rather than PATH_TRANSLATED.
; cgi.fix_pathinfo=1
; FastCGI under IIS (on WINNT based OS) supports the ability to impersonate
; security tokens of the calling client. This allows IIS to define the
; security context that the request runs under. mod_fastcgi under Apache
; does not currently support this feature (03/17/2002)
; Set to 1 if running under IIS. Default is zero.
; fastcgi.impersonate = 1;
; Disable logging through FastCGI connection
; fastcgi.logging = 0
; cgi.rfc2616_headers configuration option tells PHP what type of headers to
; use when sending HTTP response code. If it's set 0 PHP sends Status: header that
; is supported by Apache. When this option is set to 1 PHP will send
; RFC2616 compliant header.
; Default is zero.
;cgi.rfc2616_headers = 0
; File Uploads ;
; Whether to allow HTTP file uploads.
file_uploads = On
; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
;upload_tmp_dir =
; Maximum allowed size for uploaded files.
upload_max_filesize = 2M
; Fopen wrappers ;
; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
allow_url_fopen = On
; Whether to allow include/require to open URLs (like http:// or ftp://) as files.
allow_url_include = On
; Define the anonymous ftp password (your email address)
;from="[email protected]"
; Define the User-Agent string
; user_agent="PHP"
; Default timeout for socket based streams (seconds)
default_socket_timeout = 60
; Dynamic Extensions ;
; If you wish to have an extension loaded automatically, use the following
; syntax:
; extension=modulename.extension
; For example, under UNIX:
; extension=msql.so
; Note that it should be the name of the module only; no directory information
; needs to go here. Specify the location of the extension with the
; extension_dir directive above.
; Module Settings ;
[Date]
; Defines the default timezone used by the date functions
;date.timezone =
;date.default_latitude = 31.7667
;date.default_longitude = 35.2333
;date.sunrise_zenith = 90.583333
;date.sunset_zenith = 90.583333
[filter]
;filter.default = unsafe_raw
;filter.default_flags =
[iconv]
;iconv.input_encoding = ISO-8859-1
;iconv.internal_encoding = ISO-8859-1
;iconv.output_encoding = ISO-8859-1
[sqlite]
;sqlite.assoc_case = 0
[Pcre]
;PCRE library backtracking limit.
;pcre.backtrack_limit=100000
;PCRE library recursion limit.
;Please note that if you set this value to a high number you may consume all
;the available process stack and eventually crash PHP (due to reaching the
;stack size limit imposed by the Operating System).
;pcre.recursion_limit=100000
[Syslog]
; Whether or not to define the various syslog variables (e.g. $LOG_PID,
; $LOG_CRON, etc.). Turning it off is a good idea performance-wise. In
; runtime, you can define these variables by calling define_syslog_variables().
define_syslog_variables = Off
[mail function]
; For Unix only. You may supply arguments as well (default: "sendmail -t -i").
;sendmail_path =
; Force the addition of the specified parameters to be passed as extra parameters
; to the sendmail binary. These parameters will always replace the value of
; the 5th parameter to mail(), even in safe mode.
;mail.force_extra_parameters =
[SQL]
sql.safe_mode = Off
[ODBC]
;odbc.default_db = Not yet implemented
;odbc.default_user = Not yet implemented
;odbc.default_pw = Not yet implemented
; Allow or prevent persistent links.
odbc.allow_persistent = On
; Check that a connection is still valid before reuse.
odbc.check_persistent = On
; Maximum number of persistent links. -1 means no limit.
odbc.max_persistent = -1
; Maximum number of links (persistent + non-persistent). -1 means no limit.
odbc.max_links = -1
; Handling of LONG fields. Returns number of bytes to variables. 0 means
; passthru.
odbc.defaultlrl = 4096
; Handling of binary data. 0 means passthru, 1 return as is, 2 convert to char.
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation
; of uodbc.defaultlrl and uodbc.defaultbinmode
odbc.defaultbinmode = 1
[MySQL]
; Allow or prevent persistent links.
mysql.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
mysql.max_persistent = -1
; Maximum number of links (persistent + non-persistent). -1 means no limit.
mysql.max_links = -1
; Default port number for mysql_connect(). If unset, mysql_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order).
mysql.default_port =
; Default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults.
mysql.default_socket =
; Default host for mysql_connect() (doesn't apply in safe mode).
mysql.default_host =
; Default user for mysql_connect() (doesn't apply in safe mode).
mysql.default_user =
; Default password for mysql_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysql.default_password")
; and reveal this password! And of course, any users with read access to this
; file will be able to reveal the password as well.
mysql.default_password =
; Maximum time (in seconds) for connect timeout. -1 means no limit
mysql.connect_timeout = 60
; Trace mode. When trace_mode is active (=On), warnings for table/index scans and
; SQL-Errors will be displayed.
mysql.trace_mode = Off
[MySQLi]
; Maximum number of links. -1 means no limit.
mysqli.max_links = -1
; Default port number for mysqli_connect(). If unset, mysqli_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order).
mysqli.default_port = 3306
; Default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults.
mysqli.default_socket =
; Default host for mysql_connect() (doesn't apply in safe mode).
mysqli.default_host =
; Default user for mysql_connect() (doesn't apply in safe mode).
mysqli.default_user =
; Default password for mysqli_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysqli.default_pw")
; and reveal this password! And of course, any users with read access to this
; file will be able to reveal the password as well.
mysqli.default_pw =
; Allow or prevent reconnect
mysqli.reconnect = Off
[mSQL]
; Allow or prevent persistent links.
msql.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
msql.max_persistent = -1
; Maximum number of links (persistent+non persistent). -1 means no limit.
msql.max_links = -1
[OCI8]
; enables privileged connections using external credentials (OCI_SYSOPER, OCI_SYSDBA)
;oci8.privileged_connect = Off
; Connection: The maximum number of persistent OCI8 connections per
; process. Using -1 means no limit.
;oci8.max_persistent = -1
; Connection: The maximum number of seconds a process is allowed to
; maintain an idle persistent connection. Using -1 means idle
; persistent connections will be maintained forever.
;oci8.persistent_timeout = -1
; Connection: The number of seconds that must pass before issuing a
; ping during oci_pconnect() to check the connection validity. When
; set to 0, each oci_pconnect() will cause a ping. Using -1 disables
; pings completely.
;oci8.ping_interval = 60
; Tuning: This option enables statement caching, and specifies how
; many statements to cache. Using 0 disables statement caching.
;oci8.statement_cache_size = 20
; Tuning: Enables statement prefetching and sets the default number of
; rows that will be fetched automatically after statement execution.
;oci8.default_prefetch = 10
; Compatibility. Using On means oci_close() will not close
; oci_connect() and oci_new_connect() connections.
;oci8.old_oci_close_semantics = Off
[PostgresSQL]
; Allow or prevent persistent links.
pgsql.allow_persistent = On
; Detect broken persistent links always with pg_pconnect().
; Auto reset feature requires a little overheads.
pgsql.auto_reset_persistent = Off
; Maximum number of persistent links. -1 means no limit.
pgsql.max_persistent = -1
; Maximum number of links (persistent+non persistent). -1 means no limit.
pgsql.max_links = -1
; Ignore PostgreSQL backends Notice message or not.
; Notice message logging require a little overheads.
pgsql.ignore_notice = 0
; Log PostgreSQL backends Notice message or not.
; Unless pgsql.ignore_notice=0, module cannot log notice message.
pgsql.log_notice = 0
[Sybase]
; Allow or prevent persistent links.
sybase.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
sybase.max_persistent = -1
; Maximum number of links (persistent + non-persistent). -1 means no limit.
sybase.max_links = -1
;sybase.interface_file = "/usr/sybase/interfaces"
; Minimum error severity to display.
sybase.min_error_severity = 10
; Minimum message severity to display.
sybase.min_message_severity = 10
; Compatibility mode with old versions of PHP 3.0.
; If on, this will cause PHP to automatically assign types to results according
; to their Sybase type, instead of treating them all as strings. This
; compatibility mode will probably not stay around forever, so try applying
; whatever necessary changes to your code, and turn it off.
sybase.compatability_mode = Off
[Sybase-CT]
; Allow or prevent persistent links.
sybct.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
sybct.max_persistent = -1
; Maximum number of links (persistent + non-persistent). -1 means no limit.
sybct.max_links = -1
; Minimum server message severity to display.
sybct.min_server_severity = 10
; Minimum client message severity to display.
sybct.min_client_severity = 10
[bcmath]
; Number of decimal digits for all bcmath functions.
bcmath.scale = 0
[browscap]
;browscap = extra/browscap.ini
[Informix]
; Default host for ifx_connect() (doesn't apply in safe mode).
ifx.default_host =
; Default user for ifx_connect() (doesn't apply in safe mode).
ifx.default_user =
; Default password for ifx_connect() (doesn't apply in safe mode).
ifx.default_password =
; Allow or prevent persistent links.
ifx.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
ifx.max_persistent = -1
; Maximum number of links (persistent + non-persistent). -1 means no limit.
ifx.max_links = -1
; If on, select statements return the contents of a text blob instead of its id.
ifx.textasvarchar = 0
; If on, select statements return the contents of a byte blob instead of its id.
ifx.byteasvarchar = 0
; Trailing blanks are stripped from fixed-length char columns. May help the
; life of Informix SE users.
ifx.charasvarchar = 0
; If on, the contents of text and byte blobs are dumped to a file instead of
; keeping them in memory.
ifx.blobinfile = 0
; NULL's are returned as empty strings, unless this is set to 1. In that case,
; NULL's are returned as string 'NULL'.
ifx.nullformat = 0
[Session]
; Handler used to store/retrieve data.
session.save_handler = files
; Argument passed to save_handler. In the case of files, this is the path
; where data files are stored.
; As of PHP 4.0.1, you can define the path as:
; session.save_path = "N;/path"
; where N is an integer. Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories. This is useful if you
; or your OS have problems with lots of files in one directory, and is
; a more efficient layout for servers that handle lots of sessions.
; NOTE 1: PHP will not create this directory structure automatically.
; You can use the script in the ext/session dir for that purpose.
; NOTE 2: See the section on garbage collection below if you choose to
; use subdirectories for session storage
; The file storage module creates files using mode 600 by default.
; You can change that by using
; session.save_path = "N;MODE;/path"
; where MODE is the octal representation of the mode. Note that this
; does not overwrite the process's umask.
session.save_path = "/tmp"
; Whether to use cookies.
session.use_cookies = 1
;session.cookie_secure =
; This option enables administrators to make their users invulnerable to
; attacks which involve passing session ids in URLs; defaults to 0.
; session.use_only_cookies = 1
; Name of the session (used as cookie name).
session.name = PHPSESSID
; Initialize session on request startup.
session.auto_start = 0
; Lifetime in seconds of cookie or, if 0, until browser is restarted.
session.cookie_lifetime = 0
; The path for which the cookie is valid.
session.cookie_path = /
; The domain for which the cookie is valid.
session.cookie_domain =
; Whether or not to add the httpOnly flag to the cookie, which makes it inaccessible to browser scripting languages such as JavaScript.
session.cookie_httponly =
; Handler used to serialize data. php is the standard serializer of PHP.
session.serialize_handler = php
; Define the probability that the 'garbage collection' process is started
; on every session initialization.
; The probability is calculated by using gc_probability/gc_divisor,
; e.g. 1/100 means there is a 1% chance that the GC process starts
; on each request.
session.gc_probability = 1
session.gc_divisor = 1000
; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
session.gc_maxlifetime = 1440
; NOTE: If you are using the subdirectory option for storing session files
; (see session.save_path above), then garbage collection does *not*
; happen automatically. You will need to do your own garbage
; collection through a shell script, cron entry, or some other method.
; For example, the following script would is the equivalent of
; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
; cd /path/to/sessions; find -cmin +24 | xargs rm
; PHP 4.2 and less have an undocumented feature/bug that allows you to
; to initialize a session variable in the global scope, albeit register_globals
; is disabled. PHP 4.3 and later will warn you, if this feature is used.
; You can disable the feature and the warning separately. At this time,
; the warning is only displayed, if bug_compat_42 is enabled.
session.bug_compat_42 = 0
session.bug_compat_warn = 1
; Check HTTP Referer to invalidate externally stored URLs containing ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =
; How many bytes to read from the file.
session.entropy_length = 0
; Specified here to create the session id.
session.entropy_file =
;session.entropy_length = 16
;session.entropy_file = /dev/urandom
; Set to {nocache,private,public,} to determine HTTP caching aspects
; or leave this empty to avoid sending anti-caching headers.
session.cache_limiter = nocache
; Document expires after n minutes.
session.cache_expire = 180
; trans sid support is disabled by default.
; Use of trans sid may risk your users security.
; Use this option with caution.
; - User may send URL contains active session ID
; to other person via. email/irc/etc.
; - URL that contains active session ID may be stored
; in publically accessible computer.
; - User may access your site with the same session ID
; always using URL stored in browser's history or bookmarks.
session.use_trans_sid = 0
; Select a hash function
; 0: MD5 (128 bits)
; 1: SHA-1 (160 bits)
session.hash_function = 0
; Define how many bits are stored in each character when converting
; the binary hash data to something readable.
; 4 bits: 0-9, a-f
; 5 bits: 0-9, a-v
; 6 bits: 0-9, a-z, A-Z, "-", ","
session.hash_bits_per_character = 5
; The URL rewriter will look for URLs in a defined set of HTML tags.
; form/fieldset are special; if you include them here, the rewriter will
; add a hidden <input> field with the info which is otherwise appended
; to URLs. If you want XHTML conformity, remove the form entry.
; Note that all valid entries require a "=", even if no value follows.
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=fakeentry"
[MSSQL]
; Allow or prevent persistent links.
mssql.allow_persistent = On
; Maximum number of persistent links. -1 means no limit.
mssql.max_persistent = -1
; Maximum number of links (persistent+non persistent). -1 means no limit.
mssql.max_links = -1
; Minimum error severity to display.
mssql.min_error_severity = 10
; Minimum message severity to display.
mssql.min_message_severity = 10
; Compatibility mode with old versions of PHP 3.0.
mssql.compatability_mode = Off
; Connect timeout
;mssql.connect_timeout = 5
; Query timeout
;mssql.timeout = 60
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textlimit = 4096
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textsize = 4096
; Limits the number of records in each batch. 0 = all records in one batch.
;mssql.batchsize = 0
; Specify how datetime and datetim4 columns are returned
; On => Returns data converted to SQL server settings
; Off => Returns values as YYYY-MM-DD hh:mm:ss
;mssql.datetimeconvert = On
; Use NT authentication when connecting to the server
mssql.secure_connection = Off
; Specify max number of processes. -1 = library default
; msdlib defaults to 25
; FreeTDS defaults to 4096
;mssql.max_procs = -1
; Specify client character set.
; If empty or not set the client charset from freetds.comf is used
; This is only used when compiled with FreeTDS
;mssql.charset = "ISO-8859-1"
[Assertion]
; Assert(expr); active by default.
;assert.active = On
; Issue a PHP warning for each failed assertion.
;assert.warning = On
; Don't bail out by default.
;assert.bail = Off
; User-function to be called if an assertion fails.
;assert.callback = 0
; Eval the expression with current error_reporting(). Set to true if you want
; error_reporting(0) around the eval().
;assert.quiet_eval = 0
[COM]
; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs
;com.typelib_file =
; allow Distributed-COM calls
;com.allow_dcom = true
; autoregister constants of a components typlib on com_load()
;com.autoregister_typelib = true
; register constants casesensitive
;com.autoregister_casesensitive = false
; show warnings on duplicate constant registrations
;com.autoregister_verbose = true
[mbstring]
; language for internal character representation.
;mbstring.language = Japanese
; internal/script encoding.
; Some encoding cannot work as internal encoding.
; (e.g. SJIS, BIG5, ISO-2022-*)
;mbstring.internal_encoding = EUC-JP
; http input encoding.
;mbstring.http_input = auto
; http output encoding. mb_output_handler must be
; registered as output buffer to function
;mbstring.http_output = SJIS
; enable automatic encoding translation according to
; mbstring.internal_encoding setting. Input chars are
; converted to internal encoding by setting this to On.
; Note: Do _not_ use automatic encoding translation for
; portable libs/applications.
;mbstring.encoding_translation = Off
; automatic encoding detection order.
; auto means
;mbstring.detect_order = auto
; substitute_character used when character cannot be converted
; one from another
;mbstring.substitute_character = none;
; overload(replace) single byte functions by mbstring functions.
; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
; etc. Possible values are 0,1,2,4 or combination of them.
; For example, 7 for overload everything.
; 0: No overload
; 1: Overload mail() function
; 2: Overload str*() functions
; 4: Overload ereg*() functions
;mbstring.func_overload = 0
; enable strict encoding detection.
;mbstring.strict_encoding = Off
[FrontBase]
;fbsql.allow_persistent = On
;fbsql.autocommit = On
;fbsql.show_timestamp_decimals = Off
;fbsql.default_database =
;fbsql.default_database_password =
;fbsql.default_host =
;fbsql.default_password =
;fbsql.default_user = "_SYSTEM"
;fbsql.generate_warnings = Off
;fbsql.max_connections = 128
;fbsql.max_links = 128
;fbsql.max_persistent = -1
;fbsql.max_results = 128
[gd]
; Tell the jpeg decode to libjpeg warnings and try to create
; a gd image. The warning will then be displayed as notices
; disabled by default
;gd.jpeg_ignore_warning = 0
[exif]
; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS.
; With mbstring support this will automatically be converted into the encoding
; given by corresponding encode setting. When empty mbstring.internal_encoding
; is used. For the decode settings you can distinguish between motorola and
; intel byte order. A decode setting cannot be empty.
;exif.encode_unicode = ISO-8859-15
;exif.decode_unicode_motorola = UCS-2BE
;exif.decode_unicode_intel = UCS-2LE
;exif.encode_jis =
;exif.decode_jis_motorola = JIS
;exif.decode_jis_intel = JIS
[Tidy]
; The path to a default tidy configuration file to use when using tidy
;tidy.default_config = /usr/local/lib/php/default.tcfg
; Should tidy clean and repair output automatically?
; WARNING: Do not use this option if you are generating non-html content
; such as dynamic images
tidy.clean_output = Off
[soap]
; Enables or disables WSDL caching feature.
soap.wsdl_cache_enabled=1
; Sets the directory name where SOAP extension will put cache files.
soap.wsdl_cache_dir="/tmp"
; (time to live) Sets the number of second while cached file will be used
; instead of original one.
soap.wsdl_cache_ttl=86400
; available extensions
;extension=bcmath.so
;extension=bz2.so
;extension=calendar.so
extension=curl.so
;extension=dba.so
;extension=dbase.so
;extension=exif.so
;extension=ftp.so
extension=gd.so
extension=gettext.so
;extension=gmp.so
;extension=iconv.so
;extension=imap.so
;extension=json.so
;extension=ldap.so
;extension=mcrypt.so
;extension=mhash.so
;extension=mime_magic.so
;extension=mysql.so
;extension=mysqli.so
;extension=ncurses.so
;extension=odbc.so
;extension=openssl.so
;extension=pdo.so
;extension=pdo_mysql.so
;extension=pdo_odbc.so
;extension=pdo_pgsql.so
;extension=pdo_sqlite.so
;extension=pgsql.so
extension=posix.so
;extension=pspell.so
extension=session.so
;extension=shmop.so
;extension=snmp.so
;extension=soap.so
;extension=sockets.so
;extension=sqlite.so
;extension=sysvmsg.so
;extension=sysvsem.so
;extension=sysvshm.so
;extension=tidy.so
;extension=xmlrpc.so
;extension=xsl.so
;extension=zip.so
extension=zlib.so
; Local Variables:
; tab-width: 4
; End: -
Minimum system requirements for installing Oracle Application Testing Suite
Hi,
Can anyone tell me what are the minimum system requirements for intalling Oracle Application Testing Suite?
Thanks in AdvanceFrom the release notes (12.1.0.2).
System Requirements
Oracle Application Testing Suite has the following system requirements:
4
3.1 Oracle Functional Testing/OpenScript
Oracle Functional Testing’s OpenScript scripting platform has the following system
requirements:
■ Operating System (32-bit and 64-bit versions): Windows XP, Windows Vista,
Windows 2003, Windows 7, Windows 2008
■ Memory: Minimum 1 GB
■ System: x86, 32-bit or 64-bit processor, 2.6 GHz or faster
■ Disk Space: 4 GB minimum
■ Browser: Internet Explorer 7.x, 8.x., 9.x and Firefox 3.5/3.6, 6.x
3.2 Oracle Load Testing
Oracle Load Testing has the following system requirements:
■ Operating System (32-bit and 64-bit versions): Windows XP, Windows Vista,
Windows 2003, Windows 7, Windows 2008, Windows 2008 R2. Oracle Enterprise
Linux 5.1, 5.2 64, 4u8.
■ Memory: Minimum 2 GB.
■ System: x86, 32-bit or 64-bit processor, 2.6 GHz or faster
■ Disk Space: 10 GB minimum free (at least 3 GB free on the system drive)
■ Browser: Internet Explorer 7.x, 8.x, 9.x, Firefox 3.5/3.6, 6.x
■ Database: Oracle EE 10g or 11g, XE 10g
■ Application Server: Oracle WebLogic 11g (10.3.5.0). Oracle Application Testing
Suite requires the standard WebLogic Server installation (which includes jrocket
jdk.). It does not support generic versions of WebLogic Server installation (such as
those that use wls1035_generic.jar).
■ Oracle Load Testing Agent also supported on Linux 32-bit & 64-bit, in addition to
Windows 32-bit and 64-bit operating systems listed above
Note: These are minimum requirements only and actual
requirements for the Oracle Load Testing Server will vary depending
on the size and configuration of your load test. If you are running
larger load tests, of greater than 1000 Virtual Users, you should
consider deploying Oracle Load Testing on a faster server class
machine with additional RAM recommended.
Note: Oracle recommends running the Oracle Load Testing Server
and Agents on separate systems for production load testing. The
amount of memory required on the Oracle Load Testing Agent
systems may increase based on the number of Virtual Users that will
be assigned to run on each Agent. For more information, visit the
QA/Testing Technology Center on Oracle Technology Network or
contact your Oracle representative.
5
3.3 Oracle Test Manager
Oracle Test Manager has the following system requirements:
■ Operating System (32-bit and 64-bit versions): Windows XP, Windows Vista,
Windows 2003, Windows 7, Windows 2008, Windows 2008 R2. Oracle Enterprise
Linux 5.1, 5.2, 4u8.
■ Memory: Minimum 2 GB.
■ System: x86, 32-bit or 64-bit processor, 2.6 GHz or faster
■ Disk Space: 10 GB minimum free (at least 3 GB free on the system drive)
■ Browser: Internet Explorer 7.x, 8.x, 9.x, Firefox 3.5/3.6, 6.x
■ Database: Oracle EE 10g or 11g, XE 10g
■ Application Server: Oracle WebLogic 11g (10.3.5.0). Oracle Application Testing
Suite requires the standard WebLogic Server installation (which includes jrocket
jdk.). It does not support generic versions of WebLogic Server installation (such as
those that use wls1035_generic.jar).
3.4 Additional Notes
The following are additional notes about system requirements:
■ The ATS installer can automatically install and configure an Oracle 10g Express
Edition (XE) database for use with Oracle Load Testing and Oracle Test Manager.
Although this is useful for demos, for production usage switching to Oracle's 11g
Enterprise Edition database is highly recommended. Oracle 11g Standard Edition
and Oracle 10g EE or SE are also supported.
■ System memory requirements do not take into account other processes that may
be running and using memory on your system, reducing free uncommitted
memory available.
■ When installed on the same machine, Oracle Load Testing and Oracle Test
Manager will run on the same server and use shared system resources. Oracle
Functional Test/OpenScript is a separate application that have its own memory
and CPU requirements.
■ The ATS products will run in 32-bit compatibility mode when installed on 64-bit
operating systems. It is possible for Oracle Application Testing Suite to be installed
on an existing WebLogic server. However, if the pre-installed WebLogic server is
JRockit plus WebLogic (64-bit) environment, some functions in Oracle Application
Testing Suite will not work properly. Oracle Application Testing Suite can be
installed on a 32-bit WebLogic, but not a 64-bit.
■ The legacy Oracle Functional Testing, VB-based scripting platform and associated
components (such as Job Scheduler) are no longer included with the ATS installer
Note: These are minimum requirements only and actual
requirements for Oracle Test Manager will vary depending on the
quantity of test assets stored and number of concurrent users
accessing the application. If you have a large quantity of test cases,
requirements or issues stored and/or are deploying Oracle Test
Manager for a team greater than 10 users, you should consider
deploying Oracle Test Manager on a faster server class machine with
additional RAM recommended.
6
starting with version 9.2. Customers that still require this product should -
Error while running ADF-BC Test Suite from command line
Hi,
I have created a separate test project containing the Test Suite for the Model componenet of my ADF-BC application.
I need to run this test project separately from jmeter.
The tests run fine from Jdev, But when I package the test project into a jar and try to run from command line, I get the following error:
java.lang.NoClassDefFoundError: oracle/jbo/ApplicationModule
at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<init>(ServiceAMFixture.java:36)
at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<clinit>(ServiceAMFixture.java:15)
at com.oracle.cs.cap.module.view.EntitlementReportDurationViewVO.EntitlementReportDurationViewVOTest.<init>(EntitlementReportDurationViewVOTest.java:11)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.junit.internal.runners.JUnit4ClassRunner.createTest(JUnit4ClassRunner.java:72)
at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:79)
at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
at org.junit.runners.Suite.access$000(Suite.java:26)
at org.junit.runners.Suite$1.run(Suite.java:93)
at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
at org.junit.runners.Suite.run(Suite.java:91)
at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
at org.junit.internal.runners.CompositeRunner.run(CompositeRunner.java:28)
at org.junit.runner.JUnitCore.run(JUnitCore.java:130)
at org.junit.runner.JUnitCore.run(JUnitCore.java:109)
at org.junit.runner.JUnitCore.run(JUnitCore.java:100)
at org.junit.runner.JUnitCore.runMain(JUnitCore.java:81)
at org.junit.runner.JUnitCore.main(JUnitCore.java:44)
Caused by: java.lang.ClassNotFoundException: oracle.jbo.ApplicationModule
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 27 more
The Test project jar is created as ADF Library JAR File with Model.jpr as the dependent project. This takes care of project class dependencies
All the adf library dependencies are added to the manifest file of the Test Project jar referring to a location lib/ in the jar file directory.
I tried creating the ApplicationModule using both Configuration class (Configuration.createRootApplicationModule) as well as using the JDBC Connection String but both fail when I run the test cases independently from jmeter.
Anybody came across such an error? Please help.
Thanks,
SapnaHi Timo,
Im using JDev version 11.1.1.6.0.
I checked the class path on the jdev console. All the library references are mentioned in the manifest.mf classpath of the test project like below:
Manifest-Version: 1.0
Class-Path: lib/identitystore.jar
lib/adfm.jar
lib/groovy-all-1.6.3.jar
lib/adftransactionsdt.jar
lib/adf-dt-at-rt.jar
lib/adfdt_common.jar
lib/adflibrary.jar
lib/xmlparserv2.jar
lib/db-ca.jar
lib/jdev-cm.jar
lib/ojmisc.jar
lib/commons-el.jar
lib/jsp-el-api.jar
etc...
So I expect the library references should be resolved looking at the manifest file.
Another set of entries that I see in the jdev classpath are related to the Model project which is under test.
-classpath
D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\.adf;
D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\Model\classes;
How do I put these entries into my class path? Will it be sufficient if I add the Model.jar into my test project classpath?
Thanks,
Sapna -
Error in Testing the configuration
Hi All,
In File to IDoc scenarion when I am testing the Configuration in the ID-> Testconfiguration
Sender Agreement, Receiver Determination and Interface Determination is displaying as green but Interface mapping showing as red. IR there is no error in Interface Mapping.
I am getting the following error in Interface mapping.
*Interface Mapping
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor642.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy189.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_EMPData_HRMD_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor642.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy189.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor642.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy189.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more
IN the ID we are having the Interface Mapping.
Anybody can help me on this?
Regards
SReeHi Per,
while testing the configuration, by copying the payload from the Message Mapping(after emtering the values in Message and source xml) and placed in thte Configuration Testing.
As part of Payload the -(hypen) placed in front of the XML tags in the Payload, So that error repeats, When deleted those -'s it works properly.
Regards
Sridhar goli -
[New Release] Oracle Application Testing Suite 12.5.0.1.0
Hi All,
OATS new release available, please check : http://www.oracle.com/technetwork/oem/app-test/index-084446.html
From Release Notes
Oracle Application Testing Suite 12.5.0.1 - New Features and Updates
Support for Chrome 32 browser - Oracle OpenScript includes support for the Chrome 32 browser for playback.
Support for Firefox 31 browser - Oracle OpenScript includes support for the Firefox 31 browser for record and playback.
Support for Internet Explorer 10 and 11 browser - Oracle OpenScript includes support for Internet Explorer 10 browser for playback on Windows 7 SP1 and Windows 8.
New movie recording of playback feature - Oracle OpenScript includes a new movie recording feature that allows recording and playback of a movie file showing the playback of OpenScript functional test scripts.
New advanced VU start, stop, and ramp features added to Oracle Load Testing - Oracle Load Test includes new features that provide advanced control over script start, stop, and ramp up conditions a the script level.
Support for Internet Explorer 10 and 11 browser - Oracle Load Testing and Oracle Test Manager include support for Internet Explorer 10 browser for playback on Windows 7 SP1 and Windows 8.
New Lightweight Directory Access Protocol (LDAP) authentication feature added for Oracle Test Manager - Oracle Test Manager Administrator tool includes new features for configuring the LDAP server to use for authentication.
-POPSI have a similar problem with the OATS v9.20 installation. I did manage to install it on our main load generator (running Windows 2003 Server) but when it came to installing OpenScript on my laptop (XP SP3) the install 'hangs' at 78%.
I did raise a support call with Oracle about this (there was a bug report generated) but the case is still open.
I've been waiting to hear when the next version was due (in the hope that this might have been resolved) but by the sounds of it there could still be an issue on WinXP with v9.21?
For reference I originally logged this with the following in the description:
The installation looks like it is failing because of a double backslash in a path ending "OATS920\\bin\copyOUI.bat". We then get an error in javaw.exe which when OK'ed then stops the installation at the stage "creating 'Uninstall Oracle Application Testing Suite' in folder 'Oracle Application Testing Suite' ". -
Error while running test suite
Hi,
I have installed TCL-8.5 on unix platform and configured Berkely DB with test suite.
I then followed steps given in guide to run the test suite. On running the command
"% source ../test/test.tcl", following error occurs.
% source ../test/test.tcl
couldn't load file ".libs/libdb_tcl-4.6.so": .libs/libdb_tcl-4.6.so: ELF file OS ABI invalid
Could you please help me on this?
Thanks
AmanI have compiled tcl8.5 and run some simple tests using Berkeley DB, and it appears that Berkeley DB is fine with tcl8.5 (as well as tcl8.4).
Searching for the error "ELF file OS ABI invalid" it seems to arise when people mix binaries from different platforms, for example attempting to use a Linux binary on a FreeBSD platform. Did you compile Tcl8.5 on the same platform you used for compiling Berkeley DB?
Regards,
Carol -
How do emulate multiple calls to same end point in Composite Test Suite
Can any one help with a problem I face with a composite test suite? I have a composite that has 5 main activities and after each activity it logs a status in a business database. This uses the same end point each time to log a status just passing a different status at each point.
When I create a test in the SOA Suite test suite I can create an Assertion for the first status call to check that the status us being created correctly but the second time the end point gets called the status is different and therefore the overall test fails.
Does anyone know how I can create multiple assertions in a test for the same end point in the same test?Hi battlFrog,
>>I want to change the end point address to this service that is now in the solution, but not sure what the address would be.
What do you mean about the above message? I wonder if you want to let the client to reference to the service which is now in the solution, but not pointing to a service on your test server. If so, first please try to make sure that service
which is now in the solution can work well. After that please try to use the "Add Services Reference" to help you reference the service which is now in the solution. Once it finishes, you can get the correct endpoint address in your client config
file.
Besides, if your service is a self-host application, you can change the service address in the service side by modifying the baseaddress, if your service host in the IIS, you can modify the service address by doing some IIS configuration.
If I have misunderstood you, please feel free to let me know.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
I have developed a composite application that contains two bpel processes(process1 and process2). Process1 is the entry point.
1) Process1 has few activities and invokes process2.
2) Process2 invokes the db adapter to insert a record in table.
3) I have created a test suite in jdeveloper and deployed the application.
4) In EM console, I navigated to “unit tests” tab to test.
5) Test passes successfully with all activities executed in process1.
Question:
I’m not able to see any instance of process2 and also cannot see any record getting inserted in the table. Just to make sure there are no issues in process2, I tested process2 alone, the record is getting inserted successfully. Am I missing any configurations to test bpel process interactions in composite without emulations?
Kindly help me solve this issue.Anyways i found the solutions to this, i was creating the second bpel process with expose as SOAP service checkbox selected, by unselecting it, my process2 was invoked from process1 and i could see process2 getting instantiated.
-
Satellite A200: Modem has an error 633: already in use or is not configured properly
My notebook is A200-FE0.
When I tried to make a dial-up connection, there is an error window says:
"Error 633: The modem (or other connecting device) is already in use or is
not configured properly".
When I test my modem by clicking query modem on the Diagnostics tab in the modems tool in
Control Panel, the modem responds normally and appear to be working
correctly.
When I test my modem by using the Toshiba diagnostic tools, it shows "pass" and I canhear the dail tone too.
I tired to uinstall and reinstall the driver twice.
But I just can't make a dial-up connection and keep getting the error 633. I am really upset about it.
Please help me! Thank you a lot!Thanks for the hint.
I tried this method too. I am using windows vista home premium. I can't find the files named telephon.ini and tapiini.exe in my computer.
I noticed that this method is only for windows 98 and windows ME. -
Error when trying to deploy a project's test suite
I recently found that emacs auto-saved files triger what, imho, is a bug. Say you have a file called a.xml in your test suite's message directory. Emacs will auto-save it as #a.xml#. Now Whenever you try to deploy said test suite, you'll get something like:
Copying suite 'SOME_TEST_SUITE' message files...
-- ERROR --
.../SOME_TEST_SUITE/messages (Is a directory)Just watch out for funnily named files and move them away.Hi,
you may use the repository assistant to add an existing db user as target user to your repository (owned by the control center). Using design center, create a location (in your design repository) pointing to that user. Use this location for your target module.
The different architectures are explained in the document "OWB Installation and Configuration Guide for Microsoft Windows and UNIX.pdf", chapter 2 "Installing an Oracle Warehouse Builder Repository".
Of course you can do all this by using only OMBPlus. But using the GUI is somehow more straight forward.
Regards,
Carsten. -
Hi
I recently integrated Berkeley DB 4.6.19 with my application to run it on embedded linux. I now need test suite to test the integration. Is the test suite available for download on oracle website or I need to ask for a license for that?
Regards
AmanHello,
Is there any reason you can not configure with:
--enable-test
To build the Berkeley DB test suite, enter --enable-test as an argument to configure.
To run the Berkeley DB test suite, you must also build the Tcl API. This argument
should not be specified when configuring to build production binaries.
--enable-tcl
To build the Berkeley DB Tcl API, enter --enable-tcl as an argument to configure. This configuration argument expects to find Tcl's tclConfig.sh file in the /usr/local/lib directory.
See the --with-tcl argument for instructions on specifying a non-standard location for the Tcl installation. See Loading Berkeley DB with Tcl for information on sites from which you can download Tcl and which Tcl versions are compatible with Berkeley DB. To build Tcl, you must also build with shared libraries.
--with-tcl=DIR
To build the Berkeley DB Tcl API, enter --with-tcl=DIR, replacing DIR with the directory in which the Tcl tclConfig.sh file may be found. See Loading Berkeley DB with Tcl for information on sites from which you can download Tcl and which Tcl versions are compatible with Berkeley DB. To build Tcl, you must also build with shared libraries.
from:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/build_unix/conf.html
Thanks,
Sandra -
Using Test Plan and Test Suites as work items
Hi everybody.
I need to incorporate the new feature of TFS 2013 that let me manage Test Plans and Test Suites as work ítems to my current TFS environment. I have TFS 2013 Update 3 (12.0.30324); I guess this feature was released after the release I have.
So, my questions are:
- How can I integrate the work ítem definitions to my process template? I'm using a customized version of CMMI 12.2 and this version didn't have this elements as work ítems.
- How can I adjust the existing data of all my Team Projects in order to use this functionality?
- Is there any impact on the existing Reporting Services reports? or the new process template have incorporated the appropiated changes?
- Do I need to upgrade my TFS Server? If so, a migration process is needed?
Any help will be appreciated.
Best regards.Hi AjdPC,
Thanks for your post.
Yes, this feature released in TFS 2013 Update 3. But as the TFS 2013 Update 4 has released too, so we suggest you upgrade your TFS to TFS 2013 Update 4.
After you upgraded to TFS 2013 Update 4, if you want use this feature in the old/upgraded team projects, you need configure features for these team project, please refer to the detailed information in this document:
https://msdn.microsoft.com/en-us/library/ff432837.aspx. For example, if one your upgraded team project created using CMMI 12.2, open this team project’s Web Access admin page, click
Configure Features>>select the CMMI 2013.4 in the
Choose a process template to continue textbox, then click Configure button.
For the custom process templates, we suggest you download the new 2013.4 versions process template from your collection after upgraded to TFS 2013 Update 4, then custom that 2013.4 process templates to instead of that old customized 12.2 process templates,
then upload the new customized process templates to your collection and create team project use them if you want.
That not impact your Reporting Services reports.
As I said, we suggest you upgrade to TFS 2013 Update 4, In-place upgrade or migrate upgrade both are ok.
Note: make the full backup for your TFS Server databases before any upgrade or migrate operation.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Run several test suites in sequence
Hi,
I have several test suites. I would like to run each of them in sequence because each has its own configuration. If I did the following, tests from different suites will be mixed with others while running.
testRunner.test = new Suite1();
testRunner.startTest();
testRunner.test = new Suite2();
testRunner.startTest();
testRunner.test = new Suite2();
testRunner.startTest();
Anyone has ideas how to solve this?
Thanks,
DinaHi,<br /><br />Surely the ability to add test suites to test suites (the composite pattern) already allows this?<br /><br />Cheers,<br /><br />Ali<br /><br /><br />On 01/02/2009 02:03, "Daniel Rinehart" <[email protected]> wrote:<br /><br />A new message was posted by Daniel Rinehart in<br /><br />FlexUnit Development --<br /> Run several test suites in sequence<br /><br />A couple of suggestions. Dynamically create a new testRunner for each<br />TestSuite, that way you can run them in sequence. Each test runner<br />could be thrown into a tab navigator to easily view the results. The<br />TestRunnerBase fires a TestsCompleteEvent which could be used to<br />execute the next suite. The reporting of total tests across all suites<br />could be done with a custom TestListener.<br /><br />-- Daniel R. <[email protected]> [http://danielr.neophi.com/]<br /><br />> I have several test suites. I would like to run each of them in sequence<br />> because each has its own configuration. If I did the following, tests from<br />> different suites will be mixed with others while running.<br />><br />> testRunner.test = new Suite1();<br />> testRunner.startTest();<br />> testRunner.test = new Suite2();<br />> testRunner.startTest();<br />> testRunner.test = new Suite2();<br />> testRunner.startTest();<br /><br /><br />------------------------------------------------------<br />View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b799c6/0><br />Replies by email are OK.<br />Use the unsubscribe form at <a href=http://www.adobeforums.com/webx?280@@.59b799c6!folder=.59b62b92> to cancel your email subscription.
Maybe you are looking for
-
SQL Developer 3.0.04 and 3.1 wont open
I upgraded to OS X Lion today and SQL Developer stopped working. I think I've narrowed it down to missing Java installation even tho I have installed the JDK from apple from connect.apple.com? Contents of sqldeveloper-Darwin.conf: AddVMOption -Dcom.a
-
Import mpg video into Premiere Pro CS6
When I try to import video taken with a Sony Handicam DCR SX63 I get a "There was an error decompressing audio or video". In searching this issue I find many people with the same issue but never a resolution. Is there one? That a novice could impleme
-
Hello, I have installed SAP GUI 7.10 and everything is working fine, but the bex analyzer. The problem is that I can see the Toolbox but when Im clicking on the icons of the toolbox it does not work at all, it does not execute anything, so i can not
-
Hi I have downloaded Foundation Services(all the 3 parts), Essbase and Planning from edelivery site. But I am not able to start with the installation as all zip files have assembly.dat files. I cannot find any setup files. How should I go about the i
-
Hi my mum just did a sync of her iphone and lost all the old photos(it didnt warn her this would happen) of her dad who passed away, there not on her computer as she had a virus and lost the lot and now there off her phone, please someone tell me tha