• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Really weird problem w/ FileHandler and -d64 option

 
Spencer J Lee
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm seeing a strange problem and wondering if anyone else has seen and fixed this too...
the java command i'm runnning:
java -d64 -Xmx8192m -classpath <classpath> <my class>
the relevent portion of code:

the output i'm seeing:
Creating file handler for:/logs/logfile
And that's it! There are no exceptions thrown. The process just seems to die and disappear.
now, if i remove the "-d64 -Xmx8192m" options, it works fine and I see the complete output (i.e. including the "Created file handler" message.)
The file does exist and i'm running a solaris system. The uname output is
SunOS flex-sf-01 5.8 Generic_108528-20 sun4u sparc SUNW,Ultra-4
Anyone have any ideas?
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are no exceptions thrown. The process just seems to die and disappear.
Often this means there is an exception (or Error) being thrown, but it's being caught and ignored somewhere. I suggest making absolutely sure there's nothing being thrown by catching all Throwable (just for testing):

If you do find anything thrown, first figure out where you've got a catch block that's catching a throwable without providing a visible error message, and fix that. Then figure out what's causing whatever the error message says.
 
Spencer J Lee
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Found the exception! Now just got to find a way to handle it
THanks!
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm serious about what you should do first though. Do not tolerate any code in your program which catches an exception and hides it without reporting it, unless you are absolutely certain you know why the exception was thrown, and why it's OK to ignore. (InterruptedException is the most common example of this.) Empty catch blocks are EEEVIL!
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic