[
https://issues.apache.org/jira/browse/SMX4-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176547#comment-13176547
]
Freeman Fang commented on SMX4-1003:
------------------------------------
>From your description, when you say you're offline you're actually not
>offline, but just use some kind of firewall to block external server request,
>right?
If so, for me it's more like your network environment configuration problem.
IIRC, some firewall always hold request to external server long time but not
return failed immediately which is for security reason, the firewall don't want
you know immediately which server is blocked, it will take you longer time to
figure it out, just for better security when you attempt to try and find
something.
When I said I'm offline, I simply "Turn Airport Off" on my mac, which means my
machine has no physical internet connection, I didn't touch any else network
configuration(like the gateway you mentioned here), all are default one and
your testcase works perfectly for me.
> Problem on start bundle blueprint with cxf + reference to an osgi service
> expose on spring bundle on offline environment
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: SMX4-1003
> URL: https://issues.apache.org/jira/browse/SMX4-1003
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.4.0
> Environment: amd64 - linux
> Reporter: Ge@@ru
> Assignee: Freeman Fang
> Priority: Minor
> Fix For: 4.5.0
>
> Attachments: test-blueprint.tar.bz2
>
>
> On offline environment bundle that is reference to osgi service expose from
> spring bundle leave on Grace Period status until timeout expired. At timeout
> bundle go correctly to Created status but not automatically when service osgi
> is correctly deployed and started.
> With log trace i see this messages when timeout expired:
> 11:23:00,067 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.buslifecycle.CXFBusLifeCycleManager.
> 11:23:00,068 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.bus.osgi.OSGiExtensionLocator$OSGIBusListener.
> 11:23:00,069 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.ws.policy.PolicyAnnotationListener.
> 11:23:00,069 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.service.factory.FactoryBeanListenerManager.
> 11:23:00,070 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.ws.policy.PolicyEngineImpl.
> 11:23:00,073 | DEBUG | rint Extender: 2 | test-blueprint-osgi-cxf-rs |
> 184 - test-blueprint-osgi-cxf-rs - 0.1.0.SNAPSHOT | ServiceEvent REGISTERED
> 11:23:00,142 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.corba.CorbaBindingFactory.
> 11:23:00,145 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.soap.SoapBindingFactory.
> 11:23:00,146 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.xml.XMLBindingFactory.
> 11:23:00,146 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.object.ObjectBindingFactory.
> 11:23:00,155 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.http.HttpBindingFactory.
> 11:23:00,185 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.binding.soap.SoapTransportFactory.
> 11:23:00,188 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.transport.http.HTTPTransportFactory.
> 11:23:00,192 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.transport.local.LocalTransportFactory.
> 11:23:00,192 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.transport.jms.JMSTransportFactory.
> 11:23:00,195 | DEBUG | rint Extender: 2 | DefaultResourceManager |
> - - | resolving resource <cxf> type <interface org.apache.cxf.Bus>
> 11:23:00,231 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.transport.http_jetty.JettyDestinationFactory.
> 11:23:00,236 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngineFactory.
> 11:23:00,237 | DEBUG | rint Extender: 2 | DefaultResourceManager |
> - - | resolving resource <cxf> type <interface org.apache.cxf.Bus>
> 11:23:00,253 | DEBUG | rint Extender: 2 | JettyHTTPServerEngineFactory |
> - - | Creating Jetty HTTP Server Engine for port 8193.
> 11:23:00,255 | DEBUG | rint Extender: 2 | JettyHTTPServerEngine |
> - - | Configured port 8193 for "http".
> 11:23:00,258 | INFO | rint Extender: 2 | ServerImpl |
> - - | Setting the server's publish address to be http://0.0.0.0:8193/
> 11:23:00,262 | DEBUG | rint Extender: 2 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.endpoint.ServerRegistryImpl.
> 11:23:00,264 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.endpoint.ServerLifeCycleManagerImpl.
> 11:23:00,268 | DEBUG | rint Extender: 1 | ConfigurerImpl |
> - - | Could not determine bean name for instance of class
> org.apache.cxf.management.jmx.InstrumentationManagerImpl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
