Errors On Upstream????

Hey guys,
I am wondering if anyone else is having this issue. i have recently just moved to BT BB and excpet for a few wirless issue to start with i am very happy
But.............................. i seem to have an amazing amount of CRC's errors on my upstream. I have a friend who is also on Bt and he has the same. these errors are only on my upstream.
Now i have got a very good line which i am happy and i dont see to many issues with my upstream.... a few uploading issues but very rare.................
Now i work for a major ISP and if i saw this error pon someones line i would be worried I am wondering if the BT homehub is just lieing...
Also i am in the test socket and filters and cables have been swapped.
Any ideas would be great thanks
Here are stats of my line:
Downstream
8,128 Kbps
Upstream
448 Kbps
Latency type
Fast
Noise margin (Down/Up)
9.7 dB / 22.0 dB
Line attenuation (Down/Up)
24.0 dB / 13.5 dB
Output power (Down/Up)
19.8 dBm / 11.9 dBm
FEC Errors (Down/Up)
0 / 0
CRC Errors (Down/Up)
447 / 2147480000
HEC Errors (Down/Up)
nil / 0
Error Seconds (Local)
322

ahhh thanks mate. i was wondering if it was an issue with the firmware so thats fine mate i will leave it as it is
I would love 17mb mate but i dont think i'll get that but i am happy with 8mb.
I might get them to try ADSL2PLus and just see what it comes up as
Thanks for all your help guys!

Similar Messages

  • Five months of ongoing timeouts and connection loss

    SE PA area. Problem started back in January with bursts of high ping times and timeouts on an old white Westell model with a WRT54g bridged to handle the routing. After several support calls a new Westell 6100 was sent but failed to resolve the intermittent problem. It seems to be aggravated by wet weather but also happens during dry periods just not as frequently. Around March tech support sent another Westell 6100 claiming the first one went bad. Problems continued intermittently as they've always been.
    After a couple more calls to tech support they claimed the second Westell 6100 might be causing the problem and sent an Actiontec GT704WGB. Before getting the Actiontec installed our phone quit working (clicking noise and cross talk) but DSL continued to function with the same high pings and time outs randomly. This was last week and we were finally able to get a phone tech last Thursday (still had the Westell 6100 hooked up) to come to the house. Several hours prior to his arrival our phone started working and talking to the tech he said there was a line problem found and fixed.
    While the tech was here, he put a splitter in line and ran a home run for the DSL to help us eliminate any possible filter issues and see if it would help with the intermittent DSL problems. I have also replaced the line from the NID inside with a new cat5e run. Yesterday (Friday) we had a bad rain storm lasting several hours (over 1.5in of rain) and the DSL has been garbage since.
    I broke down today and pulled the Westell 6100 and my Linksys WRT54g out of the DSL line and finally installed the Actiontec GT704WGB and it's as bad or worse than ever. I've collected as much info as I can to try to shed some light on this if someone know how to interpret what the results are and can help, that would be awesome. I'm at my wits end with Indias tech support route and after 5 months I don't know what else to do.
    Reverse traceroute during problem:
    I x'd out my IP on the last hops.
    06/2/2012 10pm
    news-europe.giganews.com
    1 vl201.gw2.ams.giganews.com (216.196.110.2) 0 ms 0 ms 0 ms
    2 208.174.49.145 (208.174.49.145) 0 ms 0 ms 0 ms
    3 cr2-tengig-0-5-1-0.frankfurtft3.savvis.net (204.70.207.209) 7 ms 9 ms 7 ms
    4 cr2-ten-0-8-0-0.NewYork.savvis.net (204.70.195.22) 88 ms 88 ms 88 ms
    5 er2-tengig-8-8.newyork.savvis.net (204.70.224.249) 87 ms 87 ms 87 ms
    6 0.xe-9-2-0.BR2.NYC4.ALTER.NET (204.255.168.89) 94 ms 94 ms 94 ms
    7 0.ae2.NY5030-BB-RTR2.verizon-gni.NET (152.63.18.74) 110 ms 96 ms 88 ms
    8 ge-7-1-0-0.PHIL-CORE-RTR2.verizon-gni.net (130.81.20.139) 88 ms 88 ms 88 ms
    9 A4-0-0-1723.PHIL-DSL-RTR7.verizon-gni.net (130.81.11.234) 88 ms 88 ms 88 ms
    10 pool-xx-xx-xxx-xxx.phil.east.verizon.net (xx.xx.xx.xxx) 1736 ms 1714 ms 1593 ms
    06/2/2012 10:03pm
    news.giganews.com
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 2 ms 0 ms 0 ms
    2 g3-0.bb1.dca.giganews.com (216.196.96.62) 25 ms 54 ms 0 ms
    3 xe-8-0-7.ar2.iad1.us.nlayer.net (69.31.10.97) 4 ms 1 ms 1 ms
    4 TenGigE0-1-0-0.GW7.IAD8.ALTER.NET (152.179.50.73) 5 ms TenGigE0-2-4-0.GW7.IAD8.ALTER.NET (152.179.50.93) 0 ms TenGigE0-1-0-0.GW7.IAD8.ALTER.NET (152.179.50.73) 0 ms
    5 0.xe-0-1-0.XL4.IAD8.ALTER.NET (152.63.37.93) 0 ms 0 ms 0 ms
    6 0.ge-11-0-0.RES-BB-RTR2.verizon-gni.net (152.63.30.10) 0 ms 0.so-9-3-0.RES-BB-RTR2.verizon-gni.net (152.63.37.122) 0 ms 0.xe-15-1-0.RES-BB-RTR2.verizon-gni.NET (152.63.3.54) 0 ms
    7 ge-7-1-0-0.PHIL-CORE-RTR2.verizon-gni.net (130.81.20.139) 7 ms 6 ms 6 ms
    8 A4-0-0-1723.PHIL-DSL-RTR7.verizon-gni.net (130.81.11.234) 11 ms 9 ms 8 ms
    9 pool-70-16-xxx-xxx.phil.east.verizon.net (70.16.xxx.xxx) 1206 ms 1339 ms 1661 ms
    news-europe.giganews.com
    1 vl201.gw2.ams.giganews.com (216.196.110.2) 0 ms 0 ms 0 ms
    2 208.174.49.145 (208.174.49.145) 31 ms 0 ms 0 ms
    3 cr2-tengig-0-5-1-0.frankfurtft3.savvis.net (204.70.207.209) 7 ms 7 ms 6 ms
    4 cr2-ten-0-8-0-0.NewYork.savvis.net (204.70.195.22) 88 ms 88 ms 88 ms
    5 er2-tengig-8-8.newyork.savvis.net (204.70.224.249) 87 ms 87 ms 87 ms
    6 0.xe-9-2-0.BR2.NYC4.ALTER.NET (204.255.168.89) 94 ms 94 ms 94 ms
    7 0.ae2.NY5030-BB-RTR2.verizon-gni.NET (152.63.18.74) 105 ms 88 ms 88 ms
    8 ge-7-1-0-0.PHIL-CORE-RTR2.verizon-gni.net (130.81.20.139) 88 ms 90 ms 88 ms
    9 A4-0-0-1723.PHIL-DSL-RTR7.verizon-gni.net (130.81.11.234) 88 ms 88 ms 88 ms
    10 * * *
    11 * * pool-70-16-xxx-xxx.phil.east.verizon.net (70.16.xxx.xxx) 1802 ms
    Snippets of ping times to yahoo:
    Reply from 98.139.183.24: bytes=32 time=55ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=55ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=72ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=76ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=66ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=52ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=94ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=137ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=40ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=420ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=973ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=1410ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=1995ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=3076ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=2058ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=114ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=54ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=55ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=43ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=68ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=141ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=69ms TTL=49
    Reply from 98.139.183.24: bytes=32 time=52ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=56ms TTL=50
    Reply from 98.139.183.24: bytes=32 time=309ms TTL=50
    TRANSCEIVER STATS:
    Inside house (10pm 06/2/2012) around the time of the above traceroutes and ping snips.
    DSL Status
    VPI: 0    
    VCI: 35    
    DSL Mode Setting: Auto    
    DSL Negotiated Mode: G.DMT    
    Connection Status: ShowTime    
    Speed (down/up): 1792/448    
    ATM QoS class:     UBR
    Output Power (Downstream/Upstream): 11.9/17.3 dBm    
    Attainable Rate (Downstream/Upstream): 8352/1064 Kbps    
    HEC Errors (Downstream/Upstream): 1/0    
    OCD Errors (Downstream/Upstream): 0/0    
    LCD Errors (Downstream/Upstream): 0/0    
    SNR Margin (Downstream/Upstream): 29.8/22.0 dB    
    Attenuation (Downstream/Upstream): 49.5/24.0 dB    
    At NID (tested a couple hours prior to inside test above)
    DSL Status
    VPI: 0    
    VCI: 35    
    DSL Mode Setting: Auto    
    DSL Negotiated Mode: G.DMT    
    Connection Status: ShowTime    
    Speed (down/up): 1792/448    
    ATM QoS class:     UBR
    Output Power (Downstream/Upstream): 11.9/16.8 dBm    
    Attainable Rate (Downstream/Upstream): 8160/1052 Kbps    
    HEC Errors (Downstream/Upstream): 1/0    
    OCD Errors (Downstream/Upstream): 0/0    
    LCD Errors (Downstream/Upstream): 0/0    
    SNR Margin (Downstream/Upstream): 29.8/22.0 dB    
    Attenuation (Downstream/Upstream): 49.5/24.0 dB    

    Ah.. I was hoping you'd stop by and chime in. Thanks!  I spent a couple of evenings browsing the forums looking at others' issues and was always impressed with not only your knowledge but your willingness and consistent help to many who post up with issues. I'm gonna have to give you a Kudos on this as it's the best I can do and people such as yourself and several of the other regular "assistees" I've seen help here are what really make these forums/communities the great resource that they are.
    As I have a technical background in electronics and electro-mechanical I was able to blow through a lot of good information on what to check and get all my potential infrastructure issues on my side covered before going any farther (replacing my old lines with new cat5 and new jacks, getting the tech to put a splitter in and run a home run for the DSL line). But I don't have much knowledge in the telecommunications end and DSL. Your info helped a lot with shedding some more light on that as well as reading other posts.
    I saw the Redback router in the reverser trace and had gathered from other reading that they're older units. I have no idea what if any upgrades will be done at my CO. I am in fact fed from a CO and that fits in with my attenuation numbers as I'm about 2 miles away. From the numbers I estimate between 12-13000 feet on the wire.
    A short update since Sunday. Yesterday my wife received a call from a US based tech from the Chronic Intermittency team (I think that's what she called them) and after looking at the line the nice lady was a bit perplexed as I was as the numbers look so good on the line. She was able to determine after several steps with my wife, that we might just be saturating the 1.7Mb we were provisioned at and the modem was just giving up the ghost and timing out eventually. She opened the pipe up to 3Mb and it's gotten MUCH better since yesterday. While it tightened us up quite a bit on the Margin (I was a little surprised at how much the Margin dropped with only doubling the rate) it appears 5Mbps would easily be doable barring no other line issues. What I was most favorably impressed with though was that the nice lady promised to call back and stay with this issue until resolved. She's off for a couple of days which will give us some time to see how much better this one change has improved things but she did call twice yesterday (a call back followup after the original call and bumping up the provisioning to see if she was on the right track). That certainly helped boost my confidence level with Verizon's support a bit...
    New transceiver stats 6/4/12 actual stats were taken 6/5 with 54hrs uptime.
    DSL Status
    VPI:    0
    VCI:    35
    DSL Mode Setting: Auto    
    DSL Negotiated Mode:    G.DMT
    Connection Status:    Showtime
    Speed (down/up):    3360/832
    ATM QoS class:     UBR
    Output Power (Downstream/Upstream):    11.9 / 11.6 dBm
    Attainable Rate (Downstream/Upstream):    8320 / 932 Kbps
    HEC Errors (Downstream/Upstream): 522 / 0    
    OCD Errors (Downstream/Upstream): 0 / 0    
    LCD Errors (Downstream/Upstream): 0 / 0    
    SNR Margin (Downstream/Upstream): 17.1 / 9.0    
    Attenuation (Downstream/Upstream): 49.5 / 24.0    
    I also found it interesting that the upstream output power dropped so much. It appears that modem was getting a workout at 400Kbps. Downstream held the same.
    I'm not ready to mark this resolved yet but it does appear the lady was correct in her assumption that we were saturating the connection as a primary root cause. Interesting...
    What I still find a bit of a puzzle is our online habits haven't changed (always run virus/trojan protection as that was one item the tech queried due to the activity she was seeing based on what my wife had running at the time) and yet this didn't crop up until the beginning of this year. We primarily run 2 desktop systems and I use a laptop wirelessly occasionally (yes, I did kill the wireless on the router for a day in troubleshooting). My usage is primarily browsing and email and my browsing is mostly forums and finance based so not a lot of high bandwidth usage there. The wife does have an online game she's played for years and does use Skype and Teamspeak during her gaming, but her gaming habits/use hasn't changed over the years either. I do run the Network Meter Gadget on Windows 7 on all PCs so we can monitor our rate dynamically but it's hard to aggregate that info when we're both online to see the total bandwidth we're pushing. I've watched her sessions as well as monitoring mine and she was by no means in constant saturation. I was surprised at the constant "chatter" Skype puts on the line even with no ongoing conversations. I suspect some congestion at the DSLAM might be in play here as well. We'll see how it all shakes out in the end. I'd certainly like to get the bump to 5Mbps if it's doable and think that might just buy us a bit more life until we finally have to cave to Fios.

  • Speed availabili​ty at my location

    Hoping someone can give some insight on how to fix this problem.
    I currently live less than 2500 feet from the central office and my availability is provisioned at up to 3.0 mbps. When the technician came out to my home to connect the wires, he said he was able to get 10 mbps on my line. As a side note, I used to be located over 9000 feet from this same central office and was receiving 7.0 mbps. I've contacted sales/tech support numerous times to try and get my speed cap increased, but I keep getting punted back and forth. Sales states they can't increase my speed because the cap is set to 3 mbps, and tech states they cannot increase my speed because I'm maxed out at what I am currently provisioned for. When the tech agents test my line, they've reported back speeds on my line of between 7-9 mbps each time. I've had a sales and tech agent on a conference call and still can't get a resolution.
    What else can I do to try and get my speed cap increased?

    Thanks for your help Smith6612! I got the same run around answer, so any hail mary attempt you can make is very much appreciated.
    If it helps, here is some info I pulled from my modem and traceroute. Not sure what to make of the traceroute.
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
    2 ash-bb1-link.telia.net (213.248.70.241) 11 ms 11 ms 10 ms
    3 ash-bb3-link.telia.net (80.91.248.160) 7 ms 0 ms 7 ms
    4 ash-b2-link.telia.net (213.155.133.189) 0 ms ash-b2-link.telia.net (80.91.252.93) 0 ms ash-b2-link.telia.net (213.155.133.183) 0 ms
    5 GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 0 ms TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 0 ms 4 ms
    6 so-1-0-0-0.SJC01-CORE-RTR1.verizon-gni.net (130.81.20.45) 81 ms 81 ms 81 ms
    VPI: 0
    VCI: 35    
    DSL Mode Setting: Auto    
    DSL Negotiated Mode: G.DMT    
    Connection Status: ShowTime
    Speed (down/up): 3360 / 864 Kbps
    ATM QoS class: UBR
    Output Power (Downstream/Upstream): 11.9 / 12.9 dBm
    Attainable Rate (Downstream/Upstream): 11456 / 996 Kbps
    HEC Errors (Downstream/Upstream): 0 / 0
    OCD Errors (Downstream/Upstream): 0 / 0
    LCD Errors (Downstream/Upstream): 0 / 0
    SNR Margin (Downstream/Upstream): 29.2 / 11.0 dB
    Attenuation (Downstream/Upstream): 15.0 / 9.0 dB
    Current speed tests show 1.24 Mbps down and 0.73 Mbps up.

  • Verizon GT704-WG-B modem. Sudden, frequent disconnects.

    Hi, I've been searching on Google and reading forums everywhere for a solution yet I can't seem to find one anywhere. The closest to my issue was this post http://forums.verizon.com/t5/High-Speed-Internet-DSL-and-Dial/Connection-keeps-dropping/td-p/283839, only at the end they OP doesn't really explain how they fixed their problem, only that it stopped.
    The only difference is my internet pauses, the internet light goes off on the modem, begins resetting itself, working again a few moments later, but only for about 5-15 minutes before repeating that process again. This happens randomly and normally happens all at once for a long time before I give up and go to sleep then try the next day.
    I've tried many steps I've read over time from power cycling, using a preferred DNS server, ipconfig/release(and renew [which I read my specific model seems to block me from resetting my IP?]), checking the phone line, and checking the filters.
    In a last ditch effort I tried calling the house on my cell, and after reaching voicemail it seems that the internet would pop off briefly. I thought maybe the problem was the phones, so I unplugged them all and that seemed to work for a few hours. Then tonight (Starting at 9:30PM PST I believe) it began all over again with it resetting itself over and over until I gave up on what I had planned to do.
     I'm hoping someone here can help with my issue.
    One last bit of information; This issue only began happening AFTER recieving a recent upgrade to my speed (From 7MB to 15MB I believe), before then I had almost zero issues with connection and none that a simple reboot of my old modem didn't fix, and I've been with Verizon since I think their DSL first came out.

    DSL Status
    VPI: 0
    VCI: 35
    DSL Mode Setting: Auto
    DSL Negotiated Mode: ADSL2+
    Connection Status: ShowTime
    Speed (down/up): 16319 / 1056 Kbps
    ATM Qos class: UBR
    Output Power (Downstream/Upstream): 12.3 / 19.4 dBm
    Attainable Rate (Downstream/Upstream): 18488 / 1117 Kbps
    HEC Errors (Downstream/Upstream): 1174 / 3307
    OCD Errors (Downstream/Upstream): 231/0
    LCD Errors (Downstream/Upstream): 2 / 0
    SNR Margin (Downstream/Upstream): 7.3 10.0 dB
    Attenuation (Downstream/Upstream): 22.0 / 8.6 dB
    My constant disconnection issue happened again today though it started around 7:00PM rather then 9:30. 

  • How to correlate carmel ASIC output to actual ethernet port?

    On a Nexus 5548UP I have a 10G SM port receiving CRC errors but upstream is not sending errors. I think the receiving switch is stomping the CRC, but I cannot match up the output from "show hardware internal" to the actual port to know for sure.
    Running this command I can see the ASIC number and port ID:
    switch# show hardware internal carmel port ethernet 1/29 | include instance|mac
    carmel instance : 3 <- asic ID
    mac port : 4 <- port ID
    fw_instance : 4
    mac status polling : 1
    Then I am running this command to check for stomps, but I cannot tell which line(s) of output correspond to the port in question.
    switch# show hardware internal carmel asic 3 counters interrupt match stomp
    Slot 0 Carmel 3 interrupt statistics:
    Interrupt name |Count |ThresRch|ThresCnt|Ivls
    -----------------------------------------------+--------+--------+--------+----
    car_fi4_INT_fi_rx_pkt_crc_stomp |1 |0 |1 |0
    car_fi5_INT_fi_rx_pkt_crc_stomp |bc4d5 |0 |1 |0
    car_fi6_INT_fi_rx_pkt_crc_stomp |817d5 |0 |1 |0
    car_fi7_INT_fi_rx_pkt_crc_stomp |bc474 |0 |4 |0
    car_bm4_INT_norm_igrd_crc_stomp |bc52c |0 |4 |0
    car_bm4_INT_norm_egrd_crc_stomp |1 |0 |1 |0
    car_bm5_INT_norm_egrd_crc_stomp |bc4d5 |0 |1 |0
    car_bm6_INT_norm_egrd_crc_stomp |817d5 |0 |1 |0
    car_bm7_INT_norm_igrd_crc_stomp |1 |0 |1 |0
    car_bm7_INT_norm_egrd_crc_stomp |bc474 |0 |4 |0
    car_fw4_INT_ig_pkt_err_eth_crc_stomp |3e |0 |2 |0
    car_fw4_INT_eg_pkt_err_eth_crc_stomp |1 |0 |1 |0
    car_fw5_INT_eg_pkt_err_eth_crc_stomp |bc4d5 |0 |1 |0
    car_fw6_INT_eg_pkt_err_eth_crc_stomp |817d5 |0 |1 |0
    car_fw7_INT_ig_pkt_err_eth_crc_stomp |1 |0 |1 |0
    car_fw7_INT_eg_pkt_err_eth_crc_stomp |bc474 |0 |4 |0
    car_mm4_pb_INT_buf_ecc_crc_rx_crc_stomp |3e |0 |2 |0
    car_mm4_pb_INT_buf_ecc_crc_tx_crc_stomp |1 |0 |1 |0
    car_mm5_pb_INT_buf_ecc_crc_tx_crc_stomp |bc4d5 |0 |1 |0
    car_mm6_pb_INT_buf_ecc_crc_tx_crc_stomp |817d6 |0 |2 |0
    car_mm7_pb_INT_buf_ecc_crc_rx_crc_stomp |1 |0 |1 |0
    car_mm7_pb_INT_buf_ecc_crc_tx_crc_stomp |bc474 |0 |4 |0
    Done.
    Is it as simple as all of the lines above that have '4' in the name (like car_fi4_INT_fi_rx_pkt_crc_stomp) correspond to the port I am concerned with?
    I have checked MTU and and cleaned / reseated the fibers on both ends.

    An update to my problem.  Apparently I misunderstood the concept behind channels and tasks in DAQmx.  With the same type of output I could really just have grouped the two channels under the same task.  All I had to do was to call the DAQmxCreateAIVoltageChan twice and specifiy the two different output terminals for the two channels.  Both of which will be regulated under the same sample clock.
    After that I called the DAQmxWriteAnalogF64 function once, specifying the "dataLayout" parameter to DAQmx_Val_GroupByScanNumber, which should output the sample array interleavingly.
    The program now outputs two identical waveforms synchronized by the same sample clock.
    However the second problem remains.  What happens when I want to vary the frequency of the second channel?  A simple and obvious solution would be to write and equal number of samples for both channels and just change the value of the sample for the second channel according to the frequency.  However this would result in a gigantic array if I have to add more channels later on.
    Is there any way around this?
    Thank you
    Howard

  • RV042 WAN Slow (Yep, another post about this)

    Hi,
    I've searched and read other posts on this here and else where (via google) but cannot seem to resolve the situation.
    To help save time I've compiled a list of various tests (including bypassing the RV042) and configuration options.
    Tests (via DSL Reports) :
    without RV042 (direct connection to T1) 1410 up / 1410 down
    WITH RV042  1094 up / 763kb down
    Hardware:
    new Cisco RV042
    Firmware Version: 1.3.12.19-tm
    Internet Providers:
    WAN 1: Covad T1 via Samsung iBG1000 T1 Router (NAT Disabled, RV042 has been assigned public IP Address)
    WAN 2 (Failover): Atlantic BroadBand (via Surf Board Cable Modem)
    RV042 Configuration:
    MTU has been set to Auto, 1500, and 1492 (currently set to 1500) - speeds remain slow
    SPI Enabled & Disabled - no change
    Setting for Internet Port Speeds (also tried 1512 up for WAN 2 in case of GUI related error)
    Interface
    Upstream
    (Kbit/Sec)
    Downstream
    (Kbit/Sec)
    WAN1
    WAN2
    I think that about covers it, please let me know if there is any other info you need me to provide and thank you in advance for any help you can give.
    - Jordan

    Oh I forgot to mention that on the Easy Access it says my wifi is on but at the top of the phone it still says 4G.  So is it on or not?

  • What Lenovo notebook for Windows/Ubuntu dualboot

    Hey there,
    can anyone recommend a notebook for Windows/Ubuntu dualboot? I've heard that there are many problems with UEFI. I would like to use Ubuntu 12.04.2.
    Best wishes and thanks in advance!

    T530 has been working prett y well for me since November or so... got it with 4GB RAM & 500GB SATA HD, because that was the best price/performance package I could afford at the time.  Since then got a little more OT pay and upgraded to 16GB RAM and a 256GB SSD, and moved the 500GB SATA HD to the UltraBay in lieu of the optical drive which I almost never used. 
    This model came with Windows 7 Professional, and I had zero problems setting it up for multi-boot.  I tinkered with several different distros - Ubuntu, openSUSE, Scientific, Mint, Fedora 18... Ubuntu was one of the smoothest installs, and pretty much everything - including almost all of the function keys for sleep, lock screen, volume, brightness, etc. work 'out of the box'.  Currently running Xubuntu on it for other reasons, but may go back to 'plain' Ubuntu sometime in the near future as not as many of the little things like the Fn keys work in Xubuntu as in mainstream Ubuntu.
    Mine came with the oversized 9-cell battery pack, and that was the one thing that was a major complaint for me originally - the battery life under Linux (any flavor) was about half what it was in Win7; 2-3 hours vs 4-6.  The WebUpd8 site has a number of articles on adding various PPAs that help out with the battery life quite a bit - highly recommended.  Newer Linux kernels (since 12.04) are supposed to have better power management abilities, so I'm not sure 12.04 would be my first choice for that reason.  Some of the subsequent releases have been buggy enough that shorter battery life might be the lesser of two evils.  12.10 had some issues with one of the kernel releases (wasn't just Ubuntu, fwiw... saw the same problem on Fedora 18) right before 13.04 came out that caused problems - like unresponsive black screen after GRUB - with cards that have multiple video adapters (like the T530).  Installing the 'aftermarket' bumblebee drivers via PPA fixed that, while Ubuntu and the kernel team were still fumbling about.  FYI, the bumblebee drivers made a big difference in the power consumption as well.  Xubuntu recenly had a problem where a code error from upstream (XFCE) propagated down and caused semi-random (but very repeatable) logouts from X Windows.  That one has been going on 4+ months (12.10 and 13.04) and still not fixed in the mainstream version (had to install another PPA for a 'patch' to be able to run XFCE at all.  This is why I'm starting to debate about either going 'back' to the 12.04 LTS, or trying to hold things together long enough to get to 14.04 (next LTS)  and staying there until EOL for the hardware...
    YMMV,
    Monte

  • Proxy error - Invalid response from upstream server

    We are using Oracle Application Express Listener for requests between a Web browser and Oracle Application Express engine.
    Tomcat and Java version on the web server (Windows 2008):
    TomCat v 6.0
    Java version "1.6.0_25"
    Application Express version - 4.0.2.00.07
    Access to APEX site happens via Reverse Proxy.
    One of the reports is giving following error message from past few days and there are no log entries in Tomcat server.
    Proxy Error+
    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request GET /appname/f.
    Reason: Error reading from remote server
    What could be possible reasons for this proxy error? Please help with the possible solutions to this problem.
    I have tried restarting Tomcat service, used different browsers, cleared browser cache but for no avail. Error is only on one particular report page.

    Hi,
    Have you tried to access the page directly via tomcat without the reverse proxy? This way you can determine if the problem arises at the reverse proxy or tomcat.
    You say it happens only on 1 specific report page, this makes me think there is something with that page and not with the reverse proxy or tomcat. Arises the error when you access the page directly or via a menu option? Maybe the menu link is not correct otherwise i suggest that you take a good look at that page.
    Kees Vlek.

  • Changed setting to no proxy but not solved problem Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /iam/services/setContext. Reason: Error reading from remote server

    This problem only happens with one website when I try to follow hyperlinks to other pages. They have directed me to Firefox troubleshooting section. I have followed the advice there but it has not solved my problem.

    I haven't been able to go on line since 7.01 and up. I have to use ieexplorer. are you idiots or what. I can't even contact you because i have to be in your latest version but i can't get the internet with the latest version. good bye for good

  • Proxy error while running the financial report in workspace.

    Hi,
    We are using the Hyperion financial reporting 9.3.1 with Essbase as a data source.
    While running a report in workspace, we are getting the 'Proxy error' meassage, which is following-
    "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    '<html><head>
    <title>502 Proxy Error</title>
    </head><body>
    Proxy Error
    <p>The proxy server received an invalid
    response from an upstream server.<br />
    The proxy server could not handle the request <em><a
    href="/hr/modules/com/hyperion/reporting/web/reportViewer/HRRunJob.jsp">GET /hr/modules/com/hyperion/reporting/web/reportViewer/HRRunJob.jsp</a></em>.<p>
    Reason: <strong>Error reading from remote server</strong></p></p>
    </body></html>"
    Do anybody have any idea on this? Any help will be appriciated on this.
    Thanks & Regards,
    Mohit Jain

    Hi Iain,
    We are using Microsoft Internet explorer 6.0. I am not sure about the 'proxy' (As we don't have any proxy setting in Tool--> Internet options--> connection--> LAN setting). We are accessing the Workspace and FR studio via Citrix application. How can I check the proxy.
    Also, I noticed one more point, Report has prompt for seleting 'Account hierarchy'.If we run the report only for one account hierarchy, report is returning the data but while running for multiple account hierarchy, it is throwing the 'Proxy error' as memtioned above.
    Please help us on this.
    Thank & Regards,
    Mohit

  • Need to have mail1 play nice with upstream mail server....

    Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
    On the debian box we're seeing:
    2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
    2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
    And mail isn't piping thru to the mail1 box. Here's the main.cf
    sh-3.2# cat main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all parameters. For the syntax, and for a complete parameter
    # list, see the postconf(5) manual page (command: "man 5 postconf").
    # For common configuration examples, see BASIC_CONFIGURATION_README
    # and STANDARD_CONFIGURATION_README. To find these documents, use
    # the command "postconf html_directory readme_directory", or go to
    # http://www.postfix.org/.
    # For best results, change no more than 2-3 parameters at a time,
    # and test if Postfix still works after every change.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing. When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    #soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes. Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites. If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on. By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain. On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    # mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    # /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    # For example, you define $mydestination domain recipients in
    # the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    # feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix. See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network. Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to. See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    # subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace. Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible. Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi". This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    #recipient_delimiter = +
    # DELIVERY TO MAILBOX
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user. Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #home_mailbox = Mailbox
    #home_mailbox = Maildir/
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception: delivery for root is done as $default_user.
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #mailbox_transport = lmtp:unix:/file/name
    #mailbox_transport = cyrus
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #fallback_transport = lmtp:unix:/file/name
    #fallback_transport = cyrus
    #fallback_transport =
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients. By default, mail for unknown@$mydestination,
    # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
    # as undeliverable.
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    # luser_relay works only for the default Postfix local delivery agent.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #luser_relay = [email protected]
    #luser_relay = [email protected]
    #luser_relay = admin+$local
    # JUNK MAIL CONTROLS
    # The controls listed here are only a very small subset. The file
    # SMTPD_ACCESS_README provides an overview.
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    # For details, see "man header_checks".
    #header_checks = regexp:/etc/postfix/header_checks
    # FAST ETRN SERVICE
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # See the ETRN_README document for a detailed description.
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this service. By default, they are all domains that
    # this server is willing to relay mail to.
    #fast_flush_domains = $relay_domains
    # SHOW SOFTWARE VERSION OR NOT
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter. The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 20
    # DEBUGGING CONTROL
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    debug_peer_level = 2
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    xxgdb $daemon_directory/$process_name $process_id & sleep 5
    # If you can't use X, use this to capture the call stack when a
    # daemon crashes. The result is in a file in the configuration
    # directory, and is named after the process name and the process ID.
    # debugger_command =
    # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    # >$config_directory/$process_name.$process_id.log & sleep 5
    # Another possibility is to run gdb under a detached screen session.
    # To attach to the screen sesssion, su root and run "screen -r
    # <id_string>" where <id_string> uniquely matches one of the detached
    # sessions (from "screen -list").
    # debugger_command =
    # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
    # -dmS $process_name gdb $daemon_directory/$process_name
    # $process_id & sleep 1
    # INSTALL-TIME CONFIGURATION INFORMATION
    # The following parameters are used when installing a new Postfix version.
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    sendmail_path = /usr/sbin/sendmail
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    newaliases_path = /usr/bin/newaliases
    # mailq_path: The full pathname of the Postfix mailq command. This
    # is the Sendmail-compatible mail queue listing command.
    mailq_path = /usr/bin/mailq
    # setgid_group: The group for mail submission and queue management
    # commands. This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    setgid_group = _postdrop
    # html_directory: The location of the Postfix HTML documentation.
    html_directory = no
    # manpage_directory: The location of the Postfix on-line manual pages.
    manpage_directory = /usr/share/man
    # sample_directory: The location of the Postfix sample configuration files.
    # This parameter is obsolete as of Postfix 2.1.
    sample_directory = /usr/share/doc/postfix/examples
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    mydomain_fallback = localhost
    message_size_limit = 52428800
    myhostname = mail1.stanwood.wednet.edu
    mailbox_transport = cyrus
    mydomain = stanwood.wednet.edu
    mailbox_size_limit = 0
    enable_server_options = yes
    inet_interfaces = all
    mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
    smtpd_use_tls = yes
    smtpd_enforce_tls = no
    smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
    smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
    smtpd_sasl_auth_enable = yes
    smtpd_use_pw_server = yes
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
    smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
    content_filter = smtp-amavis:[127.0.0.1]:10024
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    owner_request_special = no
    recipient_delimiter = +
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    # 02/02/09 Server Checkup by Alex
    bounce_queue_lifetime = 6h
    delay_warning_time = 6h
    maximal_queue_lifetime = 2d
    # Topicdesk Frontline Defense
    disable_vrfy_command = yes
    smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
    smtpd_helo_required = yes
    smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
    smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
    smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
    virtual_transport = virtual
    virtual_mailbox_domains =
    sh-3.2#

    Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
    mail1:~ admin$ postconf -n
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    bouncequeuelifetime = 6h
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    delaywarningtime = 6h
    disablevrfycommand = yes
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    maximalqueuelifetime = 2d
    messagesizelimit = 52428800
    mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
    mydomain = stanwood.wednet.edu
    mydomain_fallback = localhost
    myhostname = mail1.stanwood.wednet.edu
    mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
    newaliases_path = /usr/bin/newaliases
    ownerrequestspecial = no
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
    smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
    smtpdenforcetls = no
    smtpdhelorequired = yes
    smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
    smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
    smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
    smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
    smtpduse_pwserver = yes
    smtpdusetls = yes
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains =
    virtual_transport = virtual
    mail1:~ admin$

  • Page leads to proxy error sometimes or taking too much time to load

    Hi All,
    APEX4.0
    Web server: Apache 1.3.9 (Oracle 9iAS 10.0.1.2.2)
    I am getting  the below error at first time when I try to open a page or the page takes 3 to 5 mins to load. From second time on wards, It takes 5 to 8 sec to open as normal. I debugged the page and checked the log. Logs and execution time are looking normal.  why the page takes too much time to load at first time or it leads to proxy error?? Is anybody got same experience before??
    Proxy Error
    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request GET/pls/apex/f.
    Reason : Document contains no data
    Please guide me to find out and  resolve this issue....
    Thanks in Advance
    Lakshmi

    Hi this is what the solution given by your link
    A.1.6 Connection Timeouts Through a Stateful Firewall Affect System Performance
    Problem
    To improve performance the mod_oc4j component in each Oracle HTTP Server process maintains open TCP connections to the AJP port within each OC4J instance it sends requests to.
    In situations where a firewall exists between OHS and OC4J, packages sent via AJP are rejected if the connections can be idle for periods in excess of the inactivity timeout of stateful firewalls.
    However, the AJP socket is not closed; as long as the socket remains open, the worker thread is tied to it and is never returned to the thread pool. OC4J will continue to create more threads, and will eventually exhaust system resources.
    Solution
    The OHS TCP connection must be kept "alive" to avoid firewall timeout issues. This can be accomplished using a combination of OC4J configuration parameters and Apache runtime properties.
    Set the following parameters in the httpd.conf or mod_oc4j.conf configuration files. Note that the value of Oc4jConnTimeout sets the length of inactivity, in seconds, before the session is considered inactive.
    Oc4jUserKeepalive on
    Oc4jConnTimeout 12000 (or a similar value)
    Also set the following AJP property at OC4J startup to enable OC4J to close AJP sockets in the event that a connection between OHS and OC4J is dropped due to a firewall timeout:
    ajp.keepalive=true
    For example:
    java -Dajp.keepalive=true -jar oc4j.jar
    Please tell me where or which file i should put the option
    java -Dajp.keepalive=true -jar oc4j.jar ??????/

  • New error with upgrade jboss/tomcat: "Connection handle has been closed and is unusable"

    Hi,
    This error suddenly appeared when we upgraded from jboss3/tomcat5.0 to jboss4.2/tomcat5.5.
    here's the usecase:
    1) User clicks on report link
    2) Crystal reports web componnent displays screen to fill in report parameters.
    3) user enters parameters and clicks submit
    4) System throws Exception
    The same reports worked fine with jboss 3.2.6/tomcat 5.0. We haven't touched anything in this realm.
    Log Excerpt:
    09:42:18,842 INFO  [datasource] Openning rowset
    09:42:18,904 ERROR [reportdefinition] com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: Connection handle has been closed and is unusable
    09:42:18,905 ERROR [datasource] Failed to open rowset: the query failed to open rowset
    com.crystaldecisions.reports.reportdefinition.datainterface.g: JDBC Error: Connection handle has been closed and is unusable
         at com.crystaldecisions.reports.reportdefinition.datainterface.d.a(Unknown Source)
    To try to narrow down the problem, I've updated the jdbc configuration to
         <track-statements>true</track-statements>   
    here's a recap:
    This Boolean element specifies whether to check for unclosed statements when a connection is returned to the pool. If it is true, a warning message is issued for each unclosed statement. If the log4j category org.jboss.resource.adapter.jdbc.WrappedConnection has trace level enabled, a stack trace of the connection close call is logged as well. This is a debug feature that can be turned off in production.
    Interestingly enough, this error appears slightly upstream:
    (CachedConnectionManager.java:526) - Closing a connection for you.  Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
    java.lang.Throwable: STACKTRACE
         at
    org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
         at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
         at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
         at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
         at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
         at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
         at com.crystaldecisions.reports.common.av.a(Unknown Source)
         at com.crystaldecisions.reports.common.ag.a(Unknown Source)
         at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown
    So the question arises:
    1) Is the jboss datasource overly/aggressively closing result sets?
    2) or is there a coding error in CRXIR2?
    thanks,
    bill
    Full stack trace:
    [2008-03-13 17:26:18,905] [INFO ] org.jboss.resource.connectionmanager.CachedConnectionManager (CachedConnectionManager.java:526) - Closing a connection for you.  Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
    java.lang.Throwable: STACKTRACE
         at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290)
         at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417)
         at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
         at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
         at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
         at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
         at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
         at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
         at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
         at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
         at com.crystaldecisions.reports.common.av.a(Unknown Source)
         at com.crystaldecisions.reports.common.ag.a(Unknown Source)
         at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
         at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.r.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.cf.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.z.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ak.if(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ad.int(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.bk.for(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.v.a(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.v.if(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(Unknown Source)
         at com.crystaldecisions.reports.sdk.DatabaseController.setTableLocation(Unknown Source)
         at org.apache.jsp.reports.processreport_jsp.switchTables(processreport_jsp.java:131)
         at org.apache.jsp.reports.processreport_jsp.loadReport(processreport_jsp.java:68)
         at org.apache.jsp.reports.processreport_jsp._jspService(processreport_jsp.java:227)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.participate.shared.pagecache.client.PageCacheFilter.doFilter(PageCacheFilter.java:760)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.participate.util.servlet.ExpiredPasswordFilter.doFilter(ExpiredPasswordFilter.java:92)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.participate.pe.channels.client.servlet.ChannelUrlFilter.processUrl(ChannelUrlFilter.java:168)
         at com.participate.pe.channels.client.servlet.ChannelUrlFilter.doFilter(ChannelUrlFilter.java:100)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.participate.util.servlet.BlockIpAddressFilter.doFilter(BlockIpAddressFilter.java:224)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.outstart.multiapp.filters.KeepOtherSessionsAliveFilter.doFilter(KeepOtherSessionsAliveFilter.java:88)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at com.participate.util.servlet.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:151)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
         at java.lang.Thread.run(Thread.java:619)

    <p>
    OK. I found the problem along with a workaround.
    </p>
    <p>
    <strong>The problem:</strong>
    </p>
    <p>
    a programming practice clashes with a new jboss 'safety check'.
    </p>
    <p>
    <strong>Programming practice:</strong>
    </p>
    <p>
    crystal reports gets a database connection in one jsp page, then tries to use it on another jsp/servlet
    </p>
    <p>
    <strong>Jboss safety check:</strong>
    Jboss/tomcat new comes configured out-of-the-box with a 'cached connection
    manager', which
    </p>
    <p>
    "Check[s] for unclosed connections and transaction terminated checks in servlets/jsps."
    </p>
    <p>
    <strong> Summary</strong>
    </p>
    <p>
    In short, if a servlet/jsp ends and it leaves a database connection open, Jboss will automatically close it.
    </p>
    <p>
    </p>
    <p>
    <strong>Workaround:</strong><br />
    Comment out two entries in these two files:
    </p>
    <p>
    1) conf/jboss4/pe/deploy/jboss-web.deployer/server.xml
    </p>
    <p>
    2) conf/jboss4/pe/deploy/jboss-web.deployer/META-INF/jboss-service.xml
    </p>
    <p>
    The two entries:
    </p>
    <p>
    </p>
    <p>
    1)
    </p>
    <p>
                 <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"<br />
                    cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"<br />
                    transactionManagerObjectName="jboss:service=TransactionManager" /><br />
    </p>
    <p>
    2)
    </p>
    <p>
          <depends>jboss.jca:service=CachedConnectionManager</depends><br />
    </p>
    <p>
    </p>
    <p>
    <strong>Comments on the workaround</strong>
    </p>
    <p>
    The 'cached connection manager' basically makes sure that the application cleans up after bad programmers. It seems most helpful in development, load testing, or trouble shooting.
    </p>
    <p>
    In production,  you can likely  comment them out with minimal
    impact on the application.
    </p>

  • ABAP Proxy error

    Dear Friends,
    I am facing a problem when i use a ABAP client proxy (asynchronously)
    An error is raised during proxy method call-
    <CODE>SERIALIZE_APPLICATION_DATA</CODE>
    <b>  <ERRORTEXT>Conversion error ABAP => XML (Request Message; error ID: CX_ST_INVALID_XML;
    (/1SAI/TAS00000000000000000005 XML Bytepos.: 0 XML Path:
    Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document) )</ERRORTEXT></b>
    The same proxy runs fine in upstream system (dev) but doesnot run in downstream system (QA) even though all proxy objects have been transferred.
    This proxy & another proxy from the same calling report program  is serialized in a queue.The first proxy is raising this error, but the second proxy call is successful.
    Can someone help,
    Thanks
    Prasenjit

    Hi Guru,
    All the fields in the data type have string - also this roxy works fine in devpt. system- but it doesnt work in downstream QA system.
    Other proxy interfaces in the QA system work fine.
    The error message when i single test the proxy is as follows-
    - <CX_XMS_SYSTEM_ERROR>
      <ID>SERIALIZE_APPLICATION_DATA</ID>
      <P1>Request Message</P1>
      <P2>CX_ST_INVALID_XML</P2>
      <P3>/1SAI/TAS00000000000000000005</P3>
      <P4>XML Bytepos.: 0 XML Path: Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document</P4>
      <INFO />
      <CATEGORY>XIProxy</CATEGORY>
      <AREA>ABAP</AREA>
    <CX_ST_ERROR>
      <ST_PROGNAME>/1SAI/TAS00000000000000000005</ST_PROGNAME>
      <X-ML_OFFSET>0</X-ML_OFFSET>
      <X-ML_PATH />
      <ST_IC>2</ST_IC>
      <ST_TIMESTAMP>20070907163313</ST_TIMESTAMP>
      </CX_ST_ERROR>
    Any other possible solutions ?
    thanks
    Prasenjit

  • How to extract data from multiple tables (always got errors)

    Dear Experts,
    I have a simple mapping to extract data from multiple tables as a source (A, B, C) to a target table (X). Below is the picture:
    (Sources)....(Target)
    A----------------***
    B----------------X
    C----------------***
    Sample Source Data:
    Table A:
    ColA1
    100
    200
    etc
    Table B:
    ColB1 ColB2 ColB3
    10 Y Ten
    20 Y Twenty
    30 Y Thirty
    etc
    Table C:
    ColC1 ColC2
    11
    12
    13
    etc
    Target table (X) should be (just has 1 group INGRP1):
    ColA1 ColB1 ColB3 ColC1
    100 10 Ten 11
    100 10 Ten 12
    100 20 Twenty 21
    etc
    Scenarios:
    1. Directly map from A, B, C to X. Unable to map with error message: "API8003: Connection target attribute group is already connected to an incompatible data source. Use a Joiner or Set operator to join the upstream data first before connecting it into this operator."
    2. Map each source to Expression Operator and then map from each Expression to target table. I am able to map all attributes successfully but got error when validating it with message: "VLD-1104: Attributes flowing into TEST.EXPR_SRC.INGRP1 have different data sources."
    How can I achieve the correct mapping for this purpose?
    Use Joiner? I have no key to join the sources
    Use Set? The sources have different number of columns
    Thanks in advance
    Prat

    Thanks Nico,
    I think it will results data like this:
    100 10 Ten 11
    200 20 Twenty 12
    300 30 Thirty 13
    etc
    and not the expected:
    100 10 Ten 11
    100 10 Ten 12
    100 20 Twenty 21
    etc
    But it inspired me to solve this by adding key expression in each source table (B & C) to be joined to table A with this formula:
    100+TRUNC(INGRP1.COLB1,-2)
    Regards
    Prat

Maybe you are looking for

  • HELP (Apple TV not showing up in Devices list)

    Has anyone resolved this issues. Like many others, i have things set up perfectly. My itunes stream, but when I go back to sync photos,etc. there is no Apple TV in the "Devices" list (as there is no devices list). HEEEEEEELP

  • Tv protection plan

    Hi, I have the tv protection plan and i am currently having problems with my television.  What do I need to do to get it repaired? Regards, Mara

  • Trouble begining to use Reader 9

    I have just downloaded Adobe Reader 9 Version 9.1.2 and when I try to open a PDF I get an error messege "Before proceeding you must first launch Adobe Acrobat and accept the End User License Agreement". When I launch Adobe Acrobat I can't find the EU

  • Overriding forms built-in functions

    Hi, I have made pl/sql -triggers that control the data insert, update and delete functions. T hen i have coded the ON-INSERT, ON-UPDATE, ON-DELETE -triggers and also ON-QUERY. The problem is that when i calla the database trigger, i'm not able to set

  • "Import Price Catalogs" fails with RATE not valid

    Importing BLANKET using "Import Price Catalogs" but it fails with Error RATE cannot be null, IF I pass rate it fails with RATE not valid. CASE#1 po_headers_interface rate_type: Corporate Rate: 6.5 rate_date: xx-xx-xxxx ( same as PO creation date) CAS