search

bmatthias / kolab-android

Automatically exported from code.google.com/p/kolab-android
Other
0 stars 0 forks source link

javax.activation.UnsupportedDataTyoeException #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Kolab Client running and syncing in background
2. log file says: Fatal Error:javax.mail.MessagingException: IOException while 
appending messages (...) nested exception is:
javax.activation.UnsupportedDataTypeException: no object DCH for M(... cannot 
be read as beyond screen edge...)
boundary="----=_Part_0_1184382952.1295510930996"

What version of the product are you using? On what operating system?

0.0.5

Please provide any additional information below.

Sync works, in general.
What else can I provide to help anaylzing the error?

Original issue reported on code.google.com by android....@googlemail.com on 20 Jan 2011 at 8:27

GoogleCodeExporter commented 8 years ago 
typo: it is, of course:        javax.activation.UnsupportedDataTypeException
And it is listed in the "calendar" log.

Original comment by android....@googlemail.com on 20 Jan 2011 at 8:32

GoogleCodeExporter commented 8 years ago 
Could you please upload the exception as explained in:
http://code.google.com/p/kolab-android/wiki/ErrorReporting

And please tell us when you uploaded the exception so we can find it in our 
document.

Regards,

Stefan

Original comment by STrille...@googlemail.com on 20 Jan 2011 at 8:45

GoogleCodeExporter commented 8 years ago 
I am not sure what you expect. There was no crash report splash screen, just 
the error message in the log.

Andy

Original comment by android....@googlemail.com on 6 Feb 2011 at 1:49

GoogleCodeExporter commented 8 years ago 
Hmm seems like the message is "broken" somehow. But our calendar sync is broken 
anyway at the moment and until that is fixed, we have to ignore this bug, since 
we cannot debug it properly, I'm sorry :(

Original comment by STrille...@googlemail.com on 6 Feb 2011 at 2:06

GoogleCodeExporter commented 8 years ago 
sometimes I also see this exception. Seams to be a bug in our java mail 
implementation. A resync helps mostly. Also, sync is not crashing on individual 
errors now.

Original comment by arthur.z...@gmail.com on 25 May 2011 at 4:03

GoogleCodeExporter commented 8 years ago 
Hopefully...

Original comment by arthur.z...@gmail.com on 22 Jun 2012 at 9:38