OK, tested again with glassfish-v3_1-b01-12_31_2009.zip did all my tests -- there are no timeout issues or short file issues with this version. still see 2 things that seem wierd ??? as before: >> the WMV file is always received BEFORE the console app is loaded with >> contentType==text/plain;charset=iso-8859-1, >> and WMV mime type is not defined in the default-web.xml >> >> the WMV file is always received AFTER the console app is loaded with >> contentType==null, >> and WMV mime type is not defined in the default-web.xml also -- with netbeans starting glassfish - the first time the standalone test client is run in debug mode or i attempt debugger attach to glassfish -- the glassfish admin console app is "loaded". if i stop glassfish with netbeans and then restart glassfish with netbeans - without restarting netbeans, debugger attach attempt or running test client in debug mode does not cause admin console app to "load". but the contentType mime type received from glassfish is different for WMV files received where the WMV mime type is not defined in default-web.xml -- depending on if the admin console app has been loaded or not. gary ----- Original Message ----- From: "Justin Lee" To: Cc: "emiddio-verizon" Sent: Wednesday, March 31, 2010 5:13 PM Subject: Re: gfv3 30second upload timeout > I'm actually seeing an unrelated test fail on 1.9.18 that worked on 1.9.19 > after I ported the code over so I'm looking into the diffs to see what > would affect that. Could you try your test on a v3 nightly build (which > uses 1.9.19-beta1) and see if it works? I have a sneaking suspicion that > it just might. I'm looking at a particular diff now that looks promising. > I'll know more in a few hours. > > On 3/31/10 4:24 PM, emiddio-verizon wrote: >> i have been testing extensively various experiments with stock gfv3 and >> gfv3 with a grizzly_config.jar built 3 days ago. >> --BTW -- how can i completely replace grizzly the stock grizzly in gfv3 >> with a new one ? -- >> >> i have kept notes -- but to summarize here now. >> >> i have 2 clients -- one GETs a file from gfv3 with a .wmv extension -- >> not defined in default-web.xml; >> the other GETs a file with a .zip extension -- defined in default-web.xml >> >> i have tested with gfv3 in debug mode and not in debug mode; also tested >> with debugger attached and before >> the 1st debugger attach. >> >> i have tested with clents run in debug mode and not in debug mode. >> >> ------------- >> >> i only receive a "short" file (after 30secs) -- after i see in the gfv3 >> log the following: >> ============================ >> INFO: The Admin Console is already installed, but not yet loaded. >> INFO: The Admin Console is loading... >> INFO: Created HTTP listener http-listener-1 on port 8080 >> INFO: Created HTTP listener http-listener-2 on port 8181 >> INFO: Created HTTP listener admin-listener on port 4848 >> INFO: Created virtual server server >> INFO: Created virtual server __asadmin >> INFO: Virtual server server loaded system default web module >> INFO: SEC1002: Security Manager is OFF. >> SEVERE: SEC5054: Certificate has expired: [ >> [ >> Version: V1 >> Subject: OU=Secure Server Certification Authority, O="RSA Data >> Security, Inc.", C=US >> Signature Algorithm: MD2withRSA, OID = 1.2.840.113549.1.1.2 >> Key: Sun RSA public key, 1000 bits >> modulus: >> 6144706769222379850430183405655235862870193813433361902309516534729547168229223442088128897090426025874990958624426272027915771330043379079076269082776443120496525109458437435793974957144923190172655546279112796066635455545786300647745888353781002359412766112775410851780140804282673804950495744761467 >> public exponent: 65537 >> Validity: [From: Tue Nov 08 16:00:00 PST 1994, >> To: Thu Jan 07 15:59:59 PST 2010] >> Issuer: OU=Secure Server Certification Authority, O="RSA Data >> Security, Inc.", C=US >> SerialNumber: [ 02ad667e 4e45fe5e 576f3c98 195eddc0] >> ] >> Algorithm: [MD2withRSA] >> Signature: >> 0000: 65 DD 7E E1 B2 EC B0 E2 3A E0 EC 71 46 9A 19 11 e.......:..qF... >> 0010: B8 D3 C7 A0 B4 03 40 26 02 3E 09 9C E1 12 B3 D1 ......@&.>...... >> 0020: 5A F6 37 A5 B7 61 03 B6 5B 16 69 3B C6 44 08 0C Z.7..a..[.i;.D.. >> 0030: 88 53 0C 6B 97 49 C7 3E 35 DC 6C B9 BB AA DF 5C .S.k.I.>5.l....\ >> 0040: BB 3A 2F 93 60 B6 A9 4B 4D F2 20 F7 CD 5F 7F 64 .:/.`..KM. .._.d >> 0050: 7B 8E DC 00 5C D7 FA 77 CA 39 16 59 6F 0E EA D3 ....\..w.9.Yo... >> 0060: B5 83 7F 4D 4D 42 56 76 B4 C9 5F 04 F8 38 F8 EB ...MMBVv.._..8.. >> 0070: D2 5F 75 5F CD 7B FC E5 8E 80 7C FC 50 ._u_........P >> ] >> INFO: Security startup service called >> INFO: SEC1143: Loading policy provider >> com.sun.enterprise.security.provider.PolicyWrapper. >> INFO: Realm admin-realm of classtype >> com.sun.enterprise.security.auth.realm.file.FileRealm successfully >> created. >> INFO: Realm file of classtype >> com.sun.enterprise.security.auth.realm.file.FileRealm successfully >> created. >> INFO: Realm certificate of classtype >> com.sun.enterprise.security.auth.realm.certificate.CertificateRealm >> successfully created. >> INFO: Security service(s) started successfully.... >> INFO: Initializing Mojarra 2.0.2 (FCS b10) for context '' >> INFO: Loading application __admingui at / >> INFO: Loading __admingui Application done is 7784 ms >> INFO: The Admin Console application is loaded. >> =========================== >> >> the Admin Console is caused to be loaded by any of the following: >> >> --try to attach to gfv3 with debugger when gfv3 is not run in debug mode >> --run client in debug mode >> --debugger attach to gfv3 when run in debug mode >> --go to http://localhost:4848 -- which dispays in browser the Admin >> Console web page >> >> any time the console app has been loaded -- i can no longer use my test >> programs to GET a complete file -- >> where i have delays - Thread.sleep(10); to cause the dnload/upload to >> take more than 30seconds. >> >> before the console app is loaded i always get a complete -- non-short >> file -- usually takes about 70seconds to complete. >> >> the ZIP file is always received with a contentType==application/zip when >> received complete or short, >> and ZIP mime type is defined in default-web.xml. >> >> the WMV file is always received BEFORE the console app is loaded with >> contentType==text/plain;charset=iso-8859-1, >> and WMV mime type is not defined in the default-web.xml >> >> the WMV file is always received AFTER the console app is loaded with >> contentType==null, >> and WMV mime type is not defined in the default-web.xml >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@grizzly.dev.java.net > For additional commands, e-mail: users-help@grizzly.dev.java.net >