How to solve [closed]

In My Java application I have clicked on Wicket dropdown value and application processing our logic then we got below error in logs and nothing in my application.

<BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.>

I have increased the value of CompleteMessageTimeout to 90 in WebLogic and its working but i want to know why this error is coming in the application and can we solve this issue without increase the value in WebLogic because i will prefer any change in the java code.

I am using below technology in my application:

Java 1.5

Wicket 1.3

WebLogic 12c

Spring

Hibernate

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

closed as unclear what you're asking by Erwin Bolwidt, martin-g, greg-449, GhostCat, Nirekin Nov 14 '18 at 13:24

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

add a comment |

In My Java application I have clicked on Wicket dropdown value and application processing our logic then we got below error in logs and nothing in my application.

<BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.>

I am using below technology in my application:

Java 1.5

Wicket 1.3

WebLogic 12c

Spring

Hibernate

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

closed as unclear what you're asking by Erwin Bolwidt, martin-g, greg-449, GhostCat, Nirekin Nov 14 '18 at 13:24

add a comment |

In My Java application I have clicked on Wicket dropdown value and application processing our logic then we got below error in logs and nothing in my application.

<BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.>

I am using below technology in my application:

Java 1.5

Wicket 1.3

WebLogic 12c

Spring

Hibernate

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

In My Java application I have clicked on Wicket dropdown value and application processing our logic then we got below error in logs and nothing in my application.

<BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.>

I am using below technology in my application:

Java 1.5

Wicket 1.3

WebLogic 12c

Spring

Hibernate

java weblogic wicket weblogic12c

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

edited Nov 14 '18 at 7:01

martin-g

12.2k1926

asked Nov 14 '18 at 6:30

Nitin

318

asked Nov 14 '18 at 6:30

Nitin

318

asked Nov 14 '18 at 6:30

Nitin

318

closed as unclear what you're asking by Erwin Bolwidt, martin-g, greg-449, GhostCat, Nirekin Nov 14 '18 at 13:24

add a comment |

1 Answer
1

active

oldest

votes

I can take a thread dump after the action (click) and see where your application is stuck. From there you can decide what you need to do.

A wild guess but I would bet on some database operation taking too long.

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

add a comment |

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

I can take a thread dump after the action (click) and see where your application is stuck. From there you can decide what you need to do.

A wild guess but I would bet on some database operation taking too long.

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

add a comment |

I can take a thread dump after the action (click) and see where your application is stuck. From there you can decide what you need to do.

A wild guess but I would bet on some database operation taking too long.

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

add a comment |

I can take a thread dump after the action (click) and see where your application is stuck. From there you can decide what you need to do.

A wild guess but I would bet on some database operation taking too long.

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

I can take a thread dump after the action (click) and see where your application is stuck. From there you can decide what you need to do.

A wild guess but I would bet on some database operation taking too long.

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

answered Nov 14 '18 at 7:01

martin-g

12.2k1926

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

add a comment |

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 7:45

so if i tune db operation then we don't need to increase CompleteMessageTimeout value and how we will take thread dump.

– Nitin
Nov 14 '18 at 8:17

You can take a thread dump with kill -3 PROCESS_ID (Unix, Linux) or attach to the Java process with jconsole and click the button in it. You better google for more details.

– martin-g
Nov 14 '18 at 8:37

add a comment |

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Pfthb