Client 4.2 update issues

Client 4.2 update issues

Postby Maihem » Mon Jun 06, 2011 2:50 pm

The WoL Client has been updated to support 4.2-style combat logs.

Please report any issues you have with the update in this topic. Note that this does not include questions like "how do I upload a combat log". For these issues, please create your own topic.
Maihem
Site Admin
 
Posts: 2700
Joined: Sun Apr 05, 2009 4:14 pm

Re: Client 4.2 update issues

Postby sheadeo » Mon Jun 06, 2011 5:02 pm

I get a Failed to read file, error parsing line 1: com.wol3.client.data.invalidlineException on line 1: jaca.lang.runtimeException: Invalid string 0x8000000
sheadeo
 
Posts: 2
Joined: Thu Mar 24, 2011 10:23 pm

Re: Client 4.2 update issues

Postby Maihem » Mon Jun 06, 2011 6:35 pm

Try control panel, programs, java, temporary internet files: view, wol client and click the red cross. Then relaunch.
Maihem
Site Admin
 
Posts: 2700
Joined: Sun Apr 05, 2009 4:14 pm

Re: Client 4.2 update issues

Postby diaolos » Mon Jun 06, 2011 10:50 pm

Maihem wrote:Try control panel, programs, java, temporary internet files: view, wol client and click the red cross. Then relaunch.

I have the same problem and i try the above but it doesn't work!Can you please suggest something else??
diaolos
 
Posts: 1
Joined: Mon Jun 06, 2011 10:44 pm

Re: Client 4.2 update issues

Postby Lorune » Mon Jun 06, 2011 11:52 pm

Exactly same problem here, deleted the app from the console and unable to upload the log aswell
Lorune
 
Posts: 4
Joined: Mon Jun 06, 2011 11:50 pm

Re: Client 4.2 update issues

Postby Rcsnowball » Tue Jun 07, 2011 12:03 am

I had same problem. Seen another post about deleting first line. Cause of possible corruption. Noticed the file only had 2 lines when viewed with notepad. So didn't bother anymore with that file. Cleared the Java Temp file like Maihem mentioned. Tried sending another file which was 21MB and it went through fine. Without moding file at all. The first file was only 1KB which failed. The old Client used to prompt when a file was too small to upload. Below is the Java console log if it helps.

Exception caused by line 1, contents: "6/5 11:13:30.967 SPELL_CAST_START,0x05800000009A9AFB,"Vilmos",0x518,0x0000000000000000,nil,0x80000000,86004,"Blackfallow Ink",0x1"
com.wol3.client.data.InvalidLineException on line 1: java.lang.RuntimeException: Invalid string: 0x80000000
Last edited by Maihem on Tue Jun 07, 2011 1:37 am, edited 1 time in total.
Reason: Shorten stack trace
Rcsnowball
 
Posts: 1
Joined: Mon Jun 06, 2011 11:46 pm

Re: Client 4.2 update issues

Postby Maihem » Tue Jun 07, 2011 1:39 am

All posts above boil down to the same issue. The root of this issue lies with the combat log format detection routine. It incorrectly detected a 4.2-style combat log format when the first event of the log had no target. I've implemented a fix, which has been deployed. Relaunching the client from the link on the website should resolve the problem.

If not, please clear your JWS cache using Control Panel -> Programs -> Java -> Temporary Files -> View -> World of Logs Client -> click the red cross. Then relaunch. If you need to perform these steps (and they resolve the issue), then please post back here as that means something fishy is going on with the JNLP versioning.
Maihem
Site Admin
 
Posts: 2700
Joined: Sun Apr 05, 2009 4:14 pm

Re: Client 4.2 update issues

Postby Lorune » Tue Jun 07, 2011 3:17 pm

Working fine now again after redownloading
Lorune
 
Posts: 4
Joined: Mon Jun 06, 2011 11:50 pm

Re: Client 4.2 update issues

Postby Amo » Wed Jun 29, 2011 7:58 am

I'm getting this error trying to upload my log from tonight's first 4.2 raid, using the updated client:
Image

Zipped combat log:
http://www.mediafire.com/?0ivmk827772di3f
Last edited by Amo on Wed Jun 29, 2011 8:39 am, edited 1 time in total.
Amo
 
Posts: 1
Joined: Wed Jun 29, 2011 7:53 am

Re: Client 4.2 update issues

Postby Billeh » Wed Jun 29, 2011 8:21 am

Amo wrote:I'm getting this error trying to upload my log from tonight's first 4.2 raid, using the updated client:



I'm getting basically the same (from what I can tell) general error as Amo.

Image

RAR'd file of the log
http://www.mediafire.com/?mlrxi499b372icp
Billeh
 
Posts: 1
Joined: Wed Jun 29, 2011 8:18 am

Next

Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 2 guests