Hello Chuck,
Attached a sample script we use to start our apps.
We store our logs in a file at location as specified this script. But
unfortunately, some times I feel/ see that some of the logs[again
unfortunately these unwritten logs turn out be Exception/Error logs] are
not written in to these log files for some unknown reason. Any idea why
how to fix this?
I tried below command to capture thread dump:
$ kill -3 <PID> >threaddump.txt
but I see nothing in this file. Is this the right way of capturing thread
dumps? Please advise.
Thank You
Shravan
------------------------
On Wed, April 23, 2008 5:56 am, Chuck Hill wrote:
>
> On Apr 22, 2008, at 5:13 PM, [EMAIL PROTECTED] wrote:
>
>> Hello Chuck,
>>
>> We start our apps through scripts. We do not use Java Monitor/wotaskd.
>>
>> So, I did not work on editing SpawnOfWotaskd.sh
>>
>> Please advise if this needs to be done and it makes sense for us.
>
> Dude. You wrote the scripts. They are sending the stack trace
> _somewhere_. Read your scripts.
>
> Chuck
>
>
>
>> On Wed, April 23, 2008 12:52 am, Chuck Hill wrote:
>>>
>>> On Apr 22, 2008, at 11:43 AM, [EMAIL PROTECTED] wrote:
>>>
>>>> Hello Chuck,
>>>>
>>>> Thanks for your reply Chuck.
>>>>
>>>> I have went through the link you have provided some time back and
>>>> tried
>>>> kill -3, but it is not outputting any ino, command is just quitting
>>>> quietly.
>>>
>>> Did you follow all of the stuff on that page? Editing
>>> SpawnOfWotaskd.sh?
>>>
>>>
>>>> Can you advise what sort of things I need to check in my app, which
>>>> may
>>>> cause these issues, such that we can have a resolution asap. I mean
>>>> any
>>>> code blocks/ design/ ?
>>>
>>> Generally throwing exceptions from awake(), sleep(), and terminate()
>>> or mishandling editing context locking are common problems. There
>>> should be some deadlock information in the wiki.
>>>
>>>
>>> Chuck
>>>
>>>
>>>
>>>> On Tue, April 22, 2008 11:56 pm, Chuck Hill wrote:
>>>>>
>>>>> On Apr 22, 2008, at 11:13 AM, [EMAIL PROTECTED] wrote:
>>>>>
>>>>>> Hello Aurelien,
>>>>>>
>>>>>> Yep, we upgraded to 5.2.1 - 5.2.2 - 5.2.3 - 5.2.4.
>>>>>>
>>>>>> We do sometimes see broken pipe exception in our logs, I heard
>>>>>> that
>>>>>> this
>>>>>> generally happens when the connection between woadptor and browser
>>>>>> is idle
>>>>>> for certain amount of time, whcih generally means the connection
>>>>>> between
>>>>>> woadaptor and browser is broken. Am I right?
>>>>>>
>>>>>> How can we find dead locks in our application?
>>>>>
>>>>> http://www.gvcsitemaker.com/gvc.webobjects/faq&mode=single&recordID=41413
>>>>>
>>>>>
>>>>>> Please advise a solution as to how to determine which part of the
>>>>>> application is causing this problem.
>>>>>
>>>>> You need to analyze the thread dumps, then look in your code to
>>>>> see
>>>>> what could be causing that. It can be difficult.
>>>>>
>>>>> Chuck
>>>>>
>>>>>
>>>>>
>>>>>> ----------------------------
>>>>>> On Tue, April 22, 2008 9:11 pm, Aurélien Minet wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>> We have been battered by CLOSE_WAIT processes and instances
>>>>>>>> hang.
>>>>>>>>
>>>>>>>> We are running our application on Solaris 5.8 boxes with
>>>>>>>> WebObjects
>>>>>>>> 5.2.4, Java 1.4.2_17.
>>>>>>> The 5.2 updates are "cumulative", do you apply 5.2.3 update ?
>>>>>>> (and
>>>>>>> 5.2.1
>>>>>>> 5.2.2)
>>>>>>> it fix a bug about close_wait (
>>>>>>> http://docs.info.apple.com/article.html?artnum=107873 )
>>>>>>>>
>>>>>>>> We have collected some process dumps and consulted Sun, they
>>>>>>>> analyzed
>>>>>>>> and blame our code, alas!!!
>>>>>>>>
>>>>>>>> We see CLOSE_WAIT state of a process for both java and httpd
>>>>>>>> processes.
>>>>>>> Is the java process is your app or the wotaskd ?
>>>>>>> If it is your app, is it the only application that has the
>>>>>>> problem ?
>>>>>>>> We see degradation in our application performance as the day
>>>>>>>> progresses and our app becomes unresponsive various times, we
>>>>>>>> restart
>>>>>>>> the app various times during day.
>>>>>>> Don't you have java exception: broken pipe in your application
>>>>>>> logs ?
>>>>>>>>
>>>>>>>> Could any one please advise us a solution to find the reason for
>>>>>>>> instance hang or fix CLOSE_WAIT processes generation.
>>>>>>> You may also look for deadlocks in your apps.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Aurelien
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thank You
>>>>>> Shravan Kumar. M
>>>>>> effigent India Pvt Ltd.,
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-deploy mailing list (Webobjects-
>>>>>> [EMAIL PROTECTED])
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>> http://lists.apple.com/mailman/options/webobjects-deploy/chill%40global-village.net
>>>>>>
>>>>>> This email sent to [EMAIL PROTECTED]
>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thank You
>>>> Shravan Kumar. M
>>>> effigent India Pvt Ltd.,
>>>>
>>>>
>>>
>>> --
>>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Thank You
>> Shravan Kumar. M
>> effigent India Pvt Ltd.,
>>
>>
>
> --
>
> 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
>
>
>
>
>
>
>
#!/bin/sh
PATH=/usr/local/bin:$NEXT_ROOT/Developer/Executables:$PATH:/usr/ccs/bin:/usr/bin:/usr/local/bin;export
PATH
PATH=/usr/local/bin:/usr/j2sdk1.4.2_17/bin:$NEXT_ROOT/Developer/Executables:$PATH:/usr/ccs/bin:/usr/bin:/usr/local/bin:$ORACLE_HOME/bin;export
PATH
PATH=$PATH:/opt/Apple/Library/Java;export PATH
LD_LIBRARY_PATH=/usr/lib/lwp:$NEXT_ROOT/Library/Executables:$NEXT_ROOT/Local/Library/Executables
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/j2sdk1.4.2_17/lib
export LD_LIBRARY_PATH
#MAIN PARAMETERS
LOG_DIR=" /opt/Apple/Local/Library/WebObjects/Applications/effigentcode/log"
APP_DIR=" /opt/Apple/Local/Library/WebObjects/Applications"
#Function to Launch it
fireApps() {
for i in `echo $PORT_RANGE`
do
echo starting $i
nohup $APP -WOPort $i $PARAMETERS -WOOutputPath $LOG_DIR | tee
$LOG_DIR/$LOG_FILE_NAME.$i.log &
done
}
fireJuicyADMIN() {
echo LAUNCHING Juicy ADMIN
# Following lines of script will create manageable log structure.
# Every day a folder with date format %m.%d.%G is created in the LOG_DIR
folder. This date folder again has different folders, one for each application.
# for eg: we want to find logs for Juicyadmin application on 17th April 2007,
then we need to cd to LOG_DIR and then cd 04.17.2007/Juicyadmin/ , here we have
logs for all the instances of the Juicyadmin application for the requested date.
LOG_FILE_NAME_PREFIX="Juicyadmin"
LOG_FILE_NAME=`date "+$LOG_FILE_NAME_PREFIX%m.%d.%G_%H:%M:%S_%Z"`
OLD_DIR=`pwd`
cd $LOG_DIR
APP_SPECIFIC_DIR=`date "+%m.%d.%G"`_log/$LOG_FILE_NAME_PREFIX
mkdir -p $APP_SPECIFIC_DIR
cd $APP_SPECIFIC_DIR
NEW_LOG_DIR=`pwd`
LOG_DIR=$NEW_LOG_DIR
cd $OLD_DIR
APP="$APP_DIR/Juicy.woa/Juicy"
PARAMETERS="-Config JuicyPAdmin -IsReportMillLicenseInstalled true -Xms64m
-Xmx512m -WOSMTPHost 192.168.1.10"
PORT_RANGE="8001 8002 8003 8004 8005 8006 8007 8008 8009 8010"
fireApps
PORT_RANGE="8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023
8024 8025 8026 8027 8028 8029 8030"
fireApps
PORT_RANGE="8031 8032 8033 8034 8035 8036 8037 8038 8039 8040"
fireApps
}
fireJuicyADMIN
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]