Re: Servicemix proxy question

[Freeman Fang <fr...@gmail.com>]

We probably have the fourth option.
Configure a proxy in maven settings.xml, so that this proxy only affect the maven related stuff.
－－－－－－－－－－－－－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042

On 2012-12-1, at 上午5:25, Gert Vanthienen wrote:

> L.S.,
> 
> 
> Those http.* system properties are being used for the entire JVM -
> personally, I would have assumed the http.nonProxyHosts would have fixed
> the issue for you.  Did you try with the exact same address format (IP or
> name) as the one you're using for your CXF-BC provider endpoint?
> 
> Another solution could be to upgrade to Apache ServiceMix 4.4.2.  Starting
> with the 4.4.x releases, we have a 'full' assembly type available for users
> that run Apache ServiceMix behind a firewall.  That assembly is a lot
> larger, but it contains all the bundles required for installing features
> without requiring an internet connection.  You can download that at
> http://servicemix.apache.org/downloads.html
> 
> A third alternative would be using a Maven repository manager (like Apache
> Archiva, Nexus, Artifactory, ...) that you install on your local network.
> You can have it download and cache artifacts from remote Maven
> repositories and the reconfigure Apache ServiceMix to connect to the
> repository manager instead of directly to the internet.
> 
> 
> Regards,
> 
> Gert Vanthienen
> 
> 
> 
> On Thu, Nov 29, 2012 at 12:29 PM, attilav <dz...@freemail.hu> wrote:
> 
>> Hi all,
>> 
>> I am using servicemix 4.3.1 behind a corporate firewall. I have
>> successfully
>> configured it via the syste.properties file to use the proxy, so that new
>> features can be fetched as needed (i.e. feature:install camel-nmr)
>> 
>> http.proxyHost=xx.xx.xx.xx
>> http.proxyPort=3128
>> http.proxyAuth=mtuser:12345
>> 
>> It works OK.
>> 
>> Next, I need to consume an internal web-service (cxfbc:provider), but if
>> the
>> proxy is set it cannot connect. It seems to me that the soap request too is
>> directed to the proxy. If I disable proxying (by commenting the above
>> lines), then the soap request works just fine -- but then features cannot
>> be
>> installed.
>> 
>> I tried to set the nonProxyHosts property, but it seems to have no effect:
>> http.nonProxyHosts=10.11.12.13
>> 
>> So the question is, how can I configure servicemix to access simultaneously
>> both the internet and the local net?
>> 
>> regards,
>> Attila
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://servicemix.396122.n5.nabble.com/Servicemix-proxy-question-tp5715059.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> 

Re: Servicemix proxy question

[Gert Vanthienen <ge...@gmail.com>]

L.S.,


I just wanted to make sure that the actual address used in the CXF endpoint
configuration matched the one in http.nonProxyHosts, but I would have
expected your current configuration to work.  Not entirely sure what's
going wrong here.  One other solution you might want to consider is to
configure the CXF HTTP Conduit itself with the proxy parameters - looking
at https://issues.apache.org/jira/browse/CXF-2839, it looks like it at
least support those properties as well as the setting for non-proxy hosts
are available on the conduit itself.

BTW, did you consider the repository manager solution I mentioned?  That's
commonly used because it also helps you in the (usual Maven-based)
development of the application bundles themselves.


Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


On Tue, Dec 4, 2012 at 4:23 PM, attilav <dz...@freemail.hu> wrote:

> Hi,
>
> Thanks for your replies.
>
> The fourth option (.m2/settings.xml) I already tried - and it would not
> work. I mean it has the same effect as setting the proxy in
> system.properties - it still redirects cxf to the proxy.
>
> Gert, what do you mean by "exact same address format"?
>
> In my beans.xml I have
>     <cxfbc:provider wsdl="classpath:/wsdl/PNM-FDL.wsdl"
>                           locationURI="http://10.11.12.13:8001/PMSEvent"
>                           service="pms:PMSServiceSoap"
>                           endpoint="PMSServiceSoap"
>                           useJBIWrapper="false"
>                           >
>     </cxfbc:provider>
>
> In the system.propreties I put:
> http.nonProxyHosts=10.11.12.13
>
>
> As for the upgrade option, I am already planning the upgrade to 4.4,
> however
> that takes time, as I have to retest quite a number of applications.
>
> regards,
> Attila
>
>
>
> --
> View this message in context:
> http://servicemix.396122.n5.nabble.com/Servicemix-proxy-question-tp5715059p5715143.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

Re: Servicemix proxy question

[attilav <dz...@freemail.hu>]

Hi,

Thanks for your replies.

The fourth option (.m2/settings.xml) I already tried - and it would not
work. I mean it has the same effect as setting the proxy in
system.properties - it still redirects cxf to the proxy.

Gert, what do you mean by "exact same address format"? 

In my beans.xml I have 
    <cxfbc:provider wsdl="classpath:/wsdl/PNM-FDL.wsdl"
                          locationURI="http://10.11.12.13:8001/PMSEvent"
                          service="pms:PMSServiceSoap"
                          endpoint="PMSServiceSoap"
                          useJBIWrapper="false"
                          >
    </cxfbc:provider>

In the system.propreties I put: 
http.nonProxyHosts=10.11.12.13 


As for the upgrade option, I am already planning the upgrade to 4.4, however
that takes time, as I have to retest quite a number of applications.

regards,
Attila



--
View this message in context: http://servicemix.396122.n5.nabble.com/Servicemix-proxy-question-tp5715059p5715143.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.