• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

javac message file is broken

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I got the following error in a jsp,
JAVAC MESSAGE FILE IS BROKEN: key=javac.err.branch.too.big, arguments=null, null, null

when i used <bean:write name="formbeanName" property="properyName" /> more than 81 times i get this error. Is there any restriction on the number of bean:writes to be used in a JSP Page?

Thanks in advance.
Kavi
[ November 08, 2004: Message edited by: Bear Bibeault ]
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Large JavaServer Pages (JSP) might give the following message in the WebSphere Application Server log:

JAVAC MESSAGE FILE IS BROKEN:
key=javac.err.branch.too.big at runtime If this occurs, follow these steps:

Set the JVM system property to true:

com.sun.tools.javac.main.largebranch = trueRestart the server and request the JSP again.
JVM properties can be set using the Administrative console to set up arguments for the Java Virtual Machine (JVM) or by creating a Custom Property
 
Bartender
Posts: 1845
10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The other solution would be to write a smaller JSP file.

There is an inherent size limitation of a method in java.
Your JSP is producing code that exceeds that limitation.

reply
    Bookmark Topic Watch Topic
  • New Topic