Skip to Content
0
Former Member
Mar 27, 2009 at 08:15 AM

2 netweaver and b2b shops block each other.

21 Views

hi,

We have a CRM4 Environment in our company and want to change from 32-bit Windows 2000 to 64-bit Windows 2003. So we set up a new server and installed netweaver, trex and deployed our b2b shop.

The Windows 2000 Server runs productive. After deploying the b2b shop neither the old not the new b2b shop worked. I just got a white screen in the browser after accepting the ssl connection in both shops.

So i stopped the new J2EE Server (which is Netweaver 640) and the old one ran perfectly.

Both servers are connected to the CRM system.

I checked the default traced from both servers and this is what i got:

Old Server (Windows 2000):

com.sap.engine.frame.cluster.ClusterException: Invalid wait on message server connect.

Cannot update HTTP load balancing information in the Message service

com.sap.engine.frame.cluster.ClusterException: Socket closed

at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1396)

at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)

at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)

at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)

at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:860)

at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:806)

at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:407)

at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

Caused by: java.net.SocketException: Socket closed

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)

at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)

at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)

at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)

at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)

at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)

at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1393)

... 10 more

So there are many lines that say about cluster problems. This isn´t a cluster and is not configurated as cluster. I don´t even know if this log entrys refer to the current problems we had.

Where could the problem be? We did the same procedure with our Consolidation environment and it was no problem to run two b2b shops simultaneously. The imsdefault connection is set to the productive b2b shop. So i don´t understand why the one b2b shop takes down another b2b shop. They refer to the same IPC server and the same TREX.

Hope someone can help me with this exceptional problem.