java.io.IOException: No content

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

java.io.IOException: No content
at com.sun.mail.imap.IMAPInputStream.fill(IMAPInputStream.java:159)
at com.sun.mail.imap.IMAPInputStream.read(IMAPInputStream.java:208)
at com.sun.mail.imap.IMAPInputStream.read(IMAPInputStream.java:234)
at com.sun.mail.util.BASE64DecoderStream.getByte(BASE64DecoderStream.java:350)
at com.sun.mail.util.BASE64DecoderStream.decode(BASE64DecoderStream.java:243)
at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:148)
at java.io.FilterInputStream.read(FilterInputStream.java:101)
at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.writeFullMimeMessage(EmailWorkPartitioningAgent.java:530)
at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.processInboxMessages(EmailWorkPartitioningAgent.java:237)
at com.bea.wli.sb.transports.email.EmailWorkPartitioningAgent.execute(EmailWorkPartitioningAgent.java:100)
at com.bea.wli.sb.transports.poller.TransportTimerListener.run(TransportTimerListener.java:74)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:217)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:738)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Know the solutions? Share your knowledge to help other developers to debug faster.