"Channel started but inactive" in RWB Monitor for SOAP sender channel

Dear XI specialists,
I have configured a communication scenario involving SOAP Adapter (sender) usage, but I'm facing the issue when testing the scenario. The problem is that none of messages are coming into the SOAP Adapter (checked via TCode SXI_MONITOR in XI) when using 3rd party SOAP-clients (XML Spy, soapUI) based on WSDL-file generated and exported from XI.
I checked the sender communication channel for SOAP Adapter - it is activated in Integration Builder's Directory. SOAP Adapter itself is also started.
I checked Runtime Workbench monitors and in the Communication Channels Monitor of the Components Monitor received the warning saying "Channel started but inactive" for my configured channel as well as for other channels working on SOAP Adapter.
Activities which were performed (in the order in which they were performed and results tested):
1. the configuration channel restart;
2. the communication channel re-activation and further re-start;
3. SOAP Adapter restart;
4. XI system's Java instance restart.
All mentioned activities didn't give any positive effect in part of this issue resolution.
On the other hand, if I use test message functionality of the Runtime Workbench (Component Monitor), then messages are seen in SXI_MONITOR and expected response messages are also returned to XI from integrated business system.
Would you please advise what can be checked else here and where the root of the problem may be detected?
All your answers and feedback will be greatly appreciated and awarded accordingly.
Many thanks in advance and my regards,
Vadim

Dear all,
Thank you for your input! Unfortunately, the problem still exists after testings and checkings which you suggested.
TO Seshagiri:
I checked message monitor and found only several messages for the required sender/receiver services pair in the used namespace - all of them were successfully processed (these are messages which I sent by means of RWB Component Monitor's test message functionality).
TO Sarvesh:
Yes, sender agreement is configured properly. I configured it when configuring communication scenario in the Configuration Wizard and then manually re-checked its definition. Moreover, when performing Test Configuration in ID, I received positive results.
TO Nallam Guna:
I cleared Data Cache in Integration Builder, but this didn't help.
TO Gujjeti:
I'm on SAP NetWeaver 2004s PI 7.0. Service Pack level for PI is 13.
TO Durga:
Thank you for provided links! I have already had a look at them - but proposed solutions doesn't seem to be working in my situation.
Thank you all once again for your prompt answers! I really appreciate your attempts in helping me!
I would appreciate if you could share any further ideas on this issue.
My best regards,
Vadim

Similar Messages

Yellow LED: Channel started but inactive from CC monitoring

Hi
We are trying SOAP to SOAP scenario, we done with all IR and ID part deployment and Activated the all the Objects ,
But still In CC monitoring both channels showing Yellow LED: Channel started but inactive
In omponent Monitoring Adapter Engine also showing Yellow LED
We tried with SXI_CACHE and CAP cache refresh also...
Help me out to solving this issue..
Thanks
Vadde

Hi Vishwanadh,
We have faced the same issue for the past two days and the sam has got resolved automatically while testing the scenario. So please go ahead with your testing, the channel will then be activated automatically.
Before that clear the CPAcache with the user PIISUSER (make sure that the user is having access to SAP_XI_Administrator_J2EE and SAP_XI_Configuratoe_J2EE
Regards,
Varadhu

RWB issue Channel started but inactive

Hi,
In RWB the SOAP adapter is showing status message as"Channel started but inactive" but all the SOAP adapters are active in Directory.
This is happening only in new environment Pre-Production.
Valueable inputs will be appreciated.
Thanks
Santosh

Hi Santosh,
SOAP adapter shows "Channel started but inactive" message when there are no messages processed till now(after activating any changes to comm channel or server is restarted). Once a message is triggered in SOAP adapter, this will go away. Try to trigger a message and see.
Regards,
Sreenivas

"Channel started but Inactive" - Issue with JDBC channels

Hi all,
I have 5 channels configured with Oracle which were functioning till yesterday night properly. All of a sudden 3 out of them have decided not to co-operate and they show a status in RWB as "Channel started but Inactive".
The rest two are functioning correctly which is more weird.
I did the following:
1. Complete cache refresh.
2. Delta cache refresh
3. channel was copied with a new name and used and it works but this doesnt make any sense.There has to be a proper way to deal with this situation.
4. All channels are activated in ID.
Has anybody faced similar issues with JDBC or any other type channels?
Regards,
Amol Joshi

Hi Amol,
Usually the channel information is available in the monitor after the service and the channel are activated successfully.
However, in the case of the SOAP adapter, the
adapter status is not available until the first request is sent to the adapter.
For JDBC Adapter try to:
1. Re-configure JDBC parameters, it might happened that it is not able to establish a database connection.
Just re-enter and activate the same.
2.goto to the IR adn ID and run the cache ,you will get the cache objects list in red color check the error details there, make sure the AE cache is up and running fine.
goto to the RWB>cache monitoring or status->check the cache status of the AE and IS, it should be green in color,
run the CPA cache from the URL with the PIDIRUSER ...then again run the cache from IR and ID and check.
Also check :
1.if you have right permission to write the data to the table
2. Check whether that table takes NULL values, if so check what data is being supplied by XI to the receiver end.
*Pls: Reward points if helpful*
Regards,
Jyoti

What happens if Channel started but inactive?

Hi.
While monitoring the training server, i found there are 100 channels with yellow color status "Channel started but inactive".
All these channels are not SOAP or MAIL channels. Most are FILE, JDBC, JMS channels.
I know that we can stop the channels in RWB but what happens if these channels are kept with that yellow status? If i stop these channels will it improve the performance??
Kindly let me know how it will effect the performance.
Thanks... !
Warm regards,
Praveen.

Hi,
While monitoring the training server, i found there are 100 channels with yellow color status "Channel started but inactive". - It means there was no msg for these channels so they are inactive......when there will be msgs for these channels, then those msgs will be processed by these channels and its status will change to running........
I know that we can stop the channels in RWB but what happens if these channels are kept with that yellow status? - No performance impact because of this inactive channels :).............
If i stop these channels will it improve the performance?? - Do not stop these channels but keep them started..........
Regards,
Rajeev Gupta

Channel Started but inactive

hi all -
i have 2 scenarios - idoc to file which works fine without any problem
in the other scenario - file to file i get this message in the communication channel monitoring for the file sender which says "Channel started but inactive".
I checked the integration directory and made sure that its activ and the change list is activated.
I also checked the sxi_cache and the contents are upto date.
any ideas how to resolve this issue?
Thanks,
Tirumal

Hi,
Try to do the CPACache Refresh.
Also adapter metadata Refresh ( Integration Builder->Admin->Cache Overview)
Also restarting Adapter engine may also help here.
This SAP Note - 764176 (SLD inconsistence )
Regards,
Moorthy

SOAP adapter - Channel started but inactive (case inside)

Good day everyone!
I have integration scenario IDOC->XI->SOAP. I did all setting and created SOAP adapter with 2 parametrs: "Target URL" and "SOAP Action".
But when I look at Channel Monitoring I see my SOAP-channel with status "Channel started but inactive" ??
What could it be?
Thanks in advance!

hi,
this issue is too common. i face it i some of my channels. there no error.
test your scenario. im sure it will work but the adapter still has been in yellow at least it fails and turn red.
I have some CC in red status and working fine. later few minutes it turn green.
don worry about it. if you leave it working it will turn green later. if u restart the java stack you can solve it but i dont recommend it because this error could appear in other adaprter too.
commonly it appear when you start and stop the channel from RWB.
Hope Helps
thanks
Rodrigo.

SOAP Adapter status stay "Channel started but inactive"

Hi, Folks:
We have a couple of SOAP adapters that I have not used for a while, so I put them in inactive status.
Now we need to switch SOAP Scenario, I activate them, however, in Communication Monitoring Page, The status is Yellow Triangle: "Channel started but inactive"
I have tried to inactivate and reactivate them for a couple of times, it does not help.
Any ideas are welcomed !
Liang

Hi Guys
As suggested by you guys, after I sent first message, all the SOAP adapter get active now. I believe I fogort how I setup it up initially. That is the value stay with your guy
Thanks everyone !
Liang
Edited by: Liang Ji on Feb 29, 2008 8:48 PM

SOAP - channel started but inactive

Hi experts..
while testing Scenario using SOAP adapter. in RWB -
> adpapter monitaring . here all the adapters in gery status , when i check in communicational chanel monitaring iam seeing error "channel started but inactive "
but i cheked all adapeters in IR ID and refreshed the cashes, and tested the proxy also evrthing is ok.
even i run the scenarion why the adpter status is not changed from yello to green?
i chek the notes 809420, 764176 but i didnt understand what is causing this issue?
note : previously all the scenarios are implemeted in SP6 , now iam working on SP16 , iam wondering in my current system all the adapters in grey color even othe scenarios excuted sucessfully also.
please suggest me ?
thanks
vasavi

Hi sheshagiri
i run the proxy iam able to see the below error in
outbound processing----
> payload after service
ADDRESSVALIDATERESPONSE>
- <RESPONSE>
- <TRANSACTIONREFERENCE>
<CUSTOMERCONTEXT>Local mode using Progistics XML Processor</CUSTOMERCONTEXT>
<XPCIVERSION>6.1.9</XPCIVERSION>
</TRANSACTIONREFERENCE>
<RESPONSESTATUSCODE>609</RESPONSESTATUSCODE>
<RESPONSESTATUSDESCRIPTION>Unable to process request</RESPONSESTATUSDESCRIPTION>
- <RESPONSEERROR>
<ERRORSEVERITY>Fatal</ERRORSEVERITY>
<ERRORCODE>2441</ERRORCODE>
<ERRORDESCRIPTION>Invalid Login ID. Verify Login ID with System Administrator. I7A9</ERRORDESCRIPTION>
<MINIMUMRETRYSECONDS>N/A</MINIMUMRETRYSECONDS>
- <ERRORLOCATION>
<ERRORLOCATIONELEMENTNAME>LOGINID/FOLDER</ERRORLOCATIONELEMENTNAME>
<ERRORLOCATIONELEMENTREFERENCE>n/a</ERRORLOCATIONELEMENTREFERENCE>
<ERRORLOCATIONATTRIBUTENAME>N/A</ERRORLOCATIONATTRIBUTENAME>
</ERRORLOCATION>
<ERRORDIGEST>N/A</ERRORDIGEST>
</RESPONSEERROR>
</RESPONSE>
</ADDRESSVALIDATERESPONSE>
please suggest me

SOAP Adapter: Channel started but inactive

Our system is XI 3.0 running on Solaris 10 zoning and Oracle 9i. All on Support Package 17.
When consulting the status of the adapter in the RWB environment we are receiving the message above "Channel started but inactive".
How can We solve this problem?

hi,
SOAP adater will be green when you process the first message via this adapter
Regards,
michal

SOAP Sender - RWB "Channel started but inactive"

I have a sender soap channel configured. In Integration Directory the Adapter Status is active. However when I go to Runtime Workbench and view the channel it says the "Channel is started but inactive". Can someone explain to me why it is not active in Runtime Workbench?
Also, SOAP messages sent to this channel are failing obviously because the channel is inactive. How can I make this channel active so that XI can receive SOAP requests.

hi rodel,
You have to process one message at least to make SOAP adapter Active
refer this discussion
how can i enable SOAP Adapter?
regards
Ramesh P

Commuication Channel monitoring for SOAP Adapter

Hi friends,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
Channel started but Inactive
What does that indicate?
Kindly update what i need to do..

Check these links :
SOAP adapter - Channel started but inactive (case inside)
SOAP Adapter status stay "Channel started but inactive"
it ll be solved by given solutions in these thread like send messages,cache refresh..

Request Response Bean for SOAP Sender Adapter

Hi Friends,
Is it possible to use Request Response Bean Module described (FIle to RFC to File here) for SOAP(sender) and JDBC(receiver) adapter?
I want to configure SOAP to JDBC to JDBC scenario.
http://wiki.sdn.sap.com/wiki/display/HOME/UsingRequestResponseBeanModuleinFILE+Adapter
Scenario:
I will do SOAP adapter call Asynchronously and JDBC receiver adapter will select data from database. This response will go back to SOAP adapter and then SOAP will divert this response to another JDBC adapter. This JDBC adapter will insert data into another database.
I do not want to use ccBPM. Is there any design approach to implement this scenario?
Thanks,
Sandeep Maurya

Hi Sandeep,
SAP says SOAP sender adapter does not support Modules. You can serch Help.sap (for SOAP sender channel) to find the same.
I would suggest to use AXIS adapter (provides all the functionality of SOAP) and supports the Modules as well.
I have used the Module beans that you mentioned in the past... but it is not consistent with its processing.. sometimes it stucks with Message ID issue... I have seen same issue faced some other friends as well .. search on SDN you will find the issue with these modules...
Using BPM would be another option...
Thanks,
Sunil Singh

How to re-use one SOAP Sender Channel for two different messages?

Hi!
I have an XI Proxy to SOAP Sync Scenario. 5 messages uses only 2 channels - cc_XI_Sender and cc_SOAP_Receiver. All messages comes from one Sender Channel and goes to one Receiver channel, and it works fine.
When I make the same for SOAP to XI Proxy Sync Scenario, I've got a problem. For example I have 2 different messages (mi_so_MSG_ONE and mi_so_MSG_TWO), so it works, if I had a two different sender channels (cc_SOAP_R1 and cc_SOAP_R2).
If I set the same Sender Channel in both Sender Agreements (cc_SOAP_R1), only one message (mi_so_MSG_ONE) goes without errors. When I send a second message (mi_so_MSG_TWO), in SXMB_MONI this message comes from Business System (BS_TEST) as message type one (mi_so_MSG_ONE), and then in stage of transformation in Interface Determination goes to message mapping program for other kind of messages (MM_MSG_ONE_to_XI_PROXY). And then - error in message mapping.
I try many URLs for both messages:
1) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=&Interface=
2) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=*
3) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=...MyNameSpace...mi_so_MSG_TWO
Message in payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<MSG_TWO xmlns="urn:xxx:yyy:MyNameSpace" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">... some fields... </MSG_TWO>
But in SOAP Header I see that is NOT second message!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
< !-- Inbound Message   -->
<SAP:Main>
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>93233F70-3E2F-11DF-8CD3-00237D301CD6</SAP:MessageId>
<SAP:TimeSent>2010-04-02T08:13:09Z</SAP:TimeSent>
<SAP:Sender>
    <SAP:Service>BS_TEST</SAP:Service>
    <SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Sender>
<SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Main>
Is it correct that many kinds of messages cannot goes through one Sender Channel ? If not... How can I reuse one SOAP Sender Channel for both this messages?
Thanks for helping.

Thanks for answers!
It means a webservice application will be deployed and exposed in PI using the associated Message Interface and its namespace information in the SOAP Sender channel.
It means only one Sender Channel per one pair of names (name of Message Interface and name of namespace). And it will fail if I change something. And question is: why URL for sending SOAP message contains parameter "Interface"?
"backward compatibility" or "for future use only"?
Nothing happens when I change this parameter, seems that name of Interface comes from first of founded Sender Agreements.
If the structures are the same
No. Structures are different.
Making one structure per all SOAP incoming messages looks workable, but... looks strange (in fact I have a lot of SOAP messages, more than 100 Sender channels).
I found an information, that I can use one Sender channel per many messages with different structures only if I make this messages like different Operations in one Service Interface (in PI 7.1).
But in this case in list of messages in SXMB_MONI I will see only a one name of Service Interface for all my messages and it's not so comfortably for supporting: to take a name of operation that fails I need to goes inside.
In older version of XI (prior 7.1) using one sender channel per many messages allowed without any hints.

HTTP Error 501 with SOAP Sender channel

Hello,
i've am simple Question:
I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
XI-Parameters:
namespace: <myInterfaceNamespace>
Interface: <myAsynchInterface>
QoS: Exactly Once in Order
Queue: MY_QUEUE
We do not care about the Response - so the processing is asynchron.
Thus my interface mapping maps to asynch interfaces. The desitnation
is an ABAP Proxy. The configuration has been done and tested.
Here my question:
according the documentation, the URL has the following syntax:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
In our case:
http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
But when i generate a WSDL for the interface out of the Configuration, the address is:
<soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&version=3.0&Sender.Service=MyService&Interface=...
and so forth.
But was is the difference between these 2 possibilities?
Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
Thanx in advance
Gunnar

Gunnar,
I will suggest you to go through it once to check all your connection.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Sarvesh

"Channel started but inactive" in RWB Monitor for SOAP sender channel

Similar Messages

Maybe you are looking for