This discussion is archived
7 Replies Latest reply: Jan 16, 2013 9:42 PM by Kishore Rout RSS

URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel

806800 Newbie
Currently Being Moderated
Hi
When I am trying ot start managed server I am getting the following error:
<Error> <WLSS.Engine> <BEA-330075> <There are no sip nor diameter channels targeted to server "core_ws_ms">

I am starting with the command below:
startManagedWebLogic.sh core_ws_ms <server>:7001
core_ws_ms is the managed server we have created using create domain wizard.

Also, what is the suggested way of starting admin and managed domains?
  • 1. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    Faisal Khan Expert
    Currently Being Moderated
    You are starting in the right way.. however issue seems to b related to SIP

    Did u look at this?

    http://download.oracle.com/docs/cd/E13209_01/wlcp/wlss21/messages/Engine.html

    EA-330075

    Error: There are no sip channels targeted to server "serverName"

    Description

    There are no sip channels targeted to server "serverName"
    Cause

    Invalid configuration
    Action

    If you intend to use this server as sip engine, please create a sip network access point and target it to server "serverName". If this server should be part of data tier servers, then make sure that this server is included in datatier.xml configuration file. Please restart the server after making necessary changes.


    -Faisal
    http://www.weblogic-wonders.com
  • 2. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    806800 Newbie
    Currently Being Moderated
    Hi THanks for the quick response.
    This is the first time we have installed weblogic and created managed domain and trying to restart.
    I saw this note but couldnt really make use of it.
    We did not specifiy any where this domain to be sip server or any thing like that.
    while creating the admin domain for the first time we have created managed domain along with it.

    Any idea how to over come above problem or where fix any parameter?
  • 3. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    Faisal Khan Expert
    Currently Being Moderated
    can you paste your config.xml here?
  • 4. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    806800 Newbie
    Currently Being Moderated
    <?xml version="1.0" encoding="UTF-8"?>
    <domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd" xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <name>ges_core_ws</name>
    <domain-version>10.3.4.0</domain-version>
    <security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml" xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">
    <name>ges_core_ws</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
    <sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    <sec:password-validator xsi:type="pas:system-password-validatorType">
    <sec:name>SystemPasswordValidator</sec:name>
    <pas:min-password-length>8</pas:min-password-length>
    <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
    </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{AES}gScrW/yCu8tIEb/H1LNPk+Usi0ntfJXvYhvX7YIcMHwbV+RzUXyncqJLD7korYD2NatSJsA8HIAgIWHWQ0cdY1AgZnGDEl53paOInrx3Ehew9yrMuQxavx2YiS4skmBV</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{AES}BaDNSPMP3n4Ux6Ajp4jip5YRaE8ptzQ6zx5UlQvMtUQ=</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <self-tuning-thread-pool-size-min>15</self-tuning-thread-pool-size-min>
    <socket-readers>2</socket-readers>
    <ssl>
    <name>AdminServer</name>
    <enabled>true</enabled>
    <listen-port>7002</listen-port>
    </ssl>
    <listen-address/>
    <network-access-point>
    <name>sip</name>
    <protocol>sip</protocol>
    <listen-port>5060</listen-port>
    <public-port>5060</public-port>
    <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
    <outbound-enabled>true</outbound-enabled>
    </network-access-point>
    <network-access-point>
    <name>sips</name>
    <protocol>sips</protocol>
    <listen-port>5061</listen-port>
    <public-port>5061</public-port>
    <http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
    <outbound-enabled>true</outbound-enabled>
    </network-access-point>
    </server>
    <server>
    <name>core_ws_ms</name>
    <listen-port>7003</listen-port>
    <listen-address/>
    <web-service>
    <name>core_ws_ms</name>
    <web-service-persistence>
    <name>core_ws_ms</name>
    <web-service-logical-store>
    <name>WseeStore</name>
    <persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
    <request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
    <response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
    </web-service-logical-store>
    </web-service-persistence>
    </web-service>
    </server>
    <embedded-ldap>
    <name>ges_core_ws</name>
    <credential-encrypted>{AES}ZsjdBOOmj+DK+EfAuJdU8FX6nWsXcz2F8PtwTermrb6EuCK7vc9IAFjXe8f9+2Ye</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.4.0</configuration-version>
    <jms-server>
    <name>WseeJmsServer</name>
    <target>core_ws_ms</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>WseeJaxwsJmsServer</name>
    <target>core_ws_ms</target>
    <persistent-store>WseeJaxwsFileStore</persistent-store>
    </jms-server>
    <self-tuning>
    <fair-share-request-class>
    <name>wlss.transport.fsrc</name>
    <target>core_ws_ms</target>
    <fair-share>50</fair-share>
    </fair-share-request-class>
    <fair-share-request-class>
    <name>wlss.timer.fsrc</name>
    <target>core_ws_ms</target>
    <fair-share>100</fair-share>
    </fair-share-request-class>
    <fair-share-request-class>
    <name>wlss.tracing.fsrc</name>
    <target>core_ws_ms</target>
    <fair-share>50</fair-share>
    </fair-share-request-class>
    <fair-share-request-class>
    <name>wlss.connect.fsrc</name>
    <target>core_ws_ms</target>
    <fair-share>1000</fair-share>
    </fair-share-request-class>
    <min-threads-constraint>
    <name>wlss.tracing.minthreads</name>
    <target>core_ws_ms</target>
    <count>1</count>
    </min-threads-constraint>
    <min-threads-constraint>
    <name>wlss.connect.minthreads</name>
    <target>core_ws_ms</target>
    <count>1</count>
    </min-threads-constraint>
    <max-threads-constraint>
    <name>wlss.timer.maxthreads</name>
    <target>core_ws_ms</target>
    <count>16</count>
    <connection-pool-name/>
    </max-threads-constraint>
    <max-threads-constraint>
    <name>wlss.tracing.maxthreads</name>
    <target>core_ws_ms</target>
    <count>1</count>
    <connection-pool-name/>
    </max-threads-constraint>
    <capacity>
    <name>wlss.transport.capacity</name>
    <target>core_ws_ms</target>
    <count>400</count>
    </capacity>
    <capacity>
    <name>wlss.timer.capacity</name>
    <target>core_ws_ms</target>
    <count>256</count>
    </capacity>
    <work-manager>
    <name>wlss.transport</name>
    <target>core_ws_ms</target>
    <fair-share-request-class>wlss.transport.fsrc</fair-share-request-class>
    <response-time-request-class xsi:nil="true"/>
    <context-request-class xsi:nil="true"/>
    <capacity>wlss.transport.capacity</capacity>
    <ignore-stuck-threads>false</ignore-stuck-threads>
    </work-manager>
    <work-manager>
    <name>wlss.timer</name>
    <target>core_ws_ms</target>
    <fair-share-request-class>wlss.timer.fsrc</fair-share-request-class>
    <response-time-request-class xsi:nil="true"/>
    <context-request-class xsi:nil="true"/>
    <max-threads-constraint>wlss.timer.maxthreads</max-threads-constraint>
    <capacity>wlss.timer.capacity</capacity>
    <ignore-stuck-threads>false</ignore-stuck-threads>
    </work-manager>
    <work-manager>
    <name>wlss.tracing.domain</name>
    <target>core_ws_ms</target>
    <fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
    <min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
    <max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
    <ignore-stuck-threads>false</ignore-stuck-threads>
    </work-manager>
    <work-manager>
    <name>wlss.tracing.local</name>
    <target>core_ws_ms</target>
    <fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
    <response-time-request-class xsi:nil="true"/>
    <context-request-class xsi:nil="true"/>
    <min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
    <max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
    <ignore-stuck-threads>false</ignore-stuck-threads>
    </work-manager>
    <work-manager>
    <name>wlss.connect</name>
    <target>core_ws_ms</target>
    <fair-share-request-class>wlss.connect.fsrc</fair-share-request-class>
    <response-time-request-class xsi:nil="true"/>
    <context-request-class xsi:nil="true"/>
    <min-threads-constraint>wlss.connect.minthreads</min-threads-constraint>
    <ignore-stuck-threads>false</ignore-stuck-threads>
    </work-manager>
    <work-manager>
    <name>weblogic.wsee.mdb.DispatchPolicy</name>
    <target>core_ws_ms</target>
    </work-manager>
    <work-manager>
    <name>weblogic.wsee.jaxws.mdb.DispatchPolicy</name>
    <target>core_ws_ms</target>
    </work-manager>
    </self-tuning>
    <file-store>
    <name>WseeFileStore</name>
    <directory>WseeFileStore</directory>
    <target>core_ws_ms</target>
    </file-store>
    <file-store>
    <name>WseeJaxwsFileStore</name>
    <directory>WseeJaxwsFileStore</directory>
    <target>core_ws_ms</target>
    </file-store>
    <file-store>
    <name>WseeFileStoreAdminServer</name>
    <directory>WseeFileStoreAdminServer</directory>
    <target>AdminServer</target>
    </file-store>
    <jms-system-resource>
    <name>WseeJmsModule</name>
    <target>core_ws_ms</target>
    <sub-deployment>
    <name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
    <target>WseeJmsServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>WseeJaxwsJmsModule</name>
    <target>core_ws_ms</target>
    <sub-deployment>
    <name>WseeJaxwsJmsServerSub</name>
    <target>WseeJaxwsJmsServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/wseejaxwsjmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <custom-resource>
    <name>sipserver</name>
    <target>core_ws_ms</target>
    <descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
    <resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
    <descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
    </custom-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <saf-agent>
    <name>ReliableWseeSAFAgent</name>
    <target>AdminServer</target>
    <store>WseeFileStoreAdminServer</store>
    </saf-agent>
    <saf-agent>
    <name>ReliableWseeJaxwsSAFAgent_core_ws_ms</name>
    <target>core_ws_ms</target>
    <store>WseeJaxwsFileStore</store>
    </saf-agent>
    </domain>
  • 5. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    806800 Newbie
    Currently Being Moderated
    I selected sip servers in the left hand side -> Targets -> removed core_ws_ms from SIP Server Targets, then it got started.
    Not sure it would impact any where else though...
  • 6. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    Sh*966636*se Newbie
    Currently Being Moderated
    After removing SIP targets its start working...is there any impact
  • 7. Re: URGET- WLS10.3.3 problem starting MS There are no sip nor diameter channel
    Kishore Rout Journeyer
    Currently Being Moderated
    Hi,
    There is absolutely no impact. Better way to handle this type of issues is to remove all sip related dependencies from config.xml file(located $DOMAIN_HOME/config) and restart your admin and managed server.

    If SIP functionality is needed, then you can download and license OCCAS 5.0 or later.

    Regards,
    Kishore

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points