Anyone who has run int issues with AXIS and log4J jar conflicts is someone who'd want multiple JVM configs. Id recommend anyone using multiple instances (for distinct applications) to use a separate jvm.config pointing to a separate install of JRE.
This allows you to independantly run different versions of JRE. For example, 1.6 for cf8 and 1.4 for cf7 instanes. It also lets you have an independant lib\ext folder in each JRE setup to resolve any JAR conflicts with CF built in classes. Pat On Oct 22, 12:17 pm, "Charlie Arehart \(lists account\)" <[EMAIL PROTECTED]> wrote: > Andrew (and others), you don't want to say that this isn't a problem on > Windows. It'll bite anyone using the multiserver (multiple instance) > configuration. > > As MrBuzzy hinted, it is that the default setup of the multiserver config is > to have all instance share on jvm.config, and that's where you tell CF what > port to use for the new CF8 debugger. > > The problem is that if any of the instances are up when another instance > tries to come up, the other instances won't come up because the port is > already in use. It can be tricky knowing what's happening and why. A real > common example of this is that the cfusion instance goes down but the admin > instance stays up. In this case, you only have 1 CF instance, but it doesn't > matter. > > So MrBuzzy indicates that you need to create a separate jvm.config for each > instance, but adds "who'd wannna do that[?]" Well, anyone who wants to use > the debugger in multiserver mode will need to. No way around it (well, at > least if one instance may ever go down). > > A couple blog entries discuss setting that up (not specific to the problem > of the debugger but just for those who wanted to do it in general, such as > perhaps to have other different JVM settings): > > http://mkruger.cfwebtools.com/index.cfm/2006/4/17/multiserverhttp://www.alagad.com/go/blog-entry/cf7-cf8-jrun-and-the-jvm > > HTH > > /charlie > > _____ > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of Andrew Scott > Sent: Thursday, October 18, 2007 7:41 PM > To: [email protected] > Subject: [cfaussie] Re: Anyone seen this error before? > > Actually under windows it isn't a problem, but under Linux for some reason > it is a problem. The thing is that it works fine if you first change the > setting, and restart ./jrun -start cfusion but once the server is rebooted > the admin and cfusion refuse to start at all because of this error. > > There is just not enough documentation to get this to work at the moment, > hopefully Adobe can shed some light at some point. > > Andrew Scott > Senior Coldfusion Developer > Aegeon Pty. Ltd.www.aegeon.com.au > Phone: +613 8676 4223 > Mobile: 0404 998 273 > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of MrBuzzy > Sent: Thursday, 18 October 2007 6:51 PM > To: [email protected] > Subject: [cfaussie] Re: Anyone seen this error before? > > This one is a bit of a pain when using the default multi-server setup. > > There's only one jvm.config to edit, making the debug port the same for all > CF instances. > > There are ways to have more than one jvm.config but bah, who'd wannna do > that. > > On 10/18/07, Andrew Scott <[EMAIL PROTECTED]> wrote: > > Yeah it was the debugger, apparently something else had taken over that > port. > > Andrew Scott > Senior Coldfusion Developer > Aegeon Pty. Ltd.www.aegeon.com.au > Phone: +613 8676 4223 > Mobile: 0404 998 273 > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of Dale Fraser > Sent: Thursday, 18 October 2007 3:23 PM > To: [email protected] > Subject: [cfaussie] Re: Anyone seen this error before? > > Its related to the debugger, google that second line and there are lots of > references. > > Regards > > Dale Fraser > > http://learncf.com > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of Andrew Scott > Sent: Thursday, 18 October 2007 2:55 PM > To: [email protected] > Subject: [cfaussie] Anyone seen this error before? > > This is a multi server configuration, jrun is running fine, cfusion is not > and the error in the logs are. > > FATAL ERROR in native method: JDWP No transports initialized, > jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) > > ERROR: transport error 202: bind failed: Address already in use > > ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) > > JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized > [../../../src/share/back/debugInit.c:690] > > Andrew Scott > Senior Coldfusion Developer > Aegeon Pty. Ltd.www.aegeon.com.au > Phone: +613 8676 4223 > Mobile: 0404 998 273 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
