java.lang.exception: word is too big
Hi everybody!
I have a problem need your help. At present I have a server-client application, server running on Linux enviroment, client running on Window enviroment. After a period of time, there is a exception thrown to console: java.lang.Exception: word is too big, try to use less letter ..... And at that time, no more client can connect to client, however clients which connected to server from before still run as normal. Please help to fix this. Thank you very much
It sounds like the code in question was written poorly. It's bad for it to throw Exception (as opposed to a specific subclass).
Look at the stack trace. Find out what's going on. Then look at the way that the application deals with exceptions -- is it leaving the relevant objects in a correct state?
It sounds like you have a painful debug/cleanup task in front of you. My sympathies.
The problem is I can not catch this exception, so I can not see what the stack trace is and can not know exactly where the error is. According to you, what happening?
> The problem is I can not catch this exception, so I
> can not see what the stack trace is and can not know
> exactly where the error is. According to you, what
> happening?
Nobody can tell because it is your program.
Search the source for the error message you are seeing.
What do you mean you can't catch it? Why not?
I thought you said it was being thrown to the console.Is there no stack trace? Can't you cut-and-paste the data to a file?
Is this a program that you have any control over? Do you have the source code? Did you or somewhere where you work write it?
It's pretty much impossible for me to tell what's happening -- my magical abilities are not as extensive as some would have you believe. However from your description, it sounds like it's garbage code that isn't dealing with exceptions properly.
This seems related: http://www.jforum.net/posts/list/927.page
I can not upload the source code here because it's so big. Before I have never ever met this error. Nearly I have a new server linux machine, and I run my program on this machine, as a result I have had this problem. I say I can catch this exception means I try to trace it by in catch and throw but nothing can be catched. And "word is too big, try to use less letters..." is not mine. I saw it in console. At first, I don't know why client can not connect to server, so I try to find out it in console mode and as you know I find out this exception. If anybody have ever met this error. Please explain it to me and help me to resolve it. Thanks
You CAN catch any exception you want.You are going to have to catch it. Otherwise you are doomed.
I know you can catch every exception, but in my case, I don't know the reason why it's impossible. I think that there is a connection or open socket limit on Linux enviroment. Is there any idea about this?
> I know you can catch every exception, but in my case, I don't know the reason why it's impossible.
Neither do I.
This exception is not thrown by Java or by any Java system I am aware of. It is nothing to do with Linux or sockets either. It is coming from the application.
ejpa at 2007-7-15 5:44:24 >
Hi!
I think you are the developer of the application, then if you have the source code with you, then debug it, follow the execution and check where the exception is thrown,
If that doesn't change anything, use System.out.println in every catch of your code.. just print anything that you will remember that is exception is of this class.
Hope I helped
Thanks everybody. I will try it. If there is anybody has the same error, please contact to me to solve it together. Once again thank you very much
Good grief. Don't hold your breath waiting.
ejpa at 2007-7-15 5:44:24 >
Thanks for reminding me. I have to debug, debug and debug instead of waiting for something happens to myself.
word to big? is that a custom error mes?
SvHa at 2007-7-15 5:44:24 >
> word to big? is that a custom error mes?
No. That is half of a corollary: "word is to big as byte is to small".
"Word is too big." is a custom error message, but that really doesn't say anything. It should say "Pixelized word is too big for container.", but that doesn't help much either. The background or box or whatever the "container" is is not really a container, not really. A more concise message would be "The word [theword] as it is formatted does not fit within the bounds of the intended container [nameofintendedcontainer]." If the original coder had used a message like that then the debugging would be easy.
If an software package that generates the error has been identified, the first thing you should probably do is confirm that you're actually using that package. Look at the jars on your classpath. Also make certain that none of your code generates the message.
Then go to the web site for that software package. Try to download documentation that might tell you what it means.
If it's a commercial package, contact the vendor.
Look at the stack trace and find out what methods you're calling that invoke the code in the external package. You're probably passing it bad arguments.
See if there are any forums specifically for that package on the package's or its vendor's web site.
Hi everybody!
Firstly, I want to say thanks to everyone. I've found out the reason why there is that error message. But at present it's not the reason that make client not to connect to server. Is there anybody know about connection or open socket limit on linux enviroment? Because I just meet this case when I run my application on new linux machine. Please help me!!!!.
You need to tell us what exception you got and what was its full text message.
ejpa at 2007-7-21 13:13:32 >
At this present, no exception or error is thrown, I'm sure of this. The problem is if client is connected to server and running, it's ok, nothing to say about this, but if this is a new client, he could not connect to server while other clients still run in normally. Why?
> At this present, no exception or error is thrown, I'm
> sure of this. The problem is if client is connected
> to server and running, it's ok, nothing to say about
> this, but if this is a new client, he could not
> connect to server while other clients still run in
> normally. Why?
Because of tidal lock.
.....
What exception is the CLIENT getting? Someone, somewhere is getting some sort of exception.
Client is getting no exception. Just socket can not be created, so I put a question, is there any connection limit on Linux system ?
> Client is getting no exception.
This is not true!
>Just socket can not
> be created,
This is an exceptional condition!
> so I put a question, is there any
> connection limit on Linux system ?
Yes. Every system has finite limits on every resource.
I kind of doubt this is actually your problem. I suspect more it is an application limit than an OS limit.
