Re: JRun 4 Updater 3 Now Available
Just to clarify. The vast majority of whats in JRun Updater 3 is what was made available to CF customers in CFMX 6.1 Updater 3 gets these fixes to JRun 4 customers. There is a some small number items fixed in Updater 3 that arent in CFMX 6.1.We're working on a cumulative hotfix due in April to make those available for CFMX 6.1 Server-configuration customers. Some other fixes available ***POST-U3*** (didn't make U3) for JRun and CFMX customers through hotfixes + other random thoughts I'll share: (note: all of these will be in the 6.1 cumulative hotfix due in April) - we expect to release new datadirect drivers soon to fix the oracle and sqlserver issues customers have reported (no more data, arrayindexoutofbounds, hangs) with the 3.2 drivers shipped with JRun 4 Updater 2 and CFMX 6.1. They are still in testing mode.JRun4 Updater 3 got the 3.1+ drivers since they were the most stable.3.1+ was also made available as a hotfix for CFMX customers with issues.We expect to replace the 3.1+ for JRun and CFMX customers with newer drivers in the next few weeks if testing goes well. Please email me if you'd like to participate in the beta. - some connector enhancements - including failover in clustering working as expected (we will have a hotfix for this soon- please email me).These fixes are long overdue. - connection pooling fixes for JRun datasources to match the pooling fixes for ColdFusion datasources (see technote below). http://www.macromedia.com/support/coldfusion/ts/documents/conn_pool_hotfix.htm (for apps like AbleCommerce that use JRun datasources ie entered through the JMC and available to all instances).Users of JRun J2EE CFMX versions would need these if they have connection-limited datasources *AND* the underlying application used JRun datasources. This fix will be made available in a few days. - Client variable purge fixes for SQL and registry datasources (there were 4 bugs fixed).This often showed up when the server hung every hour on the hour for the maintenance task of purging client variables older than [N] days. This hits many customers if they use registry and the registry grows to say 50,000 or 100,000+ entries.SQL datasources are recommended but even if users switched, the registry purges still occurred (in addition to SQL purges) and could hang the system.The fix now respects the unchecked purge setting for all client datasource types. These are the ones that come to mind that get reported most often hanging systems. ***For Dick AppleBaum***: 1) JRun and, therefore, CF use the JVM 1.3 instead of 1.4 (even with the fix postedChristian Cantrell's blog site) Part of this is the installer not allowing the selection.There are also issues with using JDK 1.4 (jvm.cfg issues).We've fixed this post-Updater 3 in the launcher.(jrun stub) Please email me and I can get you some code to test. 2) When starting a CF 6.1 JRun server instance, the scheduler does not start (see below). I've heard of this sporadically but can't reproduce it.Perhaps send me your neo-cron.xml and jrun.xml and I'll see if I can repro it on my machine.6.1 definitely massaged this .xml file on an existing server.Perhaps the one in your new instance got corrupted somehow. Regards, Stephen Dupre Macromedia QA [EMAIL PROTECTED] [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: JRun 4 Updater 3 Now Available
Note: I currently have a bug open regarding JRUN 4 Update 3 bug 54614. If you have a context root of / for cfmx. CFMX will not work... this appears to happen under W2k with IIS and Linux with Apache. - Alex -Original Message- From: Stephen Dupre [mailto:[EMAIL PROTECTED] Sent: Friday, March 19, 2004 8:14 AM To: CF-Talk Subject: Re: JRun 4 Updater 3 Now Available Just to clarify. The vast majority of what's in JRun Updater 3 is what was made available to CF customers in CFMX 6.1 Updater 3 gets these fixes to JRun 4 customers. There is a some small number items fixed in Updater 3 that aren't in CFMX 6.1.We're working on a cumulative hotfix due in April to make those available for CFMX 6.1 Server-configuration customers. Some other fixes available ***POST-U3*** (didn't make U3) for JRun and CFMX customers through hotfixes + other random thoughts I'll share: (note: all of these will be in the 6.1 cumulative hotfix due in April) - we expect to release new datadirect drivers soon to fix the oracle and sqlserver issues customers have reported (no more data, arrayindexoutofbounds, hangs) with the 3.2 drivers shipped with JRun 4 Updater 2 and CFMX 6.1. They are still in testing mode.JRun4 Updater 3 got the 3.1+ drivers since they were the most stable.3.1+ was also made available as a hotfix for CFMX customers with issues.We expect to replace the 3.1+ for JRun and CFMX customers with newer drivers in the next few weeks if testing goes well. Please email me if you'd like to participate in the beta. - some connector enhancements - including failover in clustering working as expected (we will have a hotfix for this soon- please email me).These fixes are long overdue. - connection pooling fixes for JRun datasources to match the pooling fixes for ColdFusion datasources (see technote below). http://www.macromedia.com/support/coldfusion/ts/documents/conn_pool_hotf ix.htm (for apps like AbleCommerce that use JRun datasources ie entered through the JMC and available to all instances).Users of JRun J2EE CFMX versions would need these if they have connection-limited datasources *AND* the underlying application used JRun datasources. This fix will be made available in a few days. - Client variable purge fixes for SQL and registry datasources (there were 4 bugs fixed).This often showed up when the server hung every hour on the hour for the maintenance task of purging client variables older than [N] days. This hits many customers if they use registry and the registry grows to say 50,000 or 100,000+ entries. SQL datasources are recommended but even if users switched, the registry purges still occurred (in addition to SQL purges) and could hang the system.The fix now respects the unchecked purge setting for all client datasource types. These are the ones that come to mind that get reported most often hanging systems. ***For Dick AppleBaum***: 1) JRun and, therefore, CF use the JVM 1.3 instead of 1.4 (even with the fix postedChristian Cantrell's blog site) Part of this is the installer not allowing the selection. There are also issues with using JDK 1.4 (jvm.cfg issues).We've fixed this post-Updater 3 in the launcher.(jrun stub) Please email me and I can get you some code to test. 2) When starting a CF 6.1 JRun server instance, the scheduler does not start (see below). I've heard of this sporadically but can't reproduce it. Perhaps send me your neo-cron.xml and jrun.xml and I'll see if I can repro it on my machine.6.1 definitely massaged this .xml file on an existing server.Perhaps the one in your new instance got corrupted somehow. Regards, Stephen Dupre Macromedia QA [EMAIL PROTECTED] _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: JRun 4 Updater 3 Now Available
That's great! If we are running CFMX ENT on JRun, should we wait for a CFMX update that includes this? Thanks, Calvin - Original Message - From: Damon Cooper To: CF-Talk Sent: Thursday, March 11, 2004 8:54 PM Subject: JRun 4 Updater 3 Now Available http://www.macromedia.com/software/jrun/ Next stop: JRun 4.1 and JRun 5! Damon Cooper Dir Engineering, ColdFusion JRun Macromedia [EMAIL PROTECTED] [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: JRun 4 Updater 3 Now Available
On Friday 12 Mar 2004 10:10 am, Calvin Ward wrote: If we are running CFMX ENT on JRun, should we wait for a CFMX update that includes this? I would, as there will probably be other bits'n'pieces in the CF update, and unless you are having issues addressed in the JRun update, you might as well hole off and just have your site down once. -- Tom Chiverton Advanced ColdFusion Programmer Tel: +44(0)1749 834997 email: [EMAIL PROTECTED] BlueFinger Limited Underwood Business Park Wookey Hole Road, WELLS. BA5 1AF Tel: +44 (0)1749 834900 Fax: +44 (0)1749 834901 web: www.bluefinger.com Company Reg No: 4209395 Registered Office: 2 Temple Back East, Temple Quay, BRISTOL. BS1 6EG. *** This E-mail contains confidential information for the addressee only. If you are not the intended recipient, please notify us immediately. You should not use, disclose, distribute or copy this communication if received in error. No binding contract will result from this e-mail until such time as a written document is signed on behalf of the company. BlueFinger Limited cannot accept responsibility for the completeness or accuracy of this message as it has been transmitted over public networks.*** [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: JRun 4 Updater 3 Now Available
I just installed the updater on Mac OS X -- there are at least 2 issues: 1) JRun and, therefore, CF use the JVM 1.3 instead of 1.4 (even with the fix postedChristian Cantrell's blog site) 2) When starting a CF 6.1 JRun server instance, the scheduler does not start (see below) Thoughts? Dick Starting Macromedia JRun 4 (Build 54102), cfmx61 server 03/12 06:05:36 user FileServlet: init 03/12 06:05:46 info JRun Naming Service listening on *:2909 03/12 06:05:47 error SchedulerService not started jrunx.kernel.ServiceException: SchedulerService not started at jrunx.kernel.ServiceAdapter.scheduleRunnable(ServiceAdapter.java:743) at jrun.security.SecurityContextCache.putLocal(SecurityContextCache.java: 170) at jrun.security.SecurityContextCache.put(SecurityContextCache.java:191) at jrun.security.JRunSecurityManagerService.createSecurityContext(JRunSecur ityManagerService.java:402) at jrun.security.JRunSecurityManagerService.authenticateSecurityContext(JRu nSecurityManagerService.java:371) at jrun.security.JRunSecurityManagerService.authenticateSecurityContext(JRu nSecurityManagerService.java:317) at jrun.security.JRunSecurityManagerService.authenticateSecurityContext(JRu nSecurityManagerService.java:251) at jrun.security.JRunSecurityManagerService.authenticateSecurityContext(JRu nSecurityManagerService.java:244) at jrun.naming.NamingService.authenticate(NamingService.java:835) at jrun.naming.NamingService.handleRequest(NamingService.java:590) at jrun.naming.NamingNetworkService.invokeRunnable(NamingNetworkService.jav a:182) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java :451) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) 03/12 06:05:51 info No JDBC data sources have been configured for this server (see jrun-resources.xml) 03/12 06:05:51 info JRun Web Server listening on *:8101 03/12 06:05:52 user JMCSession: init 03/12 06:05:52 info JRun Proxy Server listening on *:51002 03/12 06:05:52 warning Deployer Service failed to deploy file:/Applications/JRun4/servers/cfmx61/.FBCLockFolder/ * Unrecognized deployment: file:/Applications/JRun4/servers/cfmx61/.FBCLockFolder/ 03/12 06:05:53 info Deploying web application CFMX RDS Application from: file:/Applications/JRun4/servers/cfmx61/CFIDE/ 03/12 06:05:54 user JSPServlet: init 03/12 06:05:55 user RDSDispatchServlet: init 03/12 06:05:57 info Deploying web application Macromedia Coldfusion MX from: file:/Applications/JRun4/servers/cfmx61/cfusion/ 03/12 06:05:58 user JSPServlet: init 03/12 06:05:59 user CfmServlet: init 03/12 06:06:01 user FlashGateway: init 03/12 06:06:01 user FlashGateway: init 03/12 06:06:03 user ColdFusionStartUpServlet: init 03/12 06:06:03 user ColdFusionStartUpServlet: init 03/12 06:06:03 user ColdFusionStartUpServlet: ColdFusion MX: Starting application services 03/12 06:06:03 user ColdFusionStartUpServlet: ColdFusion MX: VM version = 1.3.1_03-76 - Starting logging... 0 [scheduler-1] INFO coldfusion.server- Starting logging... 03/12 06:06:19 user ColdFusionStartUpServlet: ColdFusion MX: application services are now available 03/12 06:06:19 user CFCServlet: init 03/12 06:06:19 user CFCServlet: init 03/12 06:06:20 user AdminServlet: init 03/12 06:06:20 user AdminServlet: init 03/12 06:06:20 info Deploying enterprise application default-ear from: file:/Applications/JRun4/servers/cfmx61/default-ear/ 03/12 06:06:21 info Deploying web application JRun Default Web Application from: file:/Applications/JRun4/servers/cfmx61/default-ear/ 03/12 06:06:30 info Web Services in default-ear#default-war: 03/12 06:06:30 info AdminService 03/12 06:06:30 user JSPServlet: init 03/12 06:06:31 info Deploying enterprise application JRun 4.0 Internal J2EE Components from: file:/Applications/JRun4/lib/jrun-comp.ear 03/12 06:06:32 info Deploying EJB JRunSQLInvoker from: file:/Applications/JRun4/lib/jrun-comp.ear 03/12 06:06:34 info Deploying enterprise application Flash Remoting EAR from: file:/Applications/JRun4/lib/flashgateway.ear 03/12 06:06:35 info Deploying web application Flash Remoting from: file:/Applications/JRun4/lib/flashgateway.ear 03/12 06:06:36 user JSPServlet: init 03/12 06:06:37 user FlashGatewayServlet: init Server cfmx61 ready (startup time: 68 seconds) [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: JRun 4 Updater 3 Now Available
I installed SP3 on my CFMX/JRun 4 install after looking at the release notes...seems ok but I have not run any thorough tests. Although this known issue scares me. Basically says clustering doesn't work. 50179 - A down machine in a cluster with multiple machines is not detected immediately. This can hold up processing for minutes and the requests often get routed to the server that is down. We've seen this in-house and could never nail down if it was a config issue or a bug. Stace _ From: Thomas Chiverton [mailto:[EMAIL PROTECTED] Sent: Friday, March 12, 2004 5:47 AM To: CF-Talk Subject: Re: JRun 4 Updater 3 Now Available On Friday 12 Mar 2004 10:10 am, Calvin Ward wrote: If we are running CFMX ENT on JRun, should we wait for a CFMX update that includes this? I would, as there will probably be other bits'n'pieces in the CF update, and unless you are having issues addressed in the JRun update, you might as well hole off and just have your site down once. -- Tom Chiverton Advanced ColdFusion Programmer Tel: +44(0)1749 834997 email: [EMAIL PROTECTED] BlueFinger Limited Underwood Business Park Wookey Hole Road, WELLS. BA5 1AF Tel: +44 (0)1749 834900 Fax: +44 (0)1749 834901 web: www.bluefinger.com Company Reg No: 4209395 Registered Office: 2 Temple Back East, Temple Quay, BRISTOL. BS1 6EG. *** This E-mail contains confidential information for the addressee only. If you are not the intended recipient, please notify us immediately. You should not use, disclose, distribute or copy this communication if received in error. No binding contract will result from this e-mail until such time as a written document is signed on behalf of the company. BlueFinger Limited cannot accept responsibility for the completeness or accuracy of this message as it has been transmitted over public networks.*** _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: JRun 4 Updater 3 Now Available
I installed SP3 on my CFMX/JRun 4 install after looking at the release notes...seems ok but I have not run any thorough tests. Although this known issue scares me. Basically says clustering doesn't work. 50179 - A down machine in a cluster with multiple machines is not detected immediately. This can hold up processing for minutes and the requests often get routed to the server that is down. We've seen this in-house and could never nail down if it was a config issue or a bug. Amen. We've had this problem for a while ourselves, and it's such a pain in the butt. I guess U3 does nothing to alleviate the bug (which is what I think it is). I'm curious as to whether this is an issue only if StickySessions are enabled, disabled, or either. Regards, Dave. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: JRun 4 Updater 3 Now Available
Not sure...we usually have sticky sessions enabled. -S _ From: Dave Carabetta [mailto:[EMAIL PROTECTED] Sent: Friday, March 12, 2004 10:28 AM To: CF-Talk Subject: RE: JRun 4 Updater 3 Now Available I installed SP3 on my CFMX/JRun 4 install after looking at the release notes...seems ok but I have not run any thorough tests. Although this known issue scares me. Basically says clustering doesn't work. 50179 - A down machine in a cluster with multiple machines is not detected immediately. This can hold up processing for minutes and the requests often get routed to the server that is down. We've seen this in-house and could never nail down if it was a config issue or a bug. Amen. We've had this problem for a while ourselves, and it's such a pain in the butt. I guess U3 does nothing to alleviate the bug (which is what I think it is). I'm curious as to whether this is an issue only if StickySessions are enabled, disabled, or either. Regards, Dave. _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: JRun 4 Updater 3 Now Available
Is this same for CFMX 6.1 running on JRun? :-D Stace _ From: Damon Cooper [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 8:54 PM To: CF-Talk Subject: JRun 4 Updater 3 Now Available http://www.macromedia.com/software/jrun/ Next stop: JRun 4.1 and JRun 5! Damon Cooper Dir Engineering, ColdFusion JRun Macromedia [EMAIL PROTECTED] _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
