[Wrm-dqd] Checking log files in production

[Bergenroth, Brandon]

I made a change yesterday and deployed to 51, I will check the logs and if it
looks good redeploy to 229 later this week.  

Thanks,
Brandon
 

> -----Original Message-----
> From: Li, Charles 
> Sent: Wednesday, February 22, 2006 8:05 AM
> To: Bergenroth, Brandon; Arbogast, Rene
> Cc: 'wrm-dqd at lists.dep.state.fl.us'; Fuller, Andrew; Lepley, Spencer
> Subject: RE: [Wrm-dqd] Checking log files in production
> 
> Brandon,
> Andrew Fuller with the ArmPars project had a similar 
> connection error.  I am forwarding his email, in hope that it 
> can help you track down your problem.
> 
> Thanks,
> Charles Li
>  
> 
> 
>  -----Original Message-----
> From: 	Bergenroth, Brandon  
> Sent:	Tuesday, February 21, 2006 2:30 PM
> To:	Li, Charles; Arbogast, Rene
> Cc:	'wrm-dqd at lists.dep.state.fl.us'
> Subject:	RE: [Wrm-dqd] Checking log files in production
> 
> I'm looking into it, trying to reproduce it on epic51.  
> Thanks for bringing it to my attention, I hadn't even noticed 
> the opmn log.
> 
> 
> 
> > -----Original Message-----
> > From: Li, Charles 
> > Sent: Tuesday, February 21, 2006 1:32 PM
> > To: Bergenroth, Brandon; Arbogast, Rene
> > Cc: 'wrm-dqd at lists.dep.state.fl.us'
> > Subject: RE: [Wrm-dqd] Checking log files in production
> > 
> > All the information is in the Dwrm OPMN log, which you can 
> > access with this URL: 
> > http://epic229.dep.state.fl.us:7000/app-logs/Log4JLogs/Dwrm_opmn.log
> > 
> >  -----Original Message-----
> > From: 	Bergenroth, Brandon  
> > Sent:	Tuesday, February 21, 2006 1:30 PM
> > To:	Li, Charles; Arbogast, Rene
> > Cc:	wrm-dqd at lists.dep.state.fl.us
> > Subject:	RE: [Wrm-dqd] Checking log files in production
> > 
> > Charles,
> > 
> > I don't see how this could have happened.  In the log4j log, 
> > http://epic229.dep.state.fl.us:7000/app-logs/Log4JLogs/WrmDqd.
> > log I see the same number of calls to open a connection as 
> > there are to close.  We didn't get that error in any testing. 
> >  Is there any more info in the opmn log file that might give a clue?
> > 
> > Thanks,
> > Brandon
> > 
> > 
> > > -----Original Message-----
> > > From: wrm-dqd-bounces at lists.dep.state.fl.us 
> > > [mailto:wrm-dqd-bounces at lists.dep.state.fl.us] On Behalf Of 
> > > Li, Charles
> > > Sent: Tuesday, February 21, 2006 11:35 AM
> > > To: Arbogast, Rene
> > > Cc: wrm-dqd at lists.dep.state.fl.us
> > > Subject: [Wrm-dqd] Checking log files in production
> > > 
> > > Rene,
> > > Is your team still monitor the production log files regularly?
> > > 
> > > I saw a connection pool error in the Dwrm opmn log for 
> > > yesterday.  Can some
> > > one from your team look into fixing it?
> > > 
> > > 
> > > ============================================
> > > 
> http://epic229.dep.state.fl.us:7000/app-logs/Log4JLogs/Dwrm_opmn.log
> > > 
> > > 06/02/20 14:55:45 DriverManagerConnectionPoolConnection not 
> > > closed, check
> > > your code!
> > > ============================================
> > > 
> > > Thanks,
> > > Charles Li
> > > _______________________________________________
> > > Wrm-dqd mailing list
> > > Wrm-dqd at lists.dep.state.fl.us
> > > http://lists.dep.state.fl.us/cgi-bin/mailman/listinfo/wrm-dqd
> > > 
> > 
>