[JBoss JIRA] (LOGMGR-42) StringIndexOutOfBoundsException in exceptionFormatStep
by Marcus Klimstra (JIRA)
Marcus Klimstra created LOGMGR-42:
-------------------------------------
Summary: StringIndexOutOfBoundsException in exceptionFormatStep
Key: LOGMGR-42
URL: https://issues.jboss.org/browse/LOGMGR-42
Project: JBoss Log Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 1.3.1.Final
Reporter: Marcus Klimstra
Assignee: David Lloyd
StringIndexOutOfBoundsException is thrown when the path does not contain a jarName.
In my case path is "/com/.../Foo.class" (from a custom classloader).
Stacktrace:
java.util.logging.ErrorManager: 5: Formatting error
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.charAt(String.java:686)
at org.jboss.logmanager.formatters.Formatters$12.renderExtended(Formatters.java:524)
at org.jboss.logmanager.formatters.Formatters$12.renderRaw(Formatters.java:388)
at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:150)
at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86)
at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35)
at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49)
at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:290)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298)
at org.jboss.logmanager.Logger.logRaw(Logger.java:721)
at org.jboss.logmanager.Logger.log(Logger.java:539)
The exception occurs here: (last line with while)
if (jarName == null) {
// OK, that would have been too easy. Next let's just grab the last piece before the class name
int endIdx = path.lastIndexOf(classResourceName);
if (endIdx != -1) {
do {
endIdx--;
} while (path.charAt(endIdx) == '/' || path.charAt(endIdx) == '\\' || path.charAt(endIdx) == '?');
Since there is nothing before the initial /, endIdx becomes -1.
--
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, 6 months
[JBoss JIRA] (AS7-5541) [7.1] OSGi bootstrap may exhaust threads and deadlock
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5541:
-----------------------------------
Summary: [7.1] OSGi bootstrap may exhaust threads and deadlock
Key: AS7-5541
URL: https://issues.jboss.org/browse/AS7-5541
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.1.Final
Reporter: David Bosschaert
Assignee: Thomas Diesler
Priority: Critical
Fix For: 7.2.0.Alpha1
Reported on the Forum:
{code}org.jboss.msc.service.fail JB${bisas.pid} MSC service thread 1-16 ERROR MSC00001: Failed to start service jbosgi.AutoInstallProvider.COMPLETE: org.jboss.msc.service.StartException in service jbosgi.AutoInstallProvider.COMPLETE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalStateException: Cannot load module: deployment.osgi.enterprise:4.2.0.201003190513
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:261)
at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:229)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAll(ResolverPlugin.java:209)
at org.jboss.osgi.framework.internal.PackageAdminPlugin.resolveBundles(PackageAdminPlugin.java:385)
at org.jboss.as.osgi.service.AutoInstallIntegration$1.start(AutoInstallIntegration.java:176)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
... 3 more
Caused by: org.jboss.modules.ModuleLoadException: Timeout waiting for module service: deployment.osgi.enterprise:4.2.0.201003190513
at org.jboss.as.server.moduleservice.ServiceModuleLoader$ModuleSpecLoadListener.getModuleSpec(ServiceModuleLoader.java:133)
at org.jboss.as.server.moduleservice.ServiceModuleLoader.findModule(ServiceModuleLoader.java:174)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:158)
at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:233)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:246)
at org.jboss.as.osgi.service.ModuleLoaderIntegration.preloadModule(ModuleLoaderIntegration.java:191)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204)
at org.jboss.osgi.framework.internal.ModuleManagerPlugin.loadModule(ModuleManagerPlugin.java:556)
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:259)
... 9 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, 6 months
[JBoss JIRA] (AS7-5517) NullPointerException if an expression is in the jboss-app.xml file
by Francois MESSIAEN (JIRA)
Francois MESSIAEN created AS7-5517:
--------------------------------------
Summary: NullPointerException if an expression is in the jboss-app.xml file
Key: AS7-5517
URL: https://issues.jboss.org/browse/AS7-5517
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.1.3.Final (EAP)
Environment: JBoss AS 7.1.3 SNAPSHOT of the 9/06/12
Windows 7 pro
Reporter: Francois MESSIAEN
Assignee: David Lloyd
A NullPointerException is thrown when the JBoss AS 7.1.3 tries to replace an expression in the "jboss-app.xml" file.
--
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, 6 months
[JBoss JIRA] (AS7-5498) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-5498:
-----------------------------------
Summary: infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
Key: AS7-5498
URL: https://issues.jboss.org/browse/AS7-5498
Project: Application Server 7
Issue Type: Bug
Environment: affected master
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 7.2.0.Alpha1
Noticed by alexey
[rhusar@rhusar jboss-as]$ java -version
java version "1.7.0_06-icedtea"
OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
{noformat}
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan ---
[INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan ---
[INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec
Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest
Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE!
Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Results :
Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null>
getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null>
Tests in error:
removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest)
Tests run: 33, Failures: 2, Errors: 6, Skipped: 0
{noformat}
--
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, 6 months
[JBoss JIRA] (AS7-4960) JMS destinations' underlying core queues are not manageable
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-4960:
--------------------------------
Summary: JMS destinations' underlying core queues are not manageable
Key: AS7-4960
URL: https://issues.jboss.org/browse/AS7-4960
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Minor
When a JMS destination is created, we expose it in the management model (in jms-queue)
However, creating a JMS destination may also result in the creation of core-queues resources (1 for JMS queues, 1 per subscribers for JMS topics). This core queues are not exposed in the management model. Only those configured in config files or CLI are present.
(However we make sure that we add core _addresses_ (1 for each JMS destination) at runtime to the management model)
This means that AS7 messaging subsystem is not a "correct" reflection of the HornetQ runtime. I can't make my mind whether it is a problem. Afaict, most operations on these underlying queues can be also done at the JMS destination level through their management operations.
--
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, 6 months