[ 
https://issues.apache.org/activemq/browse/SM-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42459#action_42459
 ] 

tpounds edited comment on SM-1205 at 4/25/08 11:20 PM:
-------------------------------------------------------------

After looking through the ServiceMix source code and inspecting the the default 
ServiceMix settings I realized this ticket is invalid and a result of a 
misconfiguration on my end. The solution to allow the wsn2005 component to play 
nice with an ActiveMQ broker without a transport connector configured is to 
change the default activemq.url property in servicemix.properties to 
vm://localhostost.

      was (Author: tpounds):
    After looking through the ServiceMix source code and inspecting the the 
default ServiceMix settings I realized this ticket is invalid and a result of a 
misconfiguration on my end.
  
> wsn component fails to start if there is no transport connector available
> -------------------------------------------------------------------------
>
>                 Key: SM-1205
>                 URL: https://issues.apache.org/activemq/browse/SM-1205
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-wsn2005
>    Affects Versions: 3.2.1
>            Reporter: Trevor Pounds
>            Assignee: Trevor Pounds
>         Attachments: servicemix.log
>
>
> The error occurs if the activemq.xml file does not have a transportConnector 
> defined. This doesn't seem desired in all cases in which one wishes to 
> utilize a vm transport and not allow connections on a tcp socket. I'm not 
> sure how this would affect the wsn component directly since we are not using 
> it. The current workaround for us it remove wsn component from hotdeploy 
> directory in this certain configuration. I've attached an error log showing 
> the offending error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to