Hello,
This is very likely the issue classified as bug 49453. The symptom
"java.lang.NumberFormatException: null" has been characteristic of this problem.
Please check the size of C:\CfusionMX\lib\client.properties. If it is only 0 bytes,
then you are experiencing the issue. This is a very rare problem in the ColdFusion
community overall, but very serious for those that have it.
The way that CFMX assigns new client variables is from a file,
{cf_root}\lib\client.properties. This contains the next block of assignable client
variable numbers.
Here is a typical client.properties:
-------------------------
#ClientID Sequence
#Sun Dec 15 18:31:06 EDT 2002
LastID=3300
-------------------------
Every 100 new clients, CFMX opens this file and retreives the LastID value. Then CFMX
adds 100 to this number and re-writes the client.properties file.
This value must be a numeric value, else you will get the following error:
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at coldfusion.runtime.ClientIDHelper.GetIDBlockFromFile(Unknown Source)
at coldfusion.runtime.ClientIDHelper.GetClientId(Unknown Source)
Numeric value means the Java definition of numeric from
http://java.sun.com/j2se/1.3/docs/api/java/lang/Integer.html , although negative
client IDs would be a very bad idea.
- ie:
Parses the string argument as a signed decimal integer. The characters in the string
must all be decimal digits, except that the first character may be an ASCII minus sign
'-' ('\u002d') to indicate a negative value.
The resulting integer value is returned. Throws NumberFormatException if the string
does not contain a parsable integer. Having a zero byte file will not return a
parsable integer.
The short term solution for server stablity is to reinitialize client.properties by
editing changing the the default client variable store in the CFAdmin to something
else, then change it back to what it was originally. This will cause CF to write a
new client.properties file with a base value, but the file will have the proper
format. The other possibility is to keep a frequent backup of that file and restore
it when this error occurs. Be aware that this may cause other secondary effects that
have not been considered yet, but it will alleviate the the null error.
==============
I will personally be out of the office over the holidays, but if you can provide more
details today then I can look into doing something for you and contacting others who
may be able to help you.
To evaluate this bug more closely, the following information would be valuable:
a- Platform, and how many CPUs
b- OS
c- Have you manually edited the file, or have changed permissions on the file.
d- JVM version (default (1.3.1-03) or other?
e- Is there more than one version of CF running on the same machine.
f- Are there more than 1 instance of JRun.exe running on the Task Manager processes
tab?
g- Is the XML (neo-clientstore.xml in the CFusionMX/lib folder) file that holds client
resource information being hosed (corrupted or a zero byte file) at the time the
problem occurs?
h- Is the client.properties (located in the CFusionMX/lib folder) file being hosed
(corrupted or a zero byte file) at the time the problem occurs?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
