Skip to main content

Log messages truncated at 10k?

3 replies [Last post]
andrewherron
Offline
Joined: 2008-04-03
Points: 0

Using the next-gen Java Plugin in 6u14 beta 2 (and possibly beta 1 as well, I've only just noticed this) long strings passed to System.err.println() are truncated with this message:

Trace message truncated for length over 10K

This seems like a pretty arbitrary change to me, the application I work on prints out a 30kb configuration file to the console for support cases - we didn't that was particularly big - so this sort of change is a deal breaker.

I have already updated our code to output the data in 10k chunks but it's annoying to have an extra newline every 10k just to keep the plugin console happy. I'm probably going to log a regression bug but wanted to see if anyone here had feedback on this.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jacobdk
Offline
Joined: 2008-04-21
Points: 0

This also has a very unfortunate side effect. From the Java Console, you can press "s" to "dump system and deployment properties". However, this is longer of any good use in 6u14, since this output is cut off in the middle like this:

deployment.version = 6.0
java.quick.star
Trace message truncated for length over 10K

Dumping the full system and deployment properties is a very convenient way of troubleshooting misc. things, but due to this change, it's hard to use this feature for anything now, since there doesn't seem to be any way to get the full list anymore.

Please fix this.

Thanks in advance,
Jacob

andrewherron
Offline
Joined: 2008-04-03
Points: 0

I never bothered to log a bug after we implemented the workaround in our code, but that's pretty bad. Can you log it on bugs.sun.com for me? They're more likely to listen to a truncation in their own code than something I write to the console ;)

jacobdk
Offline
Joined: 2008-04-21
Points: 0

I've logged a bug on this:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6850604

Let's see what they say to it....

EDIT: They have now accepted this as being a bug, meaning it will probably be fixed in an upcoming release. From reading the evaluation, it looks like you can expect your issue to be fixed too, Andrew. :-)

Jacob