Menu
▾
▴
oreka-user — Users mailing list
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(7) |
Feb
(22) |
Mar
(11) |
Apr
(23) |
May
(13) |
Jun
(22) |
Jul
(8) |
Aug
|
Sep
(2) |
Oct
(8) |
Nov
(4) |
Dec
(2) |
| 2007 |
Jan
(16) |
Feb
(4) |
Mar
(6) |
Apr
(15) |
May
(10) |
Jun
(10) |
Jul
(43) |
Aug
(29) |
Sep
(15) |
Oct
(9) |
Nov
(6) |
Dec
(13) |
| 2008 |
Jan
(7) |
Feb
(7) |
Mar
(8) |
Apr
(26) |
May
(14) |
Jun
(12) |
Jul
|
Aug
(3) |
Sep
(6) |
Oct
(19) |
Nov
(12) |
Dec
(14) |
| 2009 |
Jan
(31) |
Feb
(25) |
Mar
(9) |
Apr
(7) |
May
(7) |
Jun
(15) |
Jul
(23) |
Aug
(20) |
Sep
(17) |
Oct
(14) |
Nov
(31) |
Dec
(15) |
| 2010 |
Jan
(38) |
Feb
(58) |
Mar
(42) |
Apr
(30) |
May
(22) |
Jun
(19) |
Jul
(12) |
Aug
(16) |
Sep
(25) |
Oct
(15) |
Nov
(28) |
Dec
(8) |
| 2011 |
Jan
(8) |
Feb
(18) |
Mar
(15) |
Apr
(13) |
May
(9) |
Jun
(18) |
Jul
(10) |
Aug
(23) |
Sep
(8) |
Oct
(8) |
Nov
(19) |
Dec
(1) |
| 2012 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
(10) |
May
(1) |
Jun
(1) |
Jul
(4) |
Aug
(4) |
Sep
(7) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2013 |
Jan
(3) |
Feb
(1) |
Mar
(6) |
Apr
(1) |
May
(8) |
Jun
(13) |
Jul
(10) |
Aug
(7) |
Sep
(28) |
Oct
(22) |
Nov
(40) |
Dec
(19) |
| 2014 |
Jan
(19) |
Feb
(22) |
Mar
(12) |
Apr
(11) |
May
(6) |
Jun
(11) |
Jul
(8) |
Aug
(2) |
Sep
(10) |
Oct
(25) |
Nov
(9) |
Dec
(13) |
| 2015 |
Jan
(28) |
Feb
(8) |
Mar
(6) |
Apr
(9) |
May
|
Jun
(1) |
Jul
(3) |
Aug
(2) |
Sep
(4) |
Oct
(2) |
Nov
(4) |
Dec
(3) |
| 2016 |
Jan
(10) |
Feb
(5) |
Mar
(10) |
Apr
(6) |
May
(7) |
Jun
(7) |
Jul
(6) |
Aug
(14) |
Sep
(2) |
Oct
(6) |
Nov
(7) |
Dec
(3) |
| 2017 |
Jan
(4) |
Feb
(2) |
Mar
(6) |
Apr
(4) |
May
(1) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
(5) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
(4) |
Feb
(1) |
Mar
(10) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2019 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(5) |
Jun
(3) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(1) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
1
|
2
|
3
|
4
|
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
|
12
|
13
|
14
|
15
|
16
|
17
(2) |
18
|
|
19
(1) |
20
|
21
(4) |
22
|
23
|
24
|
25
|
|
26
|
27
|
28
|
29
|
30
(2) |
31
(2) |
|
|
From: Henri H. <he...@or...> - 2006-03-31 16:17:33
|
Hi Sergey,
If you can post an ethereal pcap trace of at least one entire call where
metadata is not detected, I can have a look at it.
For your second problem, not sure what you mean. A pcap trace would also be
welcome.
Cheers
Henri
-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Sergey
Sent: 31 March 2006 09:33
To: he...@or...
Cc: ore...@li...
Subject: [Oreka-user] sessions & direction
Good afternoon, Henri!
There's a mistake once again: Oreka can't define the direction od the
call/ring, oinspite ao the fact, that MediaGateways is already registered.
2006-03-31 17:33:57,984 INFO tapelist:204 - date=2006-03-31_17-33-28
duration=29 direction=unkn capturePort=192.168.204.1,2000
^^^^^^^^^^^^^^
localParty=192.168.204.1 remoteParty=192.168.204.10 localEntryPoint=
Moreover, there is some strange thing in the program itself:
If direct some RTR or Cisco Skinny sessions (5-6) on the SPAN port, the
record is effected by segments, with the unspecified length, it's difficult
to hear them, whereas while recording the first session, there weren't any
problems.
Is this the problem of the hardware (NIC) or some restrictions of the
program?
Thanks in advance.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Oreka-user mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-user
|
|
From: Sergey <ze...@ma...> - 2006-03-31 14:32:47
|
Good afternoon, Henri!
There's a mistake once again: Oreka can't define the direction od the
call/ring, oinspite ao the fact, that MediaGateways is already registered.
2006-03-31 17:33:57,984 INFO tapelist:204 - date=2006-03-31_17-33-28
duration=29 direction=unkn capturePort=192.168.204.1,2000
^^^^^^^^^^^^^^
localParty=192.168.204.1 remoteParty=192.168.204.10 localEntryPoint=
Moreover, there is some strange thing in the program itself:
If direct some RTR or Cisco Skinny sessions (5-6) on the SPAN port, the
record is effected by segments, with the unspecified length, it's difficult
to hear them, whereas while recording the first session, there weren't any
problems.
Is this the problem of the hardware (NIC) or some restrictions of the
program?
Thanks in advance.
|
|
From: Henri H. <he...@or...> - 2006-03-30 14:11:57
|
Hi Sergey, Are you sure you are using the very latest installer from sourceforge (orkaudio-0.5-2-win32-installer.zip) ? I think this was a problem in orkaudio-0.5-1-win32-installer.zip. Cheers Henri -----Original Message----- From: ore...@li... [mailto:ore...@li...] On Behalf Of Sergey Sent: 30 March 2006 06:25 To: ore...@li... Subject: [Oreka-user] ERROR batchProcessing:164 - Could not instanciate = RTP mixer I've downloaded oreka on the address http://oreka.sourceforge.net/download/windows .=9A Oreka is installed on the system of Windows XP SP2 with 2 network = adaptors (Intel DC21143 =C9 Intel PRO/100 VE). =9AIntel PRO/100VE is plugged in = through the switch of the phone cisco 7940 to switch Cisco 3560, SPAN port is switched on in settings 3560, to the port of which the network adaptor = Intel DC21143 is linked.=20 There is a mistake In oreka logs:=20 ERROR batchProcessing:164 - BatchProcessing: BatchProcessing - Could not instanciate RTP mixer But anyway there are still some files in AudioRecordings. 20060330_120418_192.168.204.1,2000.mcf.orig=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A= =9A=9A ~1.2Mb 20060330_120418_192.168.204.1,2000.wav=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A 56bytes Configuration in the file: config.xml,(192.168.204.1 - ip CME 3.3, 192.168.204.10 - ip Cisco 7940) The "wav" file doesn't work, that's why it's necessary to write in (indicate) in config.xml, in order to have Oreka work in the right way.=20 P.S. WinPcap 3.1 has been already installed. Thanks in advance.=20 |
|
From: Sergey <ze...@ma...> - 2006-03-30 11:25:13
|
I've downloaded oreka on the address http://oreka.sourceforge.net/download/windows .=9A Oreka is installed on the system of Windows XP SP2 with 2 network = adaptors (Intel DC21143 =C9 Intel PRO/100 VE). =9AIntel PRO/100VE is plugged in = through the switch of the phone cisco 7940 to switch Cisco 3560, SPAN port is switched on in settings 3560, to the port of which the network adaptor = Intel DC21143 is linked.=20 There is a mistake In oreka logs:=20 ERROR batchProcessing:164 - BatchProcessing: BatchProcessing - Could not instanciate RTP mixer But anyway there are still some files in AudioRecordings. 20060330_120418_192.168.204.1,2000.mcf.orig=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A= =9A=9A ~1.2Mb=20 20060330_120418_192.168.204.1,2000.wav=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A=9A= =9A=9A=9A=9A=9A 56bytes Configuration in the file: config.xml,(192.168.204.1 - ip CME 3.3, 192.168.204.10 - ip Cisco 7940) The "wav" file doesn't work, that's why it's necessary to write in (indicate) in config.xml, in order to have Oreka work in the right way.=20 P.S. WinPcap 3.1 has been already installed. Thanks in advance.=20 |
|
From: Tassone, D. <ta...@im...> - 2006-03-21 16:40:28
|
Has anyone compared performance on a linux box verses 2003 server? Curious how Oreka performs in one environment verses the other. =20 =20 David Tassone Imperial Supplies LLC VP, Information Systems Voice: 920-497-5428 Fax: 920-491-3270 <mailto:ta...@im... <mailto:ta...@im...> > =20 |
|
From: Henri H. <he...@or...> - 2006-03-21 16:34:50
|
Hi Henry, Yes, you will be able to capture all voice activity into wav files. The only thing you will miss is metadata such as local party and remote party. If you configure your the following values correctly in config.xml, you should get the call direction right. <VoIpPlugin> <!-- LanMasks can be ignored if you have standard LAN addresses (192.168.255.255 or 10.255.255.255) --> <!-- LanMasks might be used to determine the direction of a call (incoming or outgoing into or from the LAN) --> <LanMasks>11.4.3.255, 12.2.3.255</LanMasks> <!-- The following is a csv list of your PBX, PSTN gateway, conferencing server or such RTP "gateway" devices --> <!-- It is needed to properly detect call direction --> <MediaGateways>10.10.10.129, 10.10.10.130</MediaGateways> <VoIpPlugin> Cheers Henri _____ From: ore...@li... [mailto:ore...@li...] On Behalf Of Henry SCHMITT Sent: 21 March 2006 04:20 To: ore...@li... Subject: [Oreka-user] oreka on HiPath4000 Hi all, we plan to test oreka on HiPath4000 version 3.0. We have several OptiPoint 4x0 (SIP and HFA [HFA is a propietary protocol based on H.323 with addons]). On a previous mail Henri Herscher wrote: *I do not expect any particular problems with other PBXs as RTP as a standard has nothing complicated about it.* So, is it possible to use oreka on HiPath4000 for HFA, as HFA use RTP too? Or is oreka only able to monitor SIP calls? thx in advance... henry. |
|
From: Henry S. <hen...@gm...> - 2006-03-21 16:26:41
|
Hello Henri, thx for the feedback. I will test oreka on HiPath4000 an give an input back to the list. henry On 3/21/06, Henri Herscher <he...@or...> wrote: > > Hi Henry, > > Yes, you will be able to capture all voice activity into wav files. The > only thing you will miss is metadata such as local party and remote party= . > If you configure your the following values correctly in config.xml, you > should get the call direction right. > > <VoIpPlugin> > <!-- LanMasks can be ignored if you have standard LAN addresses (192.16= 8.255.255or > 10.255.255.255) --> > <!-- LanMasks might be used to determine the direction of a call > (incoming or outgoing into or from the LAN) --> > <LanMasks>11.4.3.255, 12.2.3.255</LanMasks> > > <!-- The following is a csv list of your PBX, PSTN gateway, conferencin= g > server or such RTP "gateway" devices --> > <!-- It is needed to properly detect call direction --> > <MediaGateways> 10.10.10.129, 10.10.10.130</MediaGateways> > <VoIpPlugin> > > Cheers > Henri > > ------------------------------ > *From:* ore...@li... [mailto: > ore...@li...] *On Behalf Of *Henry SCHMITT > *Sent:* 21 March 2006 04:20 > *To:* ore...@li... > *Subject:* [Oreka-user] oreka on HiPath4000 > > > > Hi all, > > we plan to test oreka on HiPath4000 version 3.0. We have several OptiPoin= t > 4x0 (SIP and HFA [HFA is a propietary protocol based on H.323 with > addons]). On a previous mail Henri Herscher wrote: > > *I do not expect any particular problems with other PBXs as RTP as a > standard has nothing complicated about it.* > > So, is it possible to use oreka on HiPath4000 for HFA, as HFA use RTP too= ? > Or is oreka only able to monitor SIP calls? > > thx in advance... > > henry. > > |
|
From: Henry S. <hen...@gm...> - 2006-03-21 09:20:12
|
Hi all, we plan to test oreka on HiPath4000 version 3.0. We have several OptiPoint 4x0 (SIP and HFA [HFA is a propietary protocol based on H.323 with addons])= . On a previous mail Henri Herscher wrote: *I do not expect any particular problems with other PBXs as RTP as a standard has nothing complicated about it.* So, is it possible to use oreka on HiPath4000 for HFA, as HFA use RTP too? Or is oreka only able to monitor SIP calls? thx in advance... henry. |
|
From: Henri H. <he...@or...> - 2006-03-19 05:52:06
|
Hi David, mcf files not converted to wav could be due to several things: 1. You haven't waited for long enough and the backlog of mcf files to process is long behind the realtime capture. It'll eventually get there when traffic quiets down. 2. There is another queue overflow in the batchProcessing thread, this manifests itself by log entries like the following: ERROR batchProcessing:45 - BatchProcessing: queue full This means that file encoding to the final storage format (such as gsm) lags behind the real time capture (this is not a problem itself) so much that the queue of mcf files to process has overflown. The default value of this queue in CVS head has now been increased to 20,000 files. It is also possible to configure this maximum queue size using the <BatchProcessingQueueSize> XML tag in config.xml. The next official version of Oreka will include this patch. 2. There is any other kind of error during the batch processing which means that oreka interrupts the ulaw -> linear -> gsm process (this is an example) before it is finished. I have yet to see this but it could happen. In this scenario, you should have a small wav file next to your mcf file. You shoud also have a log error such as this: ERROR batchProcessing Please let us know your findings. Cheers Henri _____ From: Tassone, David [mailto:ta...@im...] Sent: 17 March 2006 17:51 To: Henri Herscher Subject: RE: [Oreka-user] Orkaudio.log error - Why/what does it mean? Makes sense since the server is not the highest end. If I see lingering MCF files that never get converted to WAV files, what would cause this? _____ From: Henri Herscher [mailto:he...@or...] Sent: Friday, March 17, 2006 4:28 PM To: Tassone, David; ore...@li... Subject: RE: [Oreka-user] Orkaudio.log error - Why/what does it mean? Hi David, It essentially means that the captured audio is not written to the hard drive as fast as it is received and you are loosing bits of audio here and there which might affect the audio quality of the recordings. This can happen under heavy loads. There are two ways of getting around this: * Have a server with better specs (in particular, a fast hard drive) * Increase the queue size - I am in the process of making the default queue size bigger and also to make it configurable, this will be part of the next release of Oreka Cheers Henri _____ From: ore...@li... [mailto:ore...@li...] On Behalf Of Tassone, David Sent: 17 March 2006 16:52 To: ore...@li... Subject: [Oreka-user] Orkaudio.log error - Why/what does it mean? Orkaudio.log error - Why/what does it mean? 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full David Tassone Imperial Supplies LLC |
|
From: Henri H. <he...@or...> - 2006-03-17 22:28:39
|
Hi David, It essentially means that the captured audio is not written to the hard drive as fast as it is received and you are loosing bits of audio here and there which might affect the audio quality of the recordings. This can happen under heavy loads. There are two ways of getting around this: * Have a server with better specs (in particular, a fast hard drive) * Increase the queue size - I am in the process of making the default queue size bigger and also to make it configurable, this will be part of the next release of Oreka Cheers Henri _____ From: ore...@li... [mailto:ore...@li...] On Behalf Of Tassone, David Sent: 17 March 2006 16:52 To: ore...@li... Subject: [Oreka-user] Orkaudio.log error - Why/what does it mean? Orkaudio.log error - Why/what does it mean? 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full David Tassone Imperial Supplies LLC |
|
From: Tassone, D. <ta...@im...> - 2006-03-17 21:52:06
|
Orkaudio.log error - Why/what does it mean? =20 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full 2006-03-17 15:41:39,015 ERROR immediateProcessing:33 - ImmediateProcessing: queue full =20 David Tassone Imperial Supplies LLC =20 |