May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4834) Race condition in RemoteOutboundConnectionService

by Yokoyama Yasuo (JIRA)

Yokoyama Yasuo created AS7-4834: ----------------------------------- Summary: Race condition in RemoteOutboundConnectionService Key: AS7-4834 URL: https://issues.jboss.org/browse/AS7-4834 Project: Application Server 7 Issue Type: Bug Components: Remoting Affects Versions: 7.1.1.Final Reporter: Yokoyama Yasuo Assignee: David Lloyd The following errors may be caused if two or more remote-outbound-connection is defined. {quote} 16:24:24,187 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.remoting.endpoint.subsystem.outbound-connection.dummy-6: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.subsystem.outbound-connection.dummy-6: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] Caused by: org.jboss.remoting3.DuplicateRegistrationException: URI scheme 'remote://' is already registered to a provider at org.jboss.remoting3.EndpointImpl.addConnectionProvider(EndpointImpl.java:421) at org.jboss.as.remoting.RemoteOutboundConnectionService.start(RemoteOutboundConnectionService.java:89) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-4836) Invalid recursive module creation triggered by bundle event

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-4836?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-4836: -------------------------------- Fix Version/s: 7.1.3.Final (EAP) 7.2.0.Alpha1 Affects Version/s: 7.1.2.Final (EAP) Component/s: OSGi Forum Reference: https://community.jboss.org/message/736258 (was: https://community.jboss.org/message/736258) > Invalid recursive module creation triggered by bundle event > ----------------------------------------------------------- > > Key: AS7-4836 > URL: https://issues.jboss.org/browse/AS7-4836 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.2.Final (EAP) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > {code} > at org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:128) > at org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:298) > at org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:196) > at org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:253) > at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:201) > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) > at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) > at org.jboss.osgi.framework.internal.HostBundleRevision.findEntries(HostBundleRevision.java:126) > at org.jboss.osgi.framework.internal.AbstractBundleState.findEntries(AbstractBundleState.java:443) > at org.eclipse.gemini.blueprint.extender.internal.support.NamespaceManager.maybeAddNamespaceHandlerFor(NamespaceManager.java:130) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener.maybeAddNamespaceHandlerFor(ContextLoaderListener.java:462) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$NamespaceBundleLister.handleEvent(ContextLoaderListener.java:169) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$BaseListener.bundleChanged(ContextLoaderListener.java:137) > at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireBundleEvent(FrameworkEventsPlugin.java:372) > at org.jboss.osgi.framework.internal.AbstractBundleState.fireBundleEvent(AbstractBundleState.java:198) > at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:192) > at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:174) > at org.jboss.osgi.framework.internal.ResolverPlugin.setBundleToResolved(ResolverPlugin.java:277) > at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:207) > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) > at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:232) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:485) > at org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:145) > at org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:99) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4836) Invalid recursive module creation triggered by bundle event

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-4836?page=com.atlassian.jira.plugin.s... ] Thomas Diesler moved JBOSGI-554 to AS7-4836: -------------------------------------------- Project: Application Server 7 (was: JBoss OSGi) Key: AS7-4836 (was: JBOSGI-554) Workflow: GIT Pull Request workflow (was: jira) Security: (was: Public) > Invalid recursive module creation triggered by bundle event > ----------------------------------------------------------- > > Key: AS7-4836 > URL: https://issues.jboss.org/browse/AS7-4836 > Project: Application Server 7 > Issue Type: Bug > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > {code} > at org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:128) > at org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:298) > at org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:196) > at org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:253) > at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:201) > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) > at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) > at org.jboss.osgi.framework.internal.HostBundleRevision.findEntries(HostBundleRevision.java:126) > at org.jboss.osgi.framework.internal.AbstractBundleState.findEntries(AbstractBundleState.java:443) > at org.eclipse.gemini.blueprint.extender.internal.support.NamespaceManager.maybeAddNamespaceHandlerFor(NamespaceManager.java:130) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener.maybeAddNamespaceHandlerFor(ContextLoaderListener.java:462) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$NamespaceBundleLister.handleEvent(ContextLoaderListener.java:169) > at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$BaseListener.bundleChanged(ContextLoaderListener.java:137) > at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireBundleEvent(FrameworkEventsPlugin.java:372) > at org.jboss.osgi.framework.internal.AbstractBundleState.fireBundleEvent(AbstractBundleState.java:198) > at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:192) > at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:174) > at org.jboss.osgi.framework.internal.ResolverPlugin.setBundleToResolved(ResolverPlugin.java:277) > at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:207) > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) > at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:232) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:485) > at org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:145) > at org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:99) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4760) Logging should fallback to English message when format error

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created AS7-4760: ------------------------------------- Summary: Logging should fallback to English message when format error Key: AS7-4760 URL: https://issues.jboss.org/browse/AS7-4760 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Takayoshi Kimura Assignee: James Perkins It's related to AS7-4735. Currently Japanese message resources are missing parameter index and causes format errors. When this happens, it prints only format error and the original log message is not logged. This makes troubleshooting impossible. We need fall back mechanism to avoid "logs are missing" situation. This format error very likely could happen all time. For example, when someone add, remove, swap or replace existing log message parameters and forgot to update all i18n properties accordingly at the same time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-4735) Missing parameter order in Japanese message resource files

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created AS7-4735: ------------------------------------- Summary: Missing parameter order in Japanese message resource files Key: AS7-4735 URL: https://issues.jboss.org/browse/AS7-4735 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Takayoshi Kimura Assignee: Takayoshi Kimura I set 7.1.1.Final in Affects Version/s, but this is really an issue after 7.1.1.Final (pre-7.1.2). In this commit, Japanese message resource properties are added, but most of them don't specify parameter order properly. We need to rework on these properties files. {quote} commit 27b56ae78a60f42139d615b289efa32c21aecc69 Author: James Perkins <jperkins(a)redhat.com> Date: 2012-04-30 12:59:48 -0700 Added translations properties files. {quote} For example, English: "%s is %d" Japanese: "%d は %s" (Wrong format, this causes parameter format error) Japanese: "%2$d は %1$s" (Correct format) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
16
0 / 0

[JBoss JIRA] (JBRULES-3511) Error jitting constraints accessing a map with primitive keys

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3511: ------------------------------------ Summary: Error jitting constraints accessing a map with primitive keys Key: JBRULES-3511 URL: https://issues.jboss.org/browse/JBRULES-3511 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Error when jitting a constraint like: Bean( map[2] = "two" ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3510) Optional Maven dependencies are not declared as optional in OSGi manifest properties

by Chris Dolan (JIRA)

Chris Dolan created JBRULES-3510: ------------------------------------ Summary: Optional Maven dependencies are not declared as optional in OSGi manifest properties Key: JBRULES-3510 URL: https://issues.jboss.org/browse/JBRULES-3510 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Final Environment: Apache Karaf 2.2.4, Drools planner 5.4.0.Final Reporter: Chris Dolan Assignee: Mark Proctor When I try to load drools-core.jar into my OSGi container, I get this error: {noformat} The bundle "org.drools.core_5.4.0.Final [199]" could not be resolved. Reason: Missing Constraint: Import-Package: com.google.protobuf; version="0.0.0" {noformat} The maven-bundle-plugin configuration in drools-core/pom.xml should include ";resolution:=optional" after the packages of the optional dependencies. As a workaround, I can simply add the protobuf bundle to Karaf, but that's unpleasant because it should be unnecessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4831) CLONE - Ensure that bin's *.bat Files are in DOS Format

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-4831?page=com.atlassian.jira.plugin.s... ] Paul Gier moved JBPAPP-9050 to AS7-4831: ---------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4831 (was: JBPAPP-9050) Issue Type: Enhancement (was: Task) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 ER 7) Component/s: Build System (was: Build) Security: (was: Public) Fix Version/s: 7.1.3.Final (EAP) (was: EAP 6.0.0 ER8) Docs QE Status: (was: NEW) > CLONE - Ensure that bin's *.bat Files are in DOS Format > ------------------------------------------------------- > > Key: AS7-4831 > URL: https://issues.jboss.org/browse/AS7-4831 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System > Reporter: Jimmy Wilson > Assignee: Paul Gier > Priority: Blocker > Fix For: 7.1.3.Final (EAP) > > > We need to ensure that bin's *.bat files are in DOS format as changing them in subsequent release can mess up the patching process... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-826) LazyEnlistableConnectionManager

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-826: ------------------------------------- Summary: LazyEnlistableConnectionManager Key: JBJCA-826 URL: https://issues.jboss.org/browse/JBJCA-826 Project: IronJacamar Issue Type: Task Components: Common, Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha8 Let our ConnectionManager implement javax.resource.spi.LazyEnlistableConnectionManager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4787) CLONE - Host controller hangs intermitentlly when connecting to domain controller

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/AS7-4787?page=com.atlassian.jira.plugin.s... ] Dominik Pospisil reopened AS7-4787: ----------------------------------- Unfortunatelly, I have managed to reproduce the issue with ER8 (jboss-remoting 3.2.7.GA-redhat-1). It is just much more hard to reproduce. ER8 thread dumps attached to JBPAPP linked JIRA. > CLONE - Host controller hangs intermitentlly when connecting to domain controller > --------------------------------------------------------------------------------- > > Key: AS7-4787 > URL: https://issues.jboss.org/browse/AS7-4787 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Dominik Pospisil > Assignee: Emanuel Muckenhuber > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > Host controller hangs intermittently when connecting to domain controller. Host controller is stuck forever and never recovers from this sistuation. > I have never experienced this on local network, however this is pretty easy to reproduce using wireless network. The testing was done on private local wireless network with zero packet outages: > 6973 packets transmitted, 6969 received, 0% packet loss, time 25334ms > rtt min/avg/max/mdev = 1.398/4.318/284.480/11.672 ms, pipe 15, ipg/ewma 3.633/2.775 ms > Also, the problem seems to be affecting only connecting - once the connection is made, all the management operations are performed correctly without problems. > Logs from connecting hc: > 14:37:01,827 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1 > 14:37:01,973 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' > [Host Controller] 14:37:03,957 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1 > [Host Controller] 14:37:04,280 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-1 > [Host Controller] 14:37:04,674 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.1.Final-redhat-1) starting > [Host Controller] 14:37:05,919 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.3.GA-redhat-1 > [Host Controller] 14:37:05,943 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.3.GA-redhat-1 > [Host Controller] 14:37:05,963 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.4.GA-redhat-1 > [Host Controller] 14:37:06,018 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 192.168.1.67:9999 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2012