Blog Suche

Kategorien
Letzten Einträge
Letzten Kommentare
<< Januar, 2007 >>
SMDMDFS
123456
78910111213
14151617181920
21222324252627
28293031
Outa Links
Downloads
Applikationen
Archiv
Foto Alben
RSS

Powered by
BlogCFM v1.11

23 January 2007


Das Problem mit dem Cache
Fehlermeldung:

Error Executing Database Query.
[Macromedia][Oracle JDBC Driver][Oracle]ORA-01000: maximum open cursors exceeded

Die Fehlermeldung bekommt wohl jeder mal zu sehen der mit ColdFusion und Oracle arbeitet. Nach einigen Tests konnte ich eine Ursache ermitteln. Der Gebrauch von dem cfqueryparam Tag benötigt jeweils einen offenen Cursor. Hier ist ganz entscheidend  wie im ColdFusion Administrator der Wert für „Max Pooled Statements“ eingestellt ist. Der Wert sollte kleiner sein als die Max Open Cursor bei Oracle, sonst läuft man Gefahr das Oracle die Fehlermeldung bringt. Ein guter Wert für beide Faktoren zu ermitteln wird mir sicherlich noch einiges an Zeit kosten.

Wer diese Fehlermeldung bekommt startet am besten den CF Server neu. Das Neustarten geht sehr schnell und danach kann man die Werte optimieren. Es kann unter Umständen ein paar Sekunden dauern bis die Cursoren aufgelöst werden.

SQL um offene Cursoren abzufragen:

SELECT v.value as numopencursors ,s.machine ,s.osuser,s.username
FROM V$SESSTAT v, V$SESSION s
WHERE v.statistic# = 3 and v.sid = s.sid


UPDATE 02.02.2007
Habe jetzt bei Oracle die Max_Open_Cursor auf 1024 gesetzt und in CF die "Max pooled statements" auf 300. Die Server laufen nun wieder stabil.

Veröffentlicht von gd at 8:14 PM | Link: Das Problem mit dem Cache | 0 comments


22 January 2007


Wenn Gefangene zusammengelegt werden dann spricht man dann von Zellteilung!

Veröffentlicht von gd at 12:00 AM | Link: | 0 comments


04 January 2007


Die Frachtenbörsen Übersicht auf http://www.frachtenboersen.de hat gestern Abend ein neues Gesicht bekommen. Das neue Outfit ist meiner gestrigen Langeweile und der Tatsache das die Seite ein paar Euro in meine Kasse bring zu verdanken.

Veröffentlicht von gd at 2:32 PM | Link: | 0 comments




Newsmeldung der Frachtenbörse TimoCom
Düsseldorf, 29. September 2006 - Wie nicht anders zu erwarten, konnten Besucher der 61. IAA Nutzfahrzeuge in Hannover (Deutschland) auch dieses Jahr wieder viele neue Highlights aus der Transport- und Logistikwelt bestaunen. Dabei war die TimoCom Soft- und Hardware GmbH ebenfalls wieder mit von der Partie. Der Marktführer unter den europäischen Fracht- und Laderaumbörsen bot seinen Standbesuchern dieses Jahr eine ganz besondere Attraktion: Die Online-Version der Fracht- und Laderaumbörse TimoCom TRUCK & CARGO®!

Zur Newsmeldung der Frachtenbörse TimoCom TRUCK & CARGO

Veröffentlicht von gd at 2:27 PM | Link: Newsmeldung der Frachtenbörse TimoCom | 0 comments




CF Scope Types
The following table describes ColdFusion scopes:
Scope Description

Variables (local)

The default scope for variables of any type that are created with the cfset and cfparam tags. A local variable is available only on the page on which it is created and any included pages (see also the Caller scope).

Form

Contains variables passed from a Form page to its action page as the result of submitting the form. (If you use the HTML form tag, you must use method="post".) For more information, see Introduction to Retrieving and Formatting Data.

URL

Contains parameters passed to the current page in the URL that is used to call it. The parameters are appended to the URL in the format ?variablename = value[&variablename=value...]; for example www.MyCompany.com/inputpage.cfm?productCode=A12CD1510&quantity=3.

Note: If a URL includes multiple parameters with the same name, the resulting variable in the ColdFusion URL scope consists of all parameter values separated by commas. For example, a URL of the form http://localhost/urlparamtest.cfm? param=1&param=2&param=3 results in a URL.param variable value of 1,2,3 on the ColdFusion page.

Attributes

Used only in custom tag pages. Contains the values passed by the calling page in the custom tag's attributes. For more information, see Creating and Using Custom CFML Tags.

Caller

Used only in custom tag pages. The custom tag's Caller scope is a reference to the calling page's Variables scope. Any variables that you create or change in the custom tag page using the Caller scope are visible in the calling page's Variables scope. For more information, see Creating and Using Custom CFML Tags.

ThisTag

Used only in custom tag pages. The ThisTag scope is active for the current invocation of the tag. If a custom tag contains a nested tag, any ThisTag scope values you set before calling the nested tag are preserved when the nested tag returns to the calling tag.

The ThisTag scope includes three built-in variables that identify the tag's execution mode, contain the tag's generated contents, and indicate whether the tag has an end tag.

A nested custom tag can use the cfassociate tag to return values to the calling tag's ThisTag scope. For more information, see Accessing tag instance data.

Request

Used to hold data that must be available for the duration of one HTTP request. The Request scope is available to all pages, including custom tags and nested custom tags, that are processed in response to the request.

This scope is useful for nested (child/parent) tags. This scope can often be used in place of the Application scope, to avoid the need for locking variables. Several chapters discuss using the Request scope.

CGI

Contains environment variables identifying the context in which a page was requested. The variables available depend on the browser and server software. For a list of the commonly used CGI variables, see Reserved Words and Variables in CFML Reference.

Cookie

Contains variables maintained in a user's browser as cookies. Cookies are typically stored in a file on the browser, so they are available across browser sessions and applications. You can create memory-only Cookie variables, which are not available after the user closes the browser. Cookie scope variable names can include periods.

Client

Contains variables that are associated with one client. Client variables let you maintain state as a user moves from page to page in an application, and are available across browser sessions. By default, Client variables are stored in the system registry, but you can store them in a cookie or a database. Client variables cannot be complex data types and can include periods in their names. For more information, see Using Persistent Data and Locking.

Session

Contains variables that are associated with one client and persist only as long as the client maintains a session. They are stored in the server's memory and can be set to time out after a period of inactivity. For more information, see Using Persistent Data and Locking.

Application

Contains variables that are associated with one, named application on a server. The cfapplication tag name attribute or the Application.cfc This.name variable setting specifies the application name. For more information, see Using Persistent Data and Locking.

Server

Contains variables that are associated with the current ColdFusion server. This scope lets you define variables that are available to all your ColdFusion pages, across multiple applications. For more information, see Using Persistent Data and Locking.

Flash

Variables sent by a Macromedia Flash movie to ColdFusion and returned by ColdFusion to the movie. For more information, see Using the Flash Remoting Service.

Arguments

Variables passed in a call to a user-defined function or ColdFusion component method. For more information, see About the Arguments scope.

This

Exists only in ColdFusion components or cffunction tags that are part of a containing object such as a ColdFusion Struct. Exists for the duration of the component instance or containing object. Data in the This scope is accessible from outside the component or container by using the instance or object name as a prefix.

function local

Contains variables that are declared inside a user-defined function or ColdFusion component method and exist only while a function executes. For more information, see Writing and Calling User-Defined Functions.


Veröffentlicht von gd at 2:21 PM | Link: CF Scope Types | 0 comments