Java Blazeds AmfChannels工作不正常

您好，我正在使用Tomcat 6+windows XP环境开发blazeds应用程序。我的消息已与

flex.messaging.endpoints.AMFEndpoint

配对。如果我添加新的

flex.messaging.endpoints.StreamingAMFEndpoint

，它将不起作用。它发送通道故障错误，并且如果我在amf中更改轮询间隔，也不会受到影响。amf通道每3秒发送一次轮询

有人能帮我解决这个问题吗。我已经分享了下面的代码

My service-config.xml

<?xml version="1.0" encoding="UTF-8"?>
<services-config>

    <services>
        <service-include file-path="remoting-config.xml" />
        <service-include file-path="messaging-config.xml" />
    </services>

<channels>
    <channel-definition id="my-amf"
                        class="mx.messaging.channels.AMFChannel">
        <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf"
                  class="flex.messaging.endpoints.AMFEndpoint"/>
        <properties>
            <polling-enabled>true</polling-enabled>
            <polling-interval-millis>60000</polling-interval-millis>
        </properties>
    </channel-definition>

    <channel-definition id="my-streaming-amf"
                        class="mx.messaging.channels.StreamingAMFChannel">
        <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf"
                  class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
        <properties>
            <idle-timeout-minutes>0</idle-timeout-minutes>
            <max-streaming-clients>10</max-streaming-clients>
            <server-to-client-heartbeat-millis>5000</server-to-client-heartbeat-millis>
            <user-agent-settings>
               <user-agent match-on="MSIE" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
               <user-agent match-on="Firefox" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
            </user-agent-settings>
        </properties>
    </channel-definition>
</channels> 


</services-config>

<service id="message-service" class="flex.messaging.services.MessageService">


    <adapters>
        <adapter-definition id="CustomServiceAdapter"
            class="com.xxx.xxx.CustomServiceAdapter" default="true"/>

    </adapters>

    <default-channels>

        <channel ref="my-streaming-amf"/>
    </default-channels>

    <destination id="AlarmEvents"> 
            <channels>  
                <channel ref="my-streaming-amf" />  
            </channels>  
            <adapter ref="CustomServiceAdapter"/>  

            <properties>
                <network>
                    <session-timeout>0</session-timeout>
                </network>

                <server>
                    <message-time-to-live>0</message-time-to-live>
                    <durable>true</durable>
                </server>

            </properties> 
    </destination>

</service>

符合事实的
60000
0
10
5000

Messaging-config.xml

<?xml version="1.0" encoding="UTF-8"?>
<services-config>

    <services>
        <service-include file-path="remoting-config.xml" />
        <service-include file-path="messaging-config.xml" />
    </services>

<channels>
    <channel-definition id="my-amf"
                        class="mx.messaging.channels.AMFChannel">
        <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf"
                  class="flex.messaging.endpoints.AMFEndpoint"/>
        <properties>
            <polling-enabled>true</polling-enabled>
            <polling-interval-millis>60000</polling-interval-millis>
        </properties>
    </channel-definition>

    <channel-definition id="my-streaming-amf"
                        class="mx.messaging.channels.StreamingAMFChannel">
        <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf"
                  class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
        <properties>
            <idle-timeout-minutes>0</idle-timeout-minutes>
            <max-streaming-clients>10</max-streaming-clients>
            <server-to-client-heartbeat-millis>5000</server-to-client-heartbeat-millis>
            <user-agent-settings>
               <user-agent match-on="MSIE" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
               <user-agent match-on="Firefox" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
            </user-agent-settings>
        </properties>
    </channel-definition>
</channels> 


</services-config>

<service id="message-service" class="flex.messaging.services.MessageService">


    <adapters>
        <adapter-definition id="CustomServiceAdapter"
            class="com.xxx.xxx.CustomServiceAdapter" default="true"/>

    </adapters>

    <default-channels>

        <channel ref="my-streaming-amf"/>
    </default-channels>

    <destination id="AlarmEvents"> 
            <channels>  
                <channel ref="my-streaming-amf" />  
            </channels>  
            <adapter ref="CustomServiceAdapter"/>  

            <properties>
                <network>
                    <session-timeout>0</session-timeout>
                </network>

                <server>
                    <message-time-to-live>0</message-time-to-live>
                    <durable>true</durable>
                </server>

            </properties> 
    </destination>

</service>

0
0
符合事实的

您可以发布您收到的错误吗？另外，您可以通过一种方法来控制从客户端选择的频道，您是从客户端选择的吗？客户端上是否有通道集代码？如果是这样，请将代码粘贴到这里。嗨，宙斯，我还没有在flex端编写channelset代码。我刚刚在flex编译器中添加了service-config.xml文件的路径，并将消费者和生产者的目的地作为AlarmEvents，它已在messaging-config.xml中写入。