Databases
StackOverflow2013
Postsdbo
POConcurrency Problem in Java
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConcurrency Problem in Java
    primarykey
    data
    text
    <p>I am designing a client-server chat application in Java. This is a secure application where the messages are exchanged using cryptographic algorithms. I have one server and it can support many clients. My problem is that when one client logs on the server it works fine, but when another user logs into the system, the server starts giving me bad padding exceptions for the encrypted text. </p> <p>I am not able to figure out the problem, according to my logic, when new connection request to server is made, the server creates a thread for listening to the client. Is it possible that once the instance of thread class is created, it does all the processing correctly for the first client, but not for the second client because the variables in server listener thread class already have some previous value, and thus the encrypted text is not decrypted properly?</p> <p>Please advise how I can make this process more robust so that the number of clients does not affect how well the server functions.</p> <p>Hi, The code is like this :</p> <p>When Server Starts:</p> <pre><code>Socket in= serverSocket.accept(); Receive rlt = new Receive(in); Thread receiveReq = new Thread(rlt); receiveLoginReq.start(); </code></pre> <p>now the Receive Thread waits for the incoming message and do the process according to message type. When more than one client is invoked, Server works fine, problem starts when one client terminates and then again tries to reconnect. Server always gives the Error in following pattern:</p> <ol> <li>First time the HAsh not matched error for second client</li> <li>Second time javax.crypto.BadPaddingException: Given final block not properly padded error</li> </ol> <p>When this happens, I need to restart server and restart both clients, only then both clients works. but again if one client terminates connection and again tries to reconnects, the same 2 errors occurs in the same manner. and then again restart Server. </p> <p>Any Advise will be highly appreciated. Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTara Singh
    1. USTara Singh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POConcurrency Problem in Java
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POConcurrency Problem in Java
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSome code would go along way in allowing us to help you with your problem.
      singulars
      1. POConcurrency Problem in Java
      1. USSasha Chedygov
    2. COTitle shouldn't sound "Java memory management" but rather "problem with concurrency". If you provided some source code more can be said about this problem.
      singulars
      1. POConcurrency Problem in Java
      1. USMirek Pluta
    3. COIt sounds like all the client threads are accessing the same data, in which case you probably need to use synchronized blocks.
      singulars
      1. POConcurrency Problem in Java
      1. USJustin Ardini
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload