环境搭建中遇到的问题

1.

Well i also encountered the same problem when posting a message on to the JMS queue This queue is deployed on a managed server on weblogic 8.1

the actual problem here is if you give the Listen Address (The IP address or DNS name this server uses to listen for incoming connections) under myserver----> Configuration---->general---->Listen Address: TAB if there is a DNS Name entered here then you will encounter this problem

please clear this text box and your problem would be resolved ......

2.

或者参考这个:

点击打开链接

3.

Applies to:

Oracle Weblogic Server – Version: 7.0 to 10.3
Information in this document applies to any platform.
Symptoms

Using t3 or t3s to connect to WebLogic Server (WLS) via load balancer or proxy, the following exception is seen on the server side:
####<15-Jun-2009 17:16:42 o'clock BST> <Error> <RJVM> <testing.oracle.com> <ms2> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1245082602025>
<BEA-000572> <The server rejected a connection attempt JVMMessage from:
'1055943816590585412C:10.167.241.160R:-5807491384061495016S:10.167.241.160:SR7586539.992:ms2' to: '0B:10.167.241.160:[-1,-1,-1,443,-1,-1,-1]' cmd:
'CMD_IDENTIFY_REQUEST', QOS: '102', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x1', abbrev offset: '106' probably due to an incorrect firewall configuration or admin command.>

There is usually also an exception on the client side. For instance, when using JMS, there is a javax.naming.CommunicationException seen:
<16-Jun-2009 08:24:55 o'clock BST> <Error> <RJVM> <BEA-000515> <execute failed
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '0'
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '0'
at weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:380)
at weblogic.rjvm.http.HTTPClientJVMConnection.run(HTTPClientJVMConnection.java:255)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
Exception in thread "main" javax.naming.CommunicationException [Root exception is java.net.ConnectException: https://XX.XXX.XXX.XXX:443: Bootstrap to testing.oracle.com/10.167.241.160:443 failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
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(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at QueueSend.getInitialContext(QueueSend.java:117)
at QueueSend.main(QueueSend.java:81)
Caused by: java.net.ConnectException: https://XX.XXX.XXX.XXX:443: Bootstrap to testing.oracle.com/XX.XXX.XXX.XXX:443 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
... 9 more
Caused by: java.rmi.ConnectException: Bootstrap to testing.oracle.com/XX.XXX.XXX.XXX:443 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:328)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
... 11 more

Cause

If the Load Balancer/proxy port is not the same as the WLS port, WLS throws an exception rejecting the connection attempt during bootstrapping, saying that the ports don’t match (portMatches = false). To fix this, either the WLS port has to match the Load Balancer/proxy port or the switch -Dweblogic.rjvm.enableprotocolswitch=true needs to be enabled. If the switch is enabled, it avoids throwing the exception in the bootstrapping case by setting the portMatches variable to true.
Solution

Enable the switch -Dweblogic.rjvm.enableprotocolswitch=true as an argument to the JVM on startup on all the managed servers within the cluster.