[xep-support] Problem during the insertion of an image in a document

[ORIOU Emmanuel]

David,
It's impossible to run WAS 3.5. 3 with another version of Java than 1.2.2 and the problem persists when
I use the protocol HTTP to insert an image in a PDF document.

Sincerely,

Emmanuel ORIOU

David Tolpin a écrit :

> > Hello David,
> > With JVM 1.2.2 (WAS 3.5.3 : Solaris VM (build patc.2000.05.19.09.11,
> > native threads, sunwjit)), XEP return this error :
>
> > (S (parse ))
> > (I (meta-info )(masters )(sequences (sequence [master-reference
> > page](flow [flow-name xsl-region-body]))))
> > (F (BkMaker
> > (sequence page (flow [page-number 1])
> > (static-content [page-number 1])
> > )))
> > (T (SAX [page-number 1]SIGBUS 10 bus error
> >     si_signo [10]: BUS
> >     si_errno [0]:
> >     si_code [1]: BUS_ADRALN [addr: 0xec9a582a]
>
> >         stackpointer=EFFFD1C0
>
> > Inconsistent thread : best efforts attempt (may fail)
> > "Image Fetcher 0" (TID:0xe8b660, sys_thread_t:0xe8b598, state:CW,
> > thread_t: t at 13, threadID:0xe9a81dd8, stack_bottom:0xe9a82000,
> > stack_size:0x20000) prio=8
>
> > [1] sun.awt.image.ImageFetcher.nextImage(ImageFetcher.java:155)
> > [2] sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:211)
> > [3] sun.awt.image.ImageFetcher.run(ImageFetcher.java:187)
> > -------------------
>
> > Inconsistent thread : best efforts attempt (may fail)
> > <null>Abort (core dumped) .
>
> > What's the problem ?
>
> Emmanuel,
>
> the problem is obviously with sun.awt code trying to fetch the image.
> This is an internal java vm problem -- SIGBUS is not a good thing even
> with random input.
>
> Is it possible to run WAS with another version of Java? Does the problem
> persist with images retrieved via a different protocol?
>
> David
> -------------------
> By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html

-------------------
By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html