 |
 |
| |
|
Viewing By Entry
|
 |
| |
|
|
| |
|
|
| |
Session replication is a feature of the JRun 4 server where session data from a server instance that partipates in a cluster propagates that data via RMI to other session buddies in the JRun cluster. For ColdFusion MX 6.x and 7.x servers that run on a JRun 4 cluster, there are several situations that might result in the following error appearing in the JRun server's out.log: The web application 'cfusion-ear#cfusion-war' could not be found to accept sessions for replication
When a cluster member comes back online after a failure while session replication is enabled, JRun server attempts to restore the session back to the appropriate web application (i.e. ColdFusion MX server) running in the J2EE container. While the server instance is starting up, JRun will attempt to recover the sessions, even if the web application is not fully loaded. This error will be logged for for every session replication attempt until the web application fully loads. When the web application successfully loads, the sessions should be recovered and any session replication errors that occur during that interim can be ignored. Bug 59101 has been logged for this benign error in this context, and is expected to be included in a later release.
Below is an example of the servers out.log that illustrates the session replication error occuring while a failed server instance is starting up but has not fully loaded its web application (ColdFusion MX server): 02/09 12:00:44 user RDSDispatchServlet: init
02/09 12:00:44 info Deploying web application "Macromedia Coldfusion MX" from: file:/C:/JRun4/servers/cfmx61/cfusion/
02/09 12:00:44 user JSPServlet: init
02/09 12:00:45 warning The web application 'cfusion-ear#cfusion-war' could not be found to accept sessions for replication
02/09 12:00:46 user CfmServlet: init
02/09 12:00:47 user FlashGateway: init
02/09 12:00:47 user FlashGateway: init
02/09 12:00:47 user ColdFusionStartUpServlet: init
02/09 12:00:47 user ColdFusionStartUpServlet: init
02/09 12:00:47 user ColdFusionStartUpServlet: ColdFusion MX: Starting application services
02/09 12:00:47 user ColdFusionStartUpServlet: ColdFusion MX: VM version = 1.4.2_05-b04
- Starting logging...
0 [scheduler-9] INFO coldfusion.server - Starting logging...
02/09 12:00:48 warning The web application 'cfusion-ear#cfusion-war' could not be found to accept sessions for replication.
02/09 12:00:48 warning The web application 'cfusion-ear#cfusion-war' could not be found to accept sessions for replication
02/09 12:00:49 warning The web application 'cfusion-ear#cfusion-war' could not be found to accept sessions for replication
02/09 12:00:50 user ColdFusionStartUpServlet: ColdFusion MX: application services are now available
02/09 12:00:50 user CFCServlet: init
02/09 12:00:50 user CFCServlet: init
02/09 12:00:50 user AdminServlet: init
02/09 12:00:50 user AdminServlet: init
02/09 12:00:50 info Deploying enterprise application "default-ear" from: file:/C:/JRun4/servers/cfmx61/default-ear/
02/09 12:00:51 info Deploying web application "JRun Default Web Application" from: file:/C:/JRun4/servers/cfmx61/default-ear/
02/09 12:00:52 info Web Services in default-ear#default-war:
02/09 12:00:52 info AdminService
02/09 12:00:52 warning default-war web application has 'reload' as true in jrun-web.xml. Consider setting it false if the application is running in production environment.
02/09 12:00:52 warning default-war web application has 'compile' as true in jrun-web.xml. Consider setting it false if the application is running in production environment.
02/09 12:00:52 user JSPServlet: init
02/09 12:00:52 info Deploying enterprise application "JRun 4.0 Internal J2EE Components" from: file:/C:/JRun4/lib/jrun-comp.ear
02/09 12:00:52 info Deploying EJB "JRunSQLInvoker" from: file:/C:/JRun4/lib/jrun-comp.ear
Server cfmx61 ready (startup time: 16 seconds)
Other known causes of this error include the following when session replication is enabled: - The jrun-web.xml for the ColdFusion server web application should have the persistence-config/active node set to false or else the error will occur since ColdFusion sessions should not be persisted to disk.
- The path to cfusion.jar and WEB-INF/cfusion/lib should not occur in the JRun server's jvm.config file setting for java.class.path. ColdFusion MX 6.1 would incorrectly add those paths to the setting in some configurations.
- The cfapplication tag's attribute for name="" should not be empty. The error will occur when using the NONAME application.
- Having a typo in the java.naming.provider.url setting in jndi.properties file will produce the error.
|
posted on 9 February, 2006 at 12:29 PM.
ColdFusion | Comments (1)
|
|
Comments
|
|
|
|
|
|
Calendar |
|
| |
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| | | | | 1 | 2 | 3 |
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
Search This Site |
|
| |
This is an exact search only
|
|
About This Site |
|
| |
I live west of Boston and used to work at Adobe with ColdFusion and Flex, specializing in Unix & Linux. I recently graduated from CDIA in Pro Digital Photography. Curious about my banner image?
|
|
RSS |
|
| |
|
|
|
Aggregated By |
|
| |
|
|
|
1) I'm using some code to dump info about all active sessions. This tells me what the jsessionid is, what the username is (if they are logged in using cflogin) and the name of the node that the session originally started on. Any sessions that started on a different node. I'm using Windows NLB clustering as well, so I use an external js file that does a document.write to identify the current IIS server.
2) I thought tha session replication would mean that I'd see the same sessions existing on both CF servers, but no. They only show their own sessions.
3) If I kill a node, the sessions move over to the other node, BUT ONLY when the browser makes another request.
Is this normal behaviour? I thought session data would be continously replicated?
Also CFLOGIN is broken; if loginstorage=session is specified, and the node that's running the session is stopped, the other node will ask the user to log in again.