Re: printing from java app

[Jeremy Smallman <jeremy.smallman%doxsystems.com@localhost>]

Thanks for the tip.  Here's what I found in one of the processes when
trying to open the /dev/lpt0 port in the java app:
                        .
                        .
                        .               
 16935      1 java     CALL  gettimeofday(0xb65fee18,0)
 16935      1 java     RET   gettimeofday 0
 16935      1 java     PSIG  SIGSEGV caught handler=0xbbb9ef20
mask=(3,33): code=SEGV_MAPERR, addr=0x4, trap=14)
 16935      1 java     CALL  rt_sigreturn(0xb65fef40)
 16935      1 java     RET   rt_sigreturn -1 errno -2 No such file or
directory
 16935      1 java     CALL  write(2,0xb65fcd9c,0x39)
 16935      1 java     GIO   fd 2 wrote 57 bytes
       "jpos.JposException: Can not open the communications port."
 16935      1 java     RET   write 57/0x39
 16935      1 java     CALL  write(2,0xb65fcdcc,1)
 16935      1 java     GIO   fd 2 wrote 1 bytes
                        .
                        .
                        .

I'm running the java app as root so permissions shouldn't be an issue. 
It seems the app thinks the port doesn't exist or it thinks the printer
is not attached to the port . . .?  This java application works fine
with the printer on an OpenSUSE box, so I know it's not a problem with
the java app.

Jeremy


On Mon, 2009-03-23 at 18:07, Christos Zoulas wrote:
> In article <1237845410.10280.74.camel@v250>,
> Jeremy Smallman  <jeremy.smallman%doxsystems.com@localhost> wrote:
> >It's difficult to see exactly what's happening when I try to open the
> >port from the java app because ktrace -i just keeps spitting data out
> >non-stop (running the app for about 11 seconds to do what I need to do
> >output 102260 lines).  I was using kdump -l to follow the output but
> >that's useless now.  Going back to view that data from ktrace I still
> >don't see anything that sticks out. There are about 13 or 14 java
> >processes though running with this app.  
> >
> 
> Start the process and then attach each one of them with 
> ktrace -i -p pid -f kt.pid, just before you print.
> 
> christos