SAP XI Seeburger and X.400 Adpater

[Former Member]

Hello,

We are trying to implement Seeburger X.400 Adapter in our XI 3.0 landscape for the first time.

I went through Seeburgers config documentation and did all the setup and still getting errors. Not sure what I missed.

At the log it seems to be complaining about "Resource". I did create a logical resource and assigned it to the channels.

Following error is what I see in Comm.Channel Monitoring for both Sender and Receiver Channels:

2009/04/21 - 14:45:34:368 Retryable fault in 'Channel:CC_NL_Receiver_Test'. Description: P7 error occured! Details: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:44 PM]
Error type: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. >> Error date: 4/21/09 2:45 PM >> Description: : trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:45 PM]

Following is the error log I see in the log files (seeburger-x400p7-readable.2.trc):

Apr 21, 2009 3:21:47 PM    com.seeburger.p7.statemachine.TransportLayer.disconnect()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Error while disconnecting! The transport layer is not connected.
Apr 21, 2009 3:21:47 PM    com.seeburger.p7.MessageStore.bind()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Failed to establish a connection. Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
	at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
	at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
	at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
	at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
	at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
	at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
	at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
	at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
	at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
	at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
	at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
	at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
	at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Apr 21, 2009 3:21:47 PM    com.seeburger.p7.P7Processor.handleP7Exception()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isnt connected yet. Caused by: com.seeburger.p7.exceptions.P7Exception: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
	at com.seeburger.p7.MessageStore.bind(MessageStore.java:379)
	at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
	at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
	at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
	at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
	at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
	at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
	at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
	at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
	at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
	at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
	at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
	at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
	at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
	at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
	... 11 more

Apr 21, 2009 3:21:47 PM    com.seeburger.xi.connector.fw.XICommunicator.reservationReleased(String)                                                                               [SAPEngine_Application_Thread[impl:3]_27] # Error # Error while releasing resource in resource-management:Cannot create reservation, reason: Cannot find reservation with id X400-Seeburger49; affected object : null

Thanks in advance for your help,

Sumant.

[prateek]

In the Seeburger worbench -> Resource Management -> Reservation, make sure that you have an entry for X400 adapter. Now have a look at the Reservation time available there. If that is too old, then delete and recreate the entry. If that is current time, then restarting the message should work.

Regards,

Prateek

[Former Member]

Hi Prateek,

Thanks for your quick response.

As you said, there was a reservation entry and I deleted it. But still having the same issue.

Do you know what this error means. I see this in the comm.channel monitor:

Alert: Polling failed, caused by: Task final state is RETRY or ERROR [4/21/09 3:45 PM]

2009/04/21 - 15:45:16:341 Retryable fault in 'Channel:CC_PollingX400'. 
Description: P7 error occured!  Details: 
trying to open a connection --> 
connecting to remote session service --> 
com.seeburger.p7.exceptions.P7ConnectException: writing to network --> 
The transport layer isn't connected yet. [4/21/09 3:44 PM]

Error type: 
trying to open a connection --> 
connecting to remote session service --> 
com.seeburger.p7.exceptions.P7ConnectException: writing to network --> 
The transport layer isn't connected yet. 
>> Error date: 4/21/09 3:45 PM 
>> Description: : trying to open a connection --> 
connecting to remote session service --> 
com.seeburger.p7.exceptions.P7ConnectException: writing to network --> 
The transport layer isn't connected yet. [4/21/09 3:45 PM]

Regards,

Sumant.

[prateek]

Have you recreated the reservation? Make sure that the name given in Seeburger workbench and in the communication channel are exactly identical. It is case sensitive. Also make sure that for each mailbox, you have only one such Reource name.

Regards,

Prateek

[Former Member]

This error is very likely not caused by a problem with resource management - instead check the SSL certificate - i figure you are using TCP/IP based connection ? Which VAN are you connecting to ? Very likely a SSL connection is required which is to be configured in the comm. channel !

[Former Member]

Hi,

Thanks for your responses.

I fixed the problem. It was to do with the X400 mail parameters. One of the parameters had a typo error.

When corrected this, connections started to work.

Regards,

Sumant.