[
https://issues.apache.org/jira/browse/SYNAPSE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557170#action_12557170
]
Vesa Varimo commented on SYNAPSE-220:
-------------------------------------
Also address printed in log entries is wrong:
2008-01-09 09:07:51,416 [192.168.40.197-qa.ss.company.com] [WrapperSimpl
eAppMain] INFO HttpCoreNIOListener HTTPS Listener starting on port : 9443
2008-01-09 09:07:51,417 [192.168.40.197-qa.ss.company.com] [WrapperSimpl
eAppMain] INFO ServerManager Starting transport https on port 9443
I was binding Synapse to interfaces 192.168.40.104 and 192.168.40.105. The main
(eth0) interface is 192.168.40.197.
Vesa
> Synapse doesn't support virtual hosting
> ---------------------------------------
>
> Key: SYNAPSE-220
> URL: https://issues.apache.org/jira/browse/SYNAPSE-220
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1
> Reporter: Vesa Varimo
> Assignee: Asankha C. Perera
> Fix For: 1.1.1-QA-B2
>
>
> I have environment which has multiple virtual network interfaces.
> I'm unable to specify the ip address that I'm willing to use for Synapse.
> It would be great to have this feature implemented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
