[JBoss JIRA] (AS7-6705) build modular AS with Apache Karaf support error
by Julio Carlos Barrera (JIRA)
[ https://issues.jboss.org/browse/AS7-6705?page=com.atlassian.jira.plugin.s... ]
Julio Carlos Barrera edited comment on AS7-6705 at 3/12/13 4:57 AM:
--------------------------------------------------------------------
I made no changes in any configuration, I tried it with a clean checkout from GitHub. I am going to open a forum thread to clarify it.
was (Author: logoff):
I made no changes in any configuration, I tried it with a clean checkout from GitHub. I am going to open an forum thread to clarify it.
> build modular AS with Apache Karaf support error
> ------------------------------------------------
>
> Key: AS7-6705
> URL: https://issues.jboss.org/browse/AS7-6705
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Reporter: Julio Carlos Barrera
> Labels: Karaf, OSGi, build_issue
>
> I followed the instruction of this forum thread https://community.jboss.org/message/801855 and it gave me this error:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build Modular 8.0.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ jboss-as-build-modular ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildNumber: bfeb0721e0a10c630d164a861c01e343b27ee313 at timestamp: 1363002756518
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildScmBranch: UNKNOWN
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (modular-config) @ jboss-as-build-modular ---
> [INFO] Executing tasks
> main:
> init:
> init.standalone:
> generate-standalone-configs:
> [echo] Generate subsystems definition for logging:osgi,osgi:karaf,configadmin to /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml
> [echo] Generate module dependencies from /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml to /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /home/logoff/soft/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> [echo] Merging standalone configuration/standalone/template-osgi.xml and /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml into /home/logoff/soft/jboss-as/build-modular/target/standalone.xml, using StandaloneMain
> init.domain:
> generate-domain-configs:
> build-standalone-server:
> [mkdir] Created dir: /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 240 files to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copied 43 empty directories to 4 empty directories under /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 1 file to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT/standalone/configuration
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.659s
> [INFO] Finished at: Mon Mar 11 12:52:39 CET 2013
> [INFO] Final Memory: 16M/168M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (modular-config) on project jboss-as-build-modular: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/logoff/soft/jboss-as/build-modular/build-modular-config.xml:113: Includesfile /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt not found.
> [ERROR] around Ant part ...<ant antfile="build-modular-config.xml" inheritRefs="true">... @ 4:62 in /home/logoff/soft/jboss-as/build-modular/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> It is possible to build JBoss AS 8.0.0.Alpha1-SNAPSHOT or any version with Apache Karaf support?
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6713) CLI: "pattern" and "replacement" should be required when creating logging filter
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6713?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-6713:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=915835
> CLI: "pattern" and "replacement" should be required when creating logging filter
> --------------------------------------------------------------------------------
>
> Key: AS7-6713
> URL: https://issues.jboss.org/browse/AS7-6713
> Project: Application Server 7
> Issue Type: Bug
> Components: Logging
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> It's able to set filter attribute without "pattern" and "replacement" although they are not nillable.
> calling:
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value={replace => {"replace-all" => true}})
> will create useless filter:
> "filter" => {"replace" => {
> "replace-all" => true,
> "pattern" => "undefined",
> "replacement" => "undefined"
> }}
> "filter-spec" => "substituteAll(\"undefined\",\"undefined\")"
> only "replace-all" is actually required now:
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:update-properties(filter={replace => {"pattern" => "JBAS","replacement" => "SABJ"}})
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: null",
> "rolled-back" => true
> }
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6713) CLI: "pattern" and "replacement" should be required when creating logging filter
by Chao Wang (JIRA)
Chao Wang created AS7-6713:
------------------------------
Summary: CLI: "pattern" and "replacement" should be required when creating logging filter
Key: AS7-6713
URL: https://issues.jboss.org/browse/AS7-6713
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Chao Wang
Assignee: Chao Wang
It's able to set filter attribute without "pattern" and "replacement" although they are not nillable.
calling:
/subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value={replace => {"replace-all" => true}})
will create useless filter:
"filter" => {"replace" => {
"replace-all" => true,
"pattern" => "undefined",
"replacement" => "undefined"
}}
"filter-spec" => "substituteAll(\"undefined\",\"undefined\")"
only "replace-all" is actually required now:
[standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:update-properties(filter={replace => {"pattern" => "JBAS","replacement" => "SABJ"}})
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: null",
"rolled-back" => true
}
--
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
13 years, 4 months
[JBoss JIRA] (AS7-5958) Incorrect Candidate permutation failed due to a conflict between imports exception when using host and fragment bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-5958?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-5958:
--------------------------------
Labels: (was: OSGI)
> Incorrect Candidate permutation failed due to a conflict between imports exception when using host and fragment bundles
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5958
> URL: https://issues.jboss.org/browse/AS7-5958
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Environment: Windows XP SP3
> Reporter: Paul Illingworth
> Fix For: 8.0.0.Alpha1
>
>
> I am getting the following exception when my bundle is being resolved. I don't believe this is correct.
> {noformat}
> 2012-11-15 15:10:41,403 DEBUG [org.jboss.osgi.resolver](qtp4105020-187) Candidate permutation failed due to a conflict between imports; will try another if possible.: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]] because it is exposed to package 'com.google.inject' from resources com.google.inject [HostBundleRevision[com.google.inject:3.0.0]] and com.google.inject [HostBundleRevision[com.google.inject:3.0.0]] via two dependency chains.
> Chain 1:
> resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]]
> import: null
> |
> export: osgi.wiring.package=com.google.inject
> com.google.inject [HostBundleRevision[com.google.inject:3.0.0]]
> Chain 2:
> resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]]
> import: null
> |
> export: osgi.wiring.package=com.saaconsultants.gwt.rpc.server.servlets; uses:=com.google.inject
> reims-gwt-rpc [HostBundleRevision[reims-gwt-rpc:1.0.0.SNAPSHOT]]
> import: null
> |
> export: osgi.wiring.package=com.google.inject
> com.google.inject [HostBundleRevision[com.google.inject:3.0.0]]
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1142)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:197)
> at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:56)
> at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:152)
> at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:167)
> at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:598)
> at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:214)
> at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:520)
> at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:331)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:437)
> at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:384)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.ops4j.pax.web.service.internal.HttpServiceStarted$2.invoke(HttpServiceStarted.java:209)
> at org.ops4j.pax.web.service.internal.$Proxy39.service(Unknown Source)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
> at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
> at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
> at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:117)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
> at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:74)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
> at org.eclipse.jetty.server.Server.handle(Server.java:349)
> at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
> at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
> at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
> at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
> at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
> at java.lang.Thread.run(Thread.java:662)
> 2012-11-15 15:10:41,403 TRACE [org.jboss.osgi.framework](qtp4105020-187) Release framework lock
> {noformat}
> It seems to be happening because the ResolverImpl.isCompatible() method is comparing two capabilities; one is an AbstractBundleCapability and the other is a WrappedCapability that contains the same instance of AbstractBundleCapability. The result of the comparison is false.
> As a quick hack I changed the equals method of WrappedCapability to
> {noformat}
> @Override
> public boolean equals(Object obj)
> {
> return m_cap.equals(obj);
> }
> {noformat}
> and that seemed to make it work and resolution was successful.
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6613) ConcurrentModificationException in BundleContext.getServiceReferences()
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6613?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6613:
--------------------------------
Summary: ConcurrentModificationException in BundleContext.getServiceReferences() (was: ConcurrentModificationException in JBoss OSGi Framework)
> ConcurrentModificationException in BundleContext.getServiceReferences()
> -----------------------------------------------------------------------
>
> Key: AS7-6613
> URL: https://issues.jboss.org/browse/AS7-6613
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Environment: Linux and Windows
> Reporter: Ed Roberts
> Assignee: Thomas Diesler
> Fix For: 8.0.0.Alpha1
>
>
> Starting up JBoss AS with a number of deployments, some of which use blueprint to activate services. One of the blueprint activations exposes the concurrency issue
> {code}
> 2013-02-22 15:57:08,193 ERROR [org.eclipse.gemini.blueprint.extender.internal.blueprint.activator.BlueprintLoaderListener](EclipseGeminiBlueprintExtenderThread-29) Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.saaconsultants.x, config=bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/osgi-context.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/ee-beans.xml)): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'otEclInterpreterServiceBean' defined in OSGi resource[bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml|bnd.id=170|bnd.sym=com.saaconsultants.x]: Cannot resolve reference to bean 'xService' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
> at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
> at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
> at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
> at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:149)
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:102)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1442)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:248)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
> ... 19 more
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
> at java.util.HashMap$ValueIterator.next(HashMap.java:922)
> at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferencesInternal(ServiceManagerImpl.java:205)
> at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferences(ServiceManagerImpl.java:189)
> at org.jboss.osgi.framework.internal.AbstractBundleContext.getServiceReferences(AbstractBundleContext.java:344)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:155)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:70)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:129)
> at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:168)
> at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:138)
> at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.afterPropertiesSet(ServiceDynamicInterceptor.java:467)
> at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean$2.run(OsgiServiceProxyFactoryBean.java:196)
> at org.eclipse.gemini.blueprint.service.importer.support.AbstractServiceImporterProxyFactoryBean.getObject(AbstractServiceImporterProxyFactoryBean.java:103)
> at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean.getObject(OsgiServiceProxyFactoryBean.java:125)
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142)
> ... 24 more
> {code}
--
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
13 years, 4 months
[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-1833:
----------------------------------------------
pkremens(a)redhat.com made a comment on [bug 908955|https://bugzilla.redhat.com/show_bug.cgi?id=908955]
Calling new reload command in quick succession I get:
[standalone@localhost:9999 /] reload
[standalone@localhost:9999 /] reload
Failed to execute :reload: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out
[disconnected /]
I tried to to add --timeout argument to CLI calling, but ConnectionException occurs again.
> CLI usability: operations that shutdown the server-side management interface result in "Communication error"
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-1833
> URL: https://issues.jboss.org/browse/AS7-1833
> Project: Application Server 7
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 7.0.0.Final, 7.0.1.Final
> Reporter: Radoslav Husar
> Assignee: Alexey Loubyansky
> Priority: Critical
> Labels: eap6-ux
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> If you shutdown the server, you get an error:
> {code}
> [standalone@localhost:9999 /] :shutdown
> Communication error: Channel closed
> Closed connection to localhost:9999
> {code}
> Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH.
> The same basic issue exists for the :reload operation.
--
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
13 years, 4 months