[xep-support] Re: "wrong state RND, should be RDY" - any ideas?

Steve Anderson steveo at member.fsf.org
Thu Aug 9 04:55:36 PDT 2012


Great question.  Unfortunately I'm piping the output to /dev/null

I'll see if I can get our IT guys to modify the startup script to get a log..

      Steve

On Wed, Aug 8, 2012 at 11:16 PM, Khachik Kocharyan <khachik at renderx.com> wrote:
> What is the stacktrace from the server side, if any?
>
> Khachik
>
>
> On Օգս 8, 2012, at 23:46, Steve Anderson wrote:
>
>> Thanks.  The confusing thing, from my perspective, is that it usually
>> works, but if fails intermittently.
>>
>> What else could cause an IOException?  Disk space issues?  Network
>> issues?  Memory issues?
>>
>>      Steve
>>
>> On Wed, Aug 8, 2012 at 9:38 AM, Khachik Kocharyan <khachik at renderx.com>
>> wrote:
>>>
>>> Steve,
>>>
>>> The stacktrace means you are calling Client.shutdown while rendering is
>>> in
>>> process or it is stopped by IOException.
>>> This may be caused if your code calls the `Client.shutdown()` method in a
>>> finally block.
>>>
>>> Regards,
>>> Khachik
>>>
>>>
>>>
>>> On Օգս 8, 2012, at 22:19, Steve Anderson wrote:
>>>
>>>> I'm getting the following error when generating a PDF via cliser - any
>>>> ideas?
>>>>
>>>> ========================================================
>>>>
>>>> XEP: event page-number 3943
>>>> java.net.SocketException: Socket closed
>>>>        at com.renderx.xepx.cliser.Protocol.recvMsg(Protocol.java:64)
>>>>        at com.renderx.xepx.cliser.Client.render(Client.java:120)
>>>>        at com.renderx.xepx.cliser.Client.main(Client.java:274)
>>>> Exception in thread "main" com.renderx.xepx.cliser.ProtocolException:
>>>> wrong state RND, should be RDY
>>>>        at com.renderx.xepx.cliser.Client.chkst(Client.java:48)
>>>>        at com.renderx.xepx.cliser.Client.shutdown(Client.java:164)
>>>>        at com.renderx.xepx.cliser.Client.main(Client.java:240)
>>>>
>>>> ========================================================
>>>>
>>>> I have a couple of suspicions (out of memory, a bad graphic) but I
>>>> thought I'd ask if this is a common error message before I spend too
>>>> much time trying to debug it myself.
>>>>
>>>> Thanks,
>>>>
>>>>     Steve
>>>> --
>>>> steve.anderson at gmail.com
>>>> What you say does matter, and so does how you say it.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> (*) To unsubscribe, please visit
>>>> http://lists.renderx.com/mailman/options/xep-support
>>>> (*) By using the Service, you expressly agree to these Terms of Service
>>>> http://w
>>>> ww.renderx.com/terms-of-service.html
>>>
>>>
>>>
>>> _______________________________________________
>>> (*) To unsubscribe, please visit
>>> http://lists.renderx.com/mailman/options/xep-support
>>> (*) By using the Service, you expressly agree to these Terms of Service
>>> http://w
>>> ww.renderx.com/terms-of-service.html
>>
>>
>>
>>
>> --
>> steve.anderson at gmail.com
>> What you say does matter, and so does how you say it.
>>
>> 
>>
>>
>



-- 
steveo at member.fsf.org
What you say does matter, and so does how you say it.

!DSPAM:87,5023a55363736716173853!




More information about the Xep-support mailing list