Re: Barracuda 1.2.0 released

Jacob Kjome <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
Ahhh....ok,

I figured out where trace.log is being written on my system.  When I start 
Tomcat using the startup scripts in CATALINA_HOME/bin, that is where the 
trace.log gets written.  When I start it via an NT Service, it gets written 
to C:\WINNT\system32.  So, it is basically writing it to wherever the 
Tomcat process was started.  I assume that you are calling the startup 
scripts in Tomcat, so it would be in CATALINA_HOME/bin on barracudamvc.org.

Now, the problem with making the path "/tmp/trace.log" is that the error we 
were seeing on Linux, but is now fixed will now occur on Windows because it 
won't be able to resolve the UNIX path.  The solution to this is to fix the 
CATALINA_HOME/bin directory to allow for writing the trace.log and changing 
the path back to "./trace.log".  This will make things work on both Linux 
and Windows alike.

The other error should be solved by shutting down the server, doing a clean 
rebuild, and then starting things back up again.  That path should be 
replaced by the <copyrepl> taskdef with the proper event name.

If you can do the above, that would be great!  I will be away from the 
computer for a little while, so I won't be able to respond until later.

thanks Shawn!

Jake

At 11:11 AM 5/23/2003 -0600, you wrote:
>The problem has now been fixed!
>
>I have no idea where "./trace.log" was trying to be created but it was 
>apparently nowhere within the BarracudaDiscRack folder. Instead I modified 
>discRack.prp so that it uses the absolute path "/tmp/trace.log". That 
>solved the trace.log permissions issue. I then made the tomcat4 user owner 
>of the idb folder and all subfolders and that apparently fixed all the 
>permission issues so it seems to work now.
>
>So the only other minor glitch I noticed while testing the application is 
>that after getting the exception page (by clicking the "Test Throwing an 
>Exception" button) the link back to the login page does not work.
>
>-shawn
>
>Jacob Kjome wrote:
>>Ok. That would be good if you could do that.
>>BTW, where is the trace.log being written?  I don't see it anywhere on my 
>>system (win2k).
>>Jake
>>At 10:29 AM 5/23/2003 -0600, you wrote:
>>
>>>What I did was I made everything in the BarracudaDiscRack folder on down 
>>>world-writable (chmod -R o+w *) and cycled the app but that made no 
>>>difference. I even tried manually creating the trace.log file in various 
>>>locations with full permissions but that also did not help.
>>>
>>>After about an hour of trying different things I gave up and restored 
>>>the directory to its original permissions (which is why you don't see 
>>>any differences Jake). I can go ahead and set it all world-writable 
>>>again if one of you think you want to play around with this.
>>>
>>>-shawn
>>>
>>>Jacob Kjome wrote:
>>>
>>>>Hi Tim,
>>>>Good to see you back on the list :-)
>>>>I already considered the permissions issue.  I had asked Shawn to 
>>>>change the permissions because I don't have the proper privileges.
>>>>He claimed to have changed things and it still didn't work, but as I 
>>>>look at it now, it is no different than when I looked at it before.
>>>>So, it very well may still be a permissions issue.  I just re-sent a 
>>>>message to Shawn and Denny to see if they can try modifying the 
>>>>permissions again.
>>>>later,
>>>>Jake
>>>>At 07:55 PM 5/22/2003 -0700, you wrote:
>>>>
>>>>>Most likely this is because the db depends on being able to 
>>>>>write/rewrite a
>>>>>file to the file system.  Most likely you are deploying the DiscRack 
>>>>>as a WAR
>>>>>under some app server somewhere and the db is configured to write it's
>>>>>database files somewhere where the OS doesn't like.  Under Win2K you 
>>>>>are not
>>>>>seeing this because you are most likely admin on that box, thus disabling
>>>>>security.
>>>>>
>>>>>-Tim
>>>>>
>>>>>On Thursday 22 May 2003 02:01 pm, Jacob Kjome wrote:
>>>>> > Just wanted to send a message out to Barracuda users that Barracuda 
>>>>> 1.2.0
>>>>> > has been released and can be downloaded here:
>>>>> > http://barracudamvc.org/downloads/
>>>>> >
>>>>> > BarracudaDiscRack 1.2.0 was also released.  However, for some 
>>>>> reason, the
>>>>> > database doesn't seem to be working properly at barracudamvc.org. 
>>>>> It works
>>>>> > fine here at home.  I'm not sure if this is a Linux -vs- Win2k
>>>>> > compatibility issue or what?  It certainly works great on Win2k.
>>>>> >
>>>>> > These releases contain tons of changes and additions, so try them 
>>>>> out.  I
>>>>> > will send out another more official release announcement once we 
>>>>> figure out
>>>>> > the BaracudaDiscRack issue on barracudamvc.org.  This will go out 
>>>>> to more
>>>>> > lists, but I wanted you all to know that the 1.2.0 now exists and 
>>>>> is ready
>>>>> > to use....finally!!!
>>>>> >
>>>>> > Jake
>>>>> >
>>>>> > _______________________________________________
>>>>> > Barracuda mailing list
>>>>> > [email protected]
>>>>> > http://barracudamvc.org/lists/listinfo/barracuda
>>>>>
>>>>>_______________________________________________
>>>>>Barracuda mailing list
>>>>>[email protected]
>>>>>http://barracudamvc.org/lists/listinfo/barracuda
>>>
>>>
>>>_______________________________________________
>>>Barracuda mailing list
>>>[email protected]
>>>http://barracudamvc.org/lists/listinfo/barracuda
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.