geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
Date Tue, 08 Jan 2013 20:40:14 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547235#comment-13547235
] 

Jarek Gawor commented on GERONIMO-6427:
---------------------------------------

This is caused by the portlet that displays a list of web or ear applications. The portlet
tries to temporarily load the disabled module to see if it is a web module and to populate
the context path and display name information. The portlet then unloads the given module.
The load operation followed a quick unload operation causes this error (because some things
in this case are handled asynchronously). We could try synchronizing the code better so that
unload only happens if load was fully completed but I don't think that's really needed for
the portlet. The load operation is expensive (it installs bundles, loads gbeans, etc.) so
maybe a better option is not to load the disabled modules. The side effect is that the context
path and display name fields in the portlet would not be populated and also the war portlet
would not show war modules that are embedded in the ear modules (for modules are of course
not loaded).

                
> Transport scheme NOT recognized: [tcp]
> --------------------------------------
>
>                 Key: GERONIMO-6427
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6427
>             Project: Geronimo
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 3.0.0
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>
> I ran into the following exception:
> 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker.
Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport
scheme NOT recognized: [tcp]
> java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme
NOT recognized: [tcp]
>     at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
>     at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656)
>     at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099)
>     at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049)
>     at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511)
>     at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458)
> This happens if all the activemq modules are configured with load="false" in config.xml
and somebody tries to display all web applications using the admin console.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message