Got weblogic.socket.MaxMessageSizeExceededException
We use web start to call a session to query database.
We also add the parameter -Dweblogic.MaxMessageSize=200000000 in jnlp.
The following are the jnlp.
<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" codebase="http://localhost:7011/testws/" href="testws.jnlp">
<information>
<title>Jnlp Testing</title>
<vendor>test</vendor>
<homepage href="http://localhost:7011/" />
<description>Testing</description>
</information>
<resources>
<j2se version="1.6+" java-vm-args="-Xmx1G -Dweblogic.MaxMessageSize=value"/>
<jar href="TestJnlp.jar" />
</resources>
<application-desc main-class="com.test.Application1" />
</jnlp>
However, we still got weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
Where should we add '-Dweblogic.MaxMessageSize'?
Thanks.
Sounds like you need to set it on the server. It's a WebLogic question in any case, nothing to do with (i) JNLP (ii) this forum or (iii) this site. Locking.
Similar Messages
-
Weblogic.socket.MaxMessageSizeExceededException: Incoming message of size:
Hi ,
I have problems with the maximun message size using T3. I am trying to get large data from a remote client but i get the following exception(Here we are accessing jasper reports thru tomcat server from Weblogic,Tomcat and weblogic servers are in different machines). Even after setting the value -Dweblogic.MaxMessageSize parameter as '20000000', still the problem is alive on my tomcat system.
following is the error:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
Could any one suggest us to resolve this problem, Greatly appricated.
Regards,
Venkata KumarHi,
Here we have weblogic and tomcat servers are running on different servers(Even both app server and web server on same m\c also we are facing same problem).this problem am facing while accessing jasper reports which contains results set more than 37000 records, am able to retreive the jasper reports successfully till 37000 records and if u provide query more than 37000 this is problem am encountering in tomcat side.I have deployed my jasper iReports stuff in weblogic server and web related stuff under tomcat server.
i am able to retreive the data successfully till 37000 records and more than that creating this problem on tomcat side.
Please let me know if you any more information on this issue.
Thanks a lot for quick response!
Thanks,
Venkata -
Weblogic.socket.MaxMessageSizeExceededException
I have a long running one-way interface process...it takes like 2 hours to complete...after the process is completed when i click on the instance, the flow trace is not being seen..instead i see this error message...
Caused by: weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
I tried increasing the value of Maximum Message Size in the weblogic admin console by going to Servers >> MyServer >> Protocols >> General tab >> Max Message Size
I kept the value to 100000000, but even though i am still facing the same error...
we are soa suite 11G, weblogic 10.3.4, please provide a solution for this....
Thanks,
Nareshwe changed it for the admin server as well as the soa server....we kept the value to be 50000000...
we also passed the argument in the server start subtab looking at the metalink document ID 1352342.1
-Dweblogic.MaxMessageSize=50000000
we passed this argument for both the admin server and the soa server....but still after the process is completed, i am still getting the same error...
its still showing the same error with the same number...
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
please help... -
Weblogic.socket.MaxMessageSizeExceededException from T3S in SSLFIlter
We are seeing stack traces that complain about 10MB message sizes on the
T3S protocol stream. These stack traces go to standard out and are not
recorded in the Weblogics Server all.log and they are not time stamped.
Is this a bug in the native code of the socket muxer perhaps ?
We are running WL 6.1 sp1 with Oracle 8i using the thin Oracle 8.1.7
driver all running in a Sun 1.3.1_02 JVM on Red Hat Linux release 6.2
(Zoot). We do send a lot of JMS messages between the client and the
server over T3S, most of these messages are pretty small ( <100 bytes ).
Any ideas or help or patches appreciated, thanks.
weblogic.socket.MaxMessageSizeExceededException: [Incoming message of
size 10000022 bytes exceeds the configured maximum of 10000000 bytes for
T3S protocol]
at
weblogic.socket.SSLFilter.incrementBufferOffset(SSLFilter.java:160)
at
weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:528)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:446)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:378)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Tim Farrell Laurel Networks, IncDo contact customer support.
Meanwhile tune up your "MaxT3MessageSize" setting on your server
to 2000000000 (the max value) - which should defer the problem
by a factor of 200. Or give https a shot instead (this is of course slower).
Timothy Farrell wrote:
We are seeing stack traces that complain about 10MB message sizes on the
T3S protocol stream. These stack traces go to standard out and are not
recorded in the Weblogics Server all.log and they are not time stamped.
Is this a bug in the native code of the socket muxer perhaps ?
We are running WL 6.1 sp1 with Oracle 8i using the thin Oracle 8.1.7
driver all running in a Sun 1.3.1_02 JVM on Red Hat Linux release 6.2
(Zoot). We do send a lot of JMS messages between the client and the
server over T3S, most of these messages are pretty small ( <100 bytes ).
Any ideas or help or patches appreciated, thanks.
weblogic.socket.MaxMessageSizeExceededException: [Incoming message of
size 10000022 bytes exceeds the configured maximum of 10000000 bytes for
T3S protocol]
at
weblogic.socket.SSLFilter.incrementBufferOffset(SSLFilter.java:160)
at
weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:528)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:446)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:378)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Tim Farrell Laurel Networks, Inc -
While trying to publish mesaage by MQ 5.3 .I got the following error
Please help.
<Error> <HTTP> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff
3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Can you help me ? I have the same problem.
-
Weblogic.socket.PosixSocketMuxer.poll() take 25% of CPU into jvisualvm
Hello,
I'm running a bench of my software and I reach the CPU limit of my 2 application servers. When I'm looking for what method is the most consuming using jvisualvm sampler plugin, I can see the
weblogic.socket.PosixSocketMuxer.poll() method take 25% of CPU.
I used to run some benches under Solaris, and I didn't see the DevPollSocketMuxer consuming like that.
And obvisouly, my servers are strong : 2 x3650M2 with 2xX5560 quad cores 2 threads (16 virtual CPU per servers)
I'm using weblogic 10.3.4.
Could you please help me to give me some investigation tracks ?
Best Regards,Something spring to my mind when reading your initial post.
"And obvisouly, my servers are strong : 2 x3650M2 with 2xX5560 quad cores 2 threads (16 virtual CPU per servers)"
How many threads of the weblogic.socket.Muxer (weblogic.socket.PosixSocketMuxer) are there?
The native I/O muxer uses its own thread pool, i.e., it uses N + 1 threads by default, where N is the number of CPUs.
When running on multi-core CPUs that use hyper threading, it has an impact on the CPU count. In most cases, it makes
sense to reduce the number of muxer threads to eliminate the double counting of CPUs caused by hyper-threading.
In your case (2xX5560 quad cores 2 threads) the number of muxer threads would be 2 * 4 * 2 + 1 = 17 threads
Too many native muxer threads can have an impact on performance and it very well could be that this is what you
are observing "and I reach the CPU limit of my 2 application servers". You can change the number of native CPU
threads by using the weblogic.SocketReaders system property and set it to 2 + 1 = 3 threads. -
Weblogic 10.3 weblogic.socket.UnrecoverableConnectException Missing in lib
Hi Weblogic Guru:
We use JMX to retrieve information from domainruntime, the code works fine if use Weblogic 9.2's libraries. However when use weblogic 10.3 libraries, it throws NoClassDefFound for weblogic.socket.UnrecoverableConnectException at the point of calling JMXConnectorFactory.connect(serviceURL, h).
We searched around using jarBrowser in weblogic 10.3 server lib dir, but could not find any jar which include that class. Any idea? Thanks.
The stack trace is like:
java.lang.NoClassDefFoundError: weblogic/socket/UnrecoverableConnectException
at weblogic.rjvm.ServerURL.<clinit>(ServerURL.java:36)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:337)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:143)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(Unknown Source)
at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
Caused by: java.lang.ClassNotFoundException: weblogic.socket.UnrecoverableConnectException
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 58 more
Regards,
Gloria
Edited by: gloriaOO on Jun 1, 2009 2:00 PMHi Gloria,
It look to be the Internal moudle are not appearing to classpath.
Try to set weblogic.jar again into pre-classpath and try to start it again.
This should help.
Regards,
kal -
I am seeing the below message in the standard output. (FYI – WebLogic 10.0.1.0 is set up on the Linux server)
<Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
Increasing the “thread-pool-percent-socket-readers” parameter in config.xml from 50 to 75 did not resolve this error. The below link talks about patch CR263825.
Is this patch applicable for WebLogic 10 ?
Weblogic Thread Management
Thank youI am seeing the below message in the standard output. (FYI – WebLogic 10.0.1.0 is set up on the Linux server)
<Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
Increasing the “thread-pool-percent-socket-readers” parameter in config.xml from 50 to 75 did not resolve this error. The below link talks about patch CR263825.
Is this patch applicable for WebLogic 10 ?
Weblogic Thread Management
Thank you -
How do you manually set the # of threads - weblogic.socket.Muxer in 8.1
We are seeing some strange behavior with an application that has 9 threads as seen in the "Monitor all Active Queues..." I'd like to try to reduce this to 5, where would I set this?
Thanks!Just Google for such things as this: http://www.directron.com/12to7.html
You can also rig things yourself if you're inclined to do so and have the ability. You can finds instuctions by doing a web search.
I made something a bit different using a +8V 0.5A voltage regulator just because I had the parts and felt like doing it. -
Lots of exclusive method time in weblogic.socket.NTSocketMuxer.getIoCompletionResult
I am having a problem where response times are very slow and gets slower as my
test proceeds. When I turn on hprof and examine exclusive method times, I see
that the following method takes the largest amount of time. Ideas to why this
is? I've also included the hprof file(summary and some example traces only). Thanks
in advance
[java.hprof]I am having a problem where response times are very slow and gets slower as my
test proceeds. When I turn on hprof and examine exclusive method times, I see
that the following method takes the largest amount of time. Ideas to why this
is? I've also included the hprof file(summary and some example traces only). Thanks
in advance
[java.hprof] -
MaxMessageSizeExceededException in weblogic how to solve
How to solve this Exception. When is sent more than 8000 bytes of data
in the request weblogic 5.1 in solaris server gives me this error. But
the same server and same configuration in Window NT with same
SSLClient program does not give any expection even if i send 60000
bytes in the request.
Exception got in the weblogic server 5.1 in solaris server
weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
request headers of size 8320 bytes exceeds the configured maximum of
8192 bytes]
at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
SSLClient Program used: JSSE 1.0.2 package is used for SSL
import java.io.*;
import javax.net.ssl.*;
import java.net.*;
import com.sun.net.ssl.*;
import java.security.KeyStore;
public class SSLClient {
public SSLClientCheck()
System.out.println(" SSLClient is instantiated ...");
public String getSSLConnection(String host,String port,String
keystorepwd,String truststorepwd,
String keystorepath,String truststorepath,String
filepath,String parName,String message)throws Exception
String output = "";
int iport = Integer.parseInt(port);
SSLSocketFactory factory = null;
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
KeyStore ks2;
TrustManagerFactory tmf;
char[] storepass = keystorepwd.toCharArray();
char[] truststorepass = truststorepwd.toCharArray();
ctx = SSLContext.getInstance("SSLv3");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(keystorepath), storepass);
kmf.init(ks, storepass);
tmf = TrustManagerFactory.getInstance("SunX509");
ks2 = KeyStore.getInstance("JKS");
ks2.load(new FileInputStream(truststorepath), truststorepass);
tmf.init(ks2);
ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
factory = ctx.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream())));
out.println("GET " +
filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println("SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine ;
while ((inputLine = in.readLine()) != null){
output = output+inputLine;
//System.out.println(inputLine);
in.close();
out.close();
socket.close();
return output;
public static void main(String args[])
String host = "host name";
String port="7001";
String keystorepwd="cqrcqr";
String keystorepwd="changeit";
String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
String truststorepath="d:/jdk1.3/jre/security/cacerts";
String filepath="/servlets/SSLDemo";
String parName="xml_message";
String message="xml message";// of size more than 9000 bytes
try{
SSLClient ssl = new SSLClient();
String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
System.out.println(output);
catch(Exception e)
e.printStackTrace();Hello
I had taken a crack at this before but never got a response --
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.security&item=6948&utag=
Can you look at my old post and see if that helps at all? Please let me know
Joe Jerry
"[email protected]" wrote:
How to solve this Exception. When is sent more than 8000 bytes of data
in the request weblogic 5.1 in solaris server gives me this error. But
the same server and same configuration in Window NT with same
SSLClient program does not give any expection even if i send 60000
bytes in the request.
Exception got in the weblogic server 5.1 in solaris server
weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
request headers of size 8320 bytes exceeds the configured maximum of
8192 bytes]
at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
SSLClient Program used: JSSE 1.0.2 package is used for SSL
import java.io.*;
import javax.net.ssl.*;
import java.net.*;
import com.sun.net.ssl.*;
import java.security.KeyStore;
public class SSLClient {
public SSLClientCheck()
System.out.println(" SSLClient is instantiated ...");
public String getSSLConnection(String host,String port,String
keystorepwd,String truststorepwd,
String keystorepath,String truststorepath,String
filepath,String parName,String message)throws Exception
String output = "";
int iport = Integer.parseInt(port);
SSLSocketFactory factory = null;
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
KeyStore ks2;
TrustManagerFactory tmf;
char[] storepass = keystorepwd.toCharArray();
char[] truststorepass = truststorepwd.toCharArray();
ctx = SSLContext.getInstance("SSLv3");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(keystorepath), storepass);
kmf.init(ks, storepass);
tmf = TrustManagerFactory.getInstance("SunX509");
ks2 = KeyStore.getInstance("JKS");
ks2.load(new FileInputStream(truststorepath), truststorepass);
tmf.init(ks2);
ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
factory = ctx.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream())));
out.println("GET " +
filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println("SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine ;
while ((inputLine = in.readLine()) != null){
output = output+inputLine;
//System.out.println(inputLine);
in.close();
out.close();
socket.close();
return output;
public static void main(String args[])
String host = "host name";
String port="7001";
String keystorepwd="cqrcqr";
String keystorepwd="changeit";
String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
String truststorepath="d:/jdk1.3/jre/security/cacerts";
String filepath="/servlets/SSLDemo";
String parName="xml_message";
String message="xml message";// of size more than 9000 bytes
try{
SSLClient ssl = new SSLClient();
String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
System.out.println(output);
catch(Exception e)
e.printStackTrace(); -
Problem in SSL programation client in Weblogic 5.1 using JSSE
How to solve this Exception. When I sent more than 8000 bytes of data in the request weblogic 5.1 in solaris server gives me this error. But the same server and same configuration in Window NT with same SSLClient program does not give any expection even if i send 60000 bytes in the request.
SSLClient Program used given below. How to solve this problem. Any server setting is required.
Exception got in the weblogic server 5.1 in solaris server
weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP request headers of size 8320 bytes exceeds the configured maximum of 8192 bytes]
at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
SSLClient Program used: JSSE 1.0.2 package is used for SSL
import java.io.*;
import javax.net.ssl.*;
import java.net.*;
import com.sun.net.ssl.*;
import java.security.KeyStore;
public class SSLClient {
public SSLClientCheck()
System.out.println(" SSLClient is instantiated ...");
public String getSSLConnection(String host,String port,String keystorepwd,String truststorepwd,
String keystorepath,String truststorepath,String filepath,String parName,String message)throws Exception
String output = "";
int iport = Integer.parseInt(port);
SSLSocketFactory factory = null;
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
KeyStore ks2;
TrustManagerFactory tmf;
char[] storepass = keystorepwd.toCharArray();
char[] truststorepass = truststorepwd.toCharArray();
ctx = SSLContext.getInstance("SSLv3");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(keystorepath), storepass);
kmf.init(ks, storepass);
tmf = TrustManagerFactory.getInstance("SunX509");
ks2 = KeyStore.getInstance("JKS");
ks2.load(new FileInputStream(truststorepath), truststorepass);
tmf.init(ks2);
ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
factory = ctx.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream())));
out.println("GET " + filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println("SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine ;
while ((inputLine = in.readLine()) != null){
output = output+inputLine;
//System.out.println(inputLine);
in.close();
out.close();
socket.close();
return output;
public static void main(String args[])
String host = "host name";
String port="7001";
String keystorepwd="cqrcqr";
String keystorepwd="changeit";
String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
String truststorepath="d:/jdk1.3/jre/security/cacerts";
String filepath="/servlets/SSLDemo";
String parName="xml_message";
String message="xml message";// of size more than 9000 bytes
try{
SSLClient ssl = new SSLClient();
String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
System.out.println(output);
catch(Exception e)
e.printStackTrace();
}Maybe you should consider upgrading your Weblogic to a newer one. It might resolve the issue.
-
MaxMessageSizeExceededException any thing related preformace setting
How to solve this Exception. When is sent more than 8000 bytes of data
in the request weblogic 5.1 in solaris server gives me this error. But
the same server and same configuration in Window NT with same
SSLClient program does not give any expection even if i send 60000
bytes in the request.
Exception got in the weblogic server 5.1 in solaris server
weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
request headers of size 8320 bytes exceeds the configured maximum of
8192 bytes]
at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
SSLClient Program used: JSSE 1.0.2 package is used for SSL
import java.io.*;
import javax.net.ssl.*;
import java.net.*;
import com.sun.net.ssl.*;
import java.security.KeyStore;
public class SSLClient {
public SSLClientCheck()
System.out.println(" SSLClient is instantiated ...");
public String getSSLConnection(String host,String port,String
keystorepwd,String truststorepwd,
String keystorepath,String truststorepath,String
filepath,String parName,String message)throws Exception
String output = "";
int iport = Integer.parseInt(port);
SSLSocketFactory factory = null;
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
KeyStore ks2;
TrustManagerFactory tmf;
char[] storepass = keystorepwd.toCharArray();
char[] truststorepass = truststorepwd.toCharArray();
ctx = SSLContext.getInstance("SSLv3");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(keystorepath), storepass);
kmf.init(ks, storepass);
tmf = TrustManagerFactory.getInstance("SunX509");
ks2 = KeyStore.getInstance("JKS");
ks2.load(new FileInputStream(truststorepath), truststorepass);
tmf.init(ks2);
ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
factory = ctx.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream())));
out.println("GET " +
filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println("SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine ;
while ((inputLine = in.readLine()) != null){
output = output+inputLine;
//System.out.println(inputLine);
in.close();
out.close();
socket.close();
return output;
public static void main(String args[])
String host = "host name";
String port="7001";
String keystorepwd="cqrcqr";
String keystorepwd="changeit";
String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
String truststorepath="d:/jdk1.3/jre/security/cacerts";
String filepath="/servlets/SSLDemo";
String parName="xml_message";
String message="xml message";// of size more than 9000 bytes
try{
SSLClient ssl = new SSLClient();
String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
System.out.println(output);
catch(Exception e)
e.printStackTrace();Try to increase weblogic.httpd.maxHttpHeaderSize and/or weblogic.httpd.maxHttpHeaderSize
[email protected] <[email protected]> wrote:
How to solve this Exception. When is sent more than 8000 bytes of data
in the request weblogic 5.1 in solaris server gives me this error. But
the same server and same configuration in Window NT with same
SSLClient program does not give any expection even if i send 60000
bytes in the request.
Exception got in the weblogic server 5.1 in solaris server
weblogic.socket.MaxMessageSizeExceededException: [Incoming HTTP
request headers of size 8320 bytes exceeds the configured maximum of
8192 bytes]
at weblogic.socket.MuxableSocketHTTP.incrementBufferOffset(MuxableSocketHTTP.java:111)
at weblogic.socket.SSLFilter.isMessageComplete(SSLFilter.java:195)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:361)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
SSLClient Program used: JSSE 1.0.2 package is used for SSL
import java.io.*;
import javax.net.ssl.*;
import java.net.*;
import com.sun.net.ssl.*;
import java.security.KeyStore;
public class SSLClient {
public SSLClientCheck()
System.out.println(" SSLClient is instantiated ...");
public String getSSLConnection(String host,String port,String
keystorepwd,String truststorepwd,
String keystorepath,String truststorepath,String
filepath,String parName,String message)throws Exception
String output = "";
int iport = Integer.parseInt(port);
SSLSocketFactory factory = null;
SSLContext ctx;
KeyManagerFactory kmf;
KeyStore ks;
KeyStore ks2;
TrustManagerFactory tmf;
char[] storepass = keystorepwd.toCharArray();
char[] truststorepass = truststorepwd.toCharArray();
ctx = SSLContext.getInstance("SSLv3");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(keystorepath), storepass);
kmf.init(ks, storepass);
tmf = TrustManagerFactory.getInstance("SunX509");
ks2 = KeyStore.getInstance("JKS");
ks2.load(new FileInputStream(truststorepath), truststorepass);
tmf.init(ks2);
ctx.init(kmf.getKeyManagers(),tmf.getTrustManagers(), null);
factory = ctx.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.createSocket(host,iport);
socket.startHandshake();
PrintWriter out = new PrintWriter(
new BufferedWriter(
new OutputStreamWriter(
socket.getOutputStream())));
out.println("GET " +
filepath+"?"+parName+"="+URLEncoder.encode(message) + " HTTP/1.0");
out.println();
out.flush();
if (out.checkError())
System.out.println("SSLSocketClient: java.io.PrintWriter error");
/* read response */
BufferedReader in = new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
String inputLine ;
while ((inputLine = in.readLine()) != null){
output = output+inputLine;
//System.out.println(inputLine);
in.close();
out.close();
socket.close();
return output;
public static void main(String args[])
String host = "host name";
String port="7001";
String keystorepwd="cqrcqr";
String keystorepwd="changeit";
String keystorepath ="d:/weblogic/myserver/certificate/cqrstore";
String truststorepath="d:/jdk1.3/jre/security/cacerts";
String filepath="/servlets/SSLDemo";
String parName="xml_message";
String message="xml message";// of size more than 9000 bytes
try{
SSLClient ssl = new SSLClient();
String output = ssl.getSSLConnection(host,port,keystorepwd,keystorepwd,keystorepath,truststorepath,filepath,parName,message);
System.out.println(output);
catch(Exception e)
e.printStackTrace();
Dimitri -
MaxMessageSizeExceededException
Hi all,
Was wondering if anyone has encountered this error before on the
Administration Server. I am using Weblogic 7.0.4
In my environment I have an admin server on 10.122.10.162 and a managed
server on 10.122.10.105. I subjected my application to a load of 75
concurrent threads running over 3 physical machines and left it to run for 6
hours over the night. Came back the next morning and the application
wouldn't work anymore and I get this exception on the Admin Server.
Here's the full exception.
<Feb 14, 2004 12:03:53 AM SGT> <Error> <socket> <000413> <Failure in
processSock
ets() - GetData: weblogic.socket.NTSocketMuxer$GetData - Pointer:
'330870792', n
umBytes: '4096'
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size:
'100
00080' bytes exceeds the configured maximum of: '10000000' bytes for
protocol: '
t3'
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size:
'1000
0080' bytes exceeds the configured maximum of: '10000000' bytes for
protocol: 't
3'
at
weblogic.rjvm.t3.T3JVMConnection.incrementBufferOffset(T3JVMConnectio
n.java:676)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:617)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
Any help here would be greatly appreciated.
Best rgds,
Steven
the value for MaxMessageSize attribute can be set on the ServerMBean
(<Server /> tag in config.xml) so you can set it to a value upto a max of
2000000000
"Steven" <[email protected]> wrote in message
news:[email protected]...
> Hi all,
>
> Was wondering if anyone has encountered this error before on the
> Administration Server. I am using Weblogic 7.0.4
>
> In my environment I have an admin server on 10.122.10.162 and a managed
> server on 10.122.10.105. I subjected my application to a load of 75
> concurrent threads running over 3 physical machines and left it to run for
6
> hours over the night. Came back the next morning and the application
> wouldn't work anymore and I get this exception on the Admin Server.
>
> Here's the full exception.
>
> <Feb 14, 2004 12:03:53 AM SGT> <Error> <socket> <000413> <Failure in
> processSock
> ets() - GetData: weblogic.socket.NTSocketMuxer$GetData - Pointer:
> '330870792', n
> umBytes: '4096'
> weblogic.socket.MaxMessageSizeExceededException: Incoming message of
size:
> '100
> 00080' bytes exceeds the configured maximum of: '10000000' bytes for
> protocol: '
> t3'
> weblogic.socket.MaxMessageSizeExceededException: Incoming message of size:
> '1000
> 0080' bytes exceeds the configured maximum of: '10000000' bytes for
> protocol: 't
> 3'
> at
> weblogic.rjvm.t3.T3JVMConnection.incrementBufferOffset(T3JVMConnectio
> n.java:676)
> at
> weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:617)
> at
> weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
> 23)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
>
> Any help here would be greatly appreciated.
>
> Best rgds,
> Steven
>
>
-
Always get MaxMessageSizeExceededException on large number of MBeans
I have 60 apps deployed on my Cluster (with 2 ManagedServers), and each App has a large number of MBeans. If I go to the custom tree using wlst, I always get this error, even though the MaxMessageSize has been set way way higher.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
The ManagedServers are started with the ClusterManager, and each ManagedServer has the Arguments set for ServerStart:
-Xms4g -Xmx8g -XX:MaxPermSize=7g -d64 -XX:+UseCodeCacheFlushing -XX:NewSizeThreadIncrease=100 -Dweblogic.ThreadPoolPercentSocketReaders=50 -Dweblogic.ThreadPoolSize=100 -Dweblogic.SelfTuningThreadPoolSizeMin=1000 -Dweblogic.MaxMessageSize=20971520 -Djava.library.path=/install/Middleware/wlserver_10.3/server/native/linux/x86_64
The AdminServer has been set with a similar MaxMessageSize, and the wlst from where I issue the custom() command, has been started with "-Dweblogic.MaxMessageSize=20971520" too.
To top it off, I checked the JVM's with jinfo to double check the weblogic.MaxMessageSize, and all do comply to the specified bytes, none being 10M of the error message.
I am able to reproduce the issue on Linux x64 as well as Solaris 11 Sparc.
Could it be related to the MBeans (as I assume)? When I only deploy 55 apps, the issue does not occur. Any other tips are welcome.Here WLST would be acting as the client. It seems that you have placed the setting of the message max size on the server side (which is one part of the tuning), but you need to place the same to the WLST too or for that matter any other client like applet, stand-alone java code.
In short you can try the following, if you wish:
set the environment using setDomainEnv.sh/cmd and the run:
java -Dweblogic.MaxMessageSize=20971520 weblogic.WLST
Note: I read through your note about providing "-Dweblogic.MaxMessageSize=20971520" parameter to WLST, but not sure whether you have checked WLST process with jinfo or the WLS server nodes.
Also I am not sure what type of application you are using by you can consider passing the above property via System.property() call to the application.
Additionally, I would request you to share some more information, like the config (snippet), jinfo output, and WLST output if you try to locate the current MaxMessageSize value of the server by connecting to it, complete stack (if any).. in case the above does not help.
Note: I have tried this multiple times and it works like a charm. But from your notes it seems to a case of overridding of parameters value.
HTH,
AJ
Maybe you are looking for
-
How do I control the order of all day events in iCal?
How do I control the order of all day events in iCal? Even if I painstakingly try to re-order the events the way I want them, when they print, they are in a different order. I have searched other forums and no one seems to have an answer to this. H
-
Can no longer open BOTH DVD drives after upgrade
OK...I have a Mac Pro, and pre Lion I had NO PROBLEM using F12 and opt-F12 to open both of my Superdrive trays. However, after Lion, F12 AND opt-F12 BOTH OPEN THE BOTTOM SUPERDRIVE ONLY, and I cannot access my upper superdrive. Am I missing some sort
-
Display Row Level Data in Title UDF
Hi, The requirement is in SAP 8.8 PL 15. I have created an UDF in Marketing Documents - Title and would like to display the Location Code from the Rows (1st row) in that UDF using FMS. I have a query that is: select $[$38.2000002049.1] But it gives t
-
Can I clear my repair and any past cases history in my Apple Support Profile?
Pretty much as the head line says, you know that when you schedule a repair or open a selfsolve case it all gets to stay in there as a history in your apple support profile, and I'm wondering what If I would like to clean it? I want to give my profil
-
I have just downloaded Creative cloud and am trying to install on my 2010 MacBook Pro with OS 10.9.3 When I install I am not getting the signon button, just a blue spinning. I saw the signon button blip by once but then it went right to the spinning.