Oh and NOW I can switch debugging on and off at whim, without a restart.

So something is up. Am not sure what though. And it's not interesting 
enough for me to look into further (no offence ;-)

I'll leave if with you OpenBD boffins...

-- 
Adam



On Tuesday, 9 April 2013 14:44:44 UTC+12, Adam Cameron wrote:
>
> I'm running the "Ready2Run" version, which I run via a batch file which 
> executes the JAR file. Between changes was completely shutting that down 
> (CTRL-C which fires a shutdown), and restarting. The Java instance was 
> definitely ending and starting again.  I dunno if there's anything else I 
> should do?
>
> That said, after some delay I just shut OpenBD down again and restarted 
> (to verify what I was saying in this post), and on a whim retested and now 
> the debugging IS showing up).
>
> There is no doubt I had not already done this a few times during 
> experimenting before.
>
> I think there is some sort of irregular issue here? Does it take a while 
> for the config to be written back to file or something, and I was 
> stopping/starting too soon?
>
> Odd.  it doesn't impact me at all, but it's worth being aware of, perhaps.
>
> -- 
> Adam
>
>
>
>
> On Tuesday, 9 April 2013 14:33:16 UTC+12, Al Holden wrote:
>>
>>  I've noticed that - when publishing my Open Desktop WARs to Tomcat on 
>> AWS.
>> For just about any Admin (bluedragon.xml) change to take effect 
>> (datasource, mail server, etc), I need to bounce the whole J2EE engine.
>> Al
>>
>> On 4/8/2013 6:50 PM, Marcus F wrote:
>>  
>> I just tried, and have almost the same experience as Adam.
>>
>> I enable debugging output, check all the boxes, add local ip, save 
>> settings and reload a test page: No change.
>> I restart OpenBD 3.0 Desktop, and reload the page once more, now it has 
>> all the debug output.
>>
>> On Monday, April 8, 2013 8:43:46 PM UTC-5, Adam Cameron wrote: 
>>>
>>> I wonder if that's all you did?
>>>
>>> Having seen your question, I cranked up my shiny new, completely vanilla 
>>> OpenBD express install, went into the admin and switched debugging on:
>>> * Debugging & Logging menu
>>> * Debug Settings
>>> * Check enable debug output checkbox
>>> * Submit. The setting was saved
>>> * Check all the debug output options (Page execution, database activity, 
>>> etc).
>>> * Submit. The settings were saved
>>>
>>> I then browse to a page and see no debug output.
>>>
>>> I then restarted OpenBD complerely, rebrowse to the page: no debug 
>>> output.
>>>
>>> I then went to the Debug IP Addresses screen: there were no IP addresses 
>>> listed. This I would take to mean "all machines see debug output". However 
>>> I used "Add Local" to add my IP address (it adds 0:0:0:0:0:0:0:1), 
>>> restart everything, reload a page: still no debug output.
>>>
>>> Is there anything else I'm supposed to do?
>>>
>>> -- 
>>> Adam
>>>
>>>
>>>
>>>
>>> On Tuesday, 9 April 2013 13:33:06 UTC+12, marcel wrote: 
>>>>
>>>> Yeah finally got the output showing I needed to restart my tomcat 
>>>> instance. Weird I am sure i tried that before posting anyways showing now.
>>>>
>>>> For what it's worth debug output has been showing in all versions back 
>>>> to when the engine was still closed source from new atlanta. Also showing 
>>>> in this version. :)
>>>>
>>>> cheers
>>>>
>>>> marcel
>>>>
>>>  -- 
>> -- 
>> online documentation: http://openbd.org/manual/
>> http://groups.google.com/group/openbd?hl=en
>>  
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Open BlueDragon" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>>
>>  

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to