It defaults to true, that is why you need -WODirectConnectEnabled
false in JavaMonitor.
Chuck
On May 3, 2007, at 3:32 PM, Q wrote:
> WODirectConnectEnabled should default to false unless you
> explicitly set it to true somewhere. Check your app's Properties
> file. WOLips will pass -WODirectConnectEnabled=true as a launch arg
> when running in development mode
>
> On 04/05/2007, at 12:11 AM, Jonathan Ricker wrote:
>
>> Thanks, that's all I needed to hear.
>>
>> On May 3, 2007, at 8:18 AM, Kieran Kelleher wrote:
>>
>>> It is a bug that that is nothing to do with Eclipse/WOLips, just
>>> set it and forget it ......
>>> In Java Monitor the launch args should include -
>>> WODirectConnectEnabled false
>>> <pastedGraphic.tiff>
>>>
>>>
>>> On May 3, 2007, at 7:04 AM, Jonathan Ricker wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm working on upgrading all our apps to using wolips/eclipse.
>>>> I've been deploying the apps by running the build.xml script on
>>>> my development machine and simply copying the application to the
>>>> server. (dev machine, os x, deployment on solaris).
>>>>
>>>> I just noticed that when I try to Refuse New Sessions from Java
>>>> Monitor on a deployment, I get:
>>>>
>>>> Caused by: java.lang.IllegalStateException: Cannot refuse new
>>>> sessions when in development mode (direct connect enabled)
>>>> at
>>>> com.webobjects.appserver.WOApplication.refuseNewSessions
>>>> (WOApplication.java:2551)
>>>> at er.extensions.ERXApplication.refuseNewSessions
>>>> (ERXApplication.java:707)
>>>> at
>>>> com.webobjects.appserver.WOAdminAction.instanceRequestAction
>>>> (WOAdminAction.java:85)
>>>> at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown
>>>> Source)
>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke
>>>> (DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>> at
>>>> com.webobjects.appserver.WODirectAction.performActionNamed
>>>> (WODirectAction.java:128)
>>>> at
>>>> com.webobjects.appserver._private.WOActionRequestHandler._handleReq
>>>> uest(WOActionRequestHandler.java:240)
>>>>
>>>> I'm sure I can solve this by simply adding
>>>> WODirectConnectEnabled=false, but it brings me to another question.
>>>>
>>>> My question relates to how WO determines whether it is in
>>>> development or direct connect mode. The WebObjects Deployment
>>>> guide says the default setting for WODirectConnectEnabled is
>>>> "true during application development, false when an application
>>>> instance runs as part of a deployment." Does this apply to an
>>>> app built with woproject/wolips as well, or do I need to set
>>>> WODirectConnectEnabled explicitly for all the deployments?
>>>>
>>>>
>>>> Thanks for any help/insights on this question.
>>>>
>>>> -- Jonathan
>>>>
>>>>
>>>>
>>>
>>
>
>
>
> --
> Seeya...Q
>
> Quinton Dolan - qdola..mail.com
> Gold Coast, QLD, Australia
> Ph: +61 419 729 806
>
>
>
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Sun May 06 2007 - 12:37:50 EDT