June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-684) CompositeIndexProcessor uses wrong module loader to load external annotation indexes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-684?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-684: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1220009|https://bugzilla.redhat.com/show_bug.cgi?id=1220009] from MODIFIED to ON_QA > CompositeIndexProcessor uses wrong module loader to load external annotation indexes > ------------------------------------------------------------------------------------ > > Key: WFCORE-684 > URL: https://issues.jboss.org/browse/WFCORE-684 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.CR2 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2900: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1065128|https://bugzilla.redhat.com/show_bug.cgi?id=1065128] from MODIFIED to ON_QA > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-678) console-enabled="false" does not work in domain mode to disable web access to admin console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-678?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-678: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1215244|https://bugzilla.redhat.com/show_bug.cgi?id=1215244] from MODIFIED to ON_QA > console-enabled="false" does not work in domain mode to disable web access to admin console > ------------------------------------------------------------------------------------------- > > Key: WFCORE-678 > URL: https://issues.jboss.org/browse/WFCORE-678 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: luck3y > Assignee: luck3y > Fix For: 1.0.0.CR2 > > > Description of problem: > Disabling the web interface of the admin console using the console-enabled attribute does not work in domain mode. > Version-Release number of selected component (if applicable): > EAP 6.3.3 > How reproducible: > Very > Steps to Reproduce: > 1. Set up domain installation > 2. Set console-enabled="false" attribute on http management interface in host.xml [1] or using CLI [2] > 3. Log into admin console ( http://localhost:9990/console ) > [1] Set console-enabled in host.xml: > <http-interface security-realm="ManagementRealm" console-enabled="false"> > <socket interface="management" port="${jboss.management.http.port:9990}" secure-port="9443"/> > </http-interface> > [2] Set console-enabled through CLI: > /host=master/core-service=management/management-interface=http-interface/:write-attribute(name=console-enabled,value=false) > Actual results: > Able to access and log into web admin console. > Expected results: > Empty or no page is displayed as in standalone mode. > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-639) ManagementPermissionAuthorizer is limited to the standard roles for its authorizeJmxOperation impl

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-639?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-639: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1230394|https://bugzilla.redhat.com/show_bug.cgi?id=1230394] from MODIFIED to ON_QA > ManagementPermissionAuthorizer is limited to the standard roles for its authorizeJmxOperation impl > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-639 > URL: https://issues.jboss.org/browse/WFCORE-639 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 2.0.0.Alpha3 > > > ManagementPermissionAuthorizer.authorizeJmxOperation uses hard coded decision making based on the standard 7 roles. This is inflexible and specifically doesn't allow scoped roles to function properly. > I believe the JmxPermissionFactory interface needs to be redone to use permissions instead of role names. It should have an API more like org.jboss.as.controller.access.permission.PermissionFactory, with getUserPermissions and getRequiredPermissions. Something like > PermissionCollection getUserPermissions(Caller caller, Environment callEnvironment, JmxAction action) > PermissionCollection getRequiredPermissions(JmxAction action); > Then ManagementPermissionAuthorizer.authorizeJmxOperation does a permission match check similar to what it does for management resource permissions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-608) Using ? as control character in .inputrc causes CLI to terminate immediately.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-608?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-608: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1203997|https://bugzilla.redhat.com/show_bug.cgi?id=1203997] from MODIFIED to ON_QA > Using ? as control character in .inputrc causes CLI to terminate immediately. > ------------------------------------------------------------------------------ > > Key: WFCORE-608 > URL: https://issues.jboss.org/browse/WFCORE-608 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Linux > Reporter: Jay Kumar SenSharma > Assignee: Alexey Loubyansky > Fix For: 1.0.0.CR4, 2.0.0.Alpha1 > > > - When using *[wildfly-8.2.0.Final]* When user has a '.inputrc' in the user home directory with the following content: > {code} > # Control characters > "\C-?": backward-delete-char > {code} > - The it fails with the the following Stack Trace: > {code} > ./jboss-cli.sh > java.lang.RuntimeException: ERROR parsing ? keys to aesh. Check your inputrc. > at org.jboss.aesh.edit.mapper.KeyMapper.convertRandomControlKeys(KeyMapper.java:161) > at org.jboss.aesh.edit.mapper.KeyMapper.mapRandomKeys(KeyMapper.java:138) > at org.jboss.aesh.edit.mapper.KeyMapper.mapKeys(KeyMapper.java:108) > at org.jboss.aesh.edit.mapper.KeyMapper.mapQuoteKeys(KeyMapper.java:49) > at org.jboss.aesh.console.Config.parseInputrc(Config.java:127) > at org.jboss.aesh.console.Console.reset(Console.java:150) > at org.jboss.aesh.console.Console.<init>(Console.java:105) > at org.jboss.aesh.console.Console.<init>(Console.java:101) > at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:85) > at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:78) > at org.jboss.as.cli.impl.CommandContextImpl.initBasicConsole(CommandContextImpl.java:349) > at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:296) > at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > {code} > - Expectation is that CLI should not have terminated suddenly rather the exception should have been handled in a proper way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-752) Only one deployment overlay can be created for each deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-752?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-752: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1229711, https://bugzilla.redhat.com/show_bug.cgi?id=1233287 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1229711) > Only one deployment overlay can be created for each deployment > -------------------------------------------------------------- > > Key: WFCORE-752 > URL: https://issues.jboss.org/browse/WFCORE-752 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.CR5, 2.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.CR6, 2.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4805) Distributable app causes TransferQueueBundler Invalid argument and Topology errors

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-4805?page=com.atlassian.jira.plugin.... ] Michal Babacek moved JBEAP-352 to WFLY-4805: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-4805 (was: JBEAP-352) Workflow: GIT Pull Request workflow (was: CDW v1) Affects Version/s: 10.0.0.Alpha4 (was: EAP 7.0.0.DR3) (was: EAP 7.0.0.DR4) Component/s: Clustering (was: Clustering) Target Release: (was: EAP 7.0.0.GA) > Distributable app causes TransferQueueBundler Invalid argument and Topology errors > ---------------------------------------------------------------------------------- > > Key: WFLY-4805 > URL: https://issues.jboss.org/browse/WFLY-4805 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha4 > Environment: Oracle JDK 1.8, Open JDK 1.8, RHEL 7 > Reporter: Michal Babacek > Assignee: Paul Ferraro > Attachments: clusterbench.war, configs.zip, logs.zip > > > Simple shutdown failover tests are failing due to apparent error in / misconfiguration of the distributed cache. > If one follows the aforementioned steps to reproduce, the following symptoms appear: > * Variations on {noformat}SEVERE [org.jgroups.protocols.UDP] (TransferQueueBundler,ee,rhel7gax86-64) JGRP000029: rhel7gax86-64: failed sending message to rhel7gax86-64 (59 bytes): java.io.IOException: Invalid argument, headers: UNICAST3: ACK, seqno=9410, ts=217, UDP: [cluster_name=ee]{noformat} > * Failures of this kind: {noformat}ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (transport-thread--p2-t12) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Timed out waiting for topology 11 > at org.infinispan.statetransfer.StateTransferLockImpl.waitForTransactionData(StateTransferLockImpl.java:92) > at org.infinispan.interceptors.base.BaseStateTransferInterceptor.waitForTransactionData(BaseStateTransferInterceptor.java:96) > at org.infinispan.statetransfer.StateTransferInterceptor.handleTxWriteCommand(StateTransferInterceptor.java:285) > at org.infinispan.statetransfer.StateTransferInterceptor.handleWriteCommand(StateTransferInterceptor.java:254) > at org.infinispan.statetransfer.StateTransferInterceptor.visitRemoveCommand(StateTransferInterceptor.java:130) > at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:58) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:97) > at org.infinispan.interceptors.CacheMgmtInterceptor.visitRemoveCommand(CacheMgmtInterceptor.java:209) > at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:58) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:97) > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:102) > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:71) > at org.infinispan.commands.AbstractVisitor.visitRemoveCommand(AbstractVisitor.java:49) > at org.infinispan.commands.write.RemoveCommand.acceptVisitor(RemoveCommand.java:58) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336) > at org.infinispan.cache.impl.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1617) > at org.infinispan.cache.impl.CacheImpl.removeInternal(CacheImpl.java:579) > at org.infinispan.cache.impl.CacheImpl.remove(CacheImpl.java:572) > at org.infinispan.cache.impl.DecoratedCache.remove(DecoratedCache.java:442) > at org.infinispan.cache.impl.AbstractDelegatingCache.remove(AbstractDelegatingCache.java:297) > at org.wildfly.clustering.server.registry.CacheRegistry.topologyChanged(CacheRegistry.java:152) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl$1.run(AbstractListenerImpl.java:286) > at org.infinispan.util.concurrent.WithinThreadExecutor.execute(WithinThreadExecutor.java:22) > at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl.invoke(AbstractListenerImpl.java:309) > at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.doRealInvocation(CacheNotifierImpl.java:1180) > at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.invoke(CacheNotifierImpl.java:1139) > at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.invoke(CacheNotifierImpl.java:1105) > at org.infinispan.notifications.cachelistener.CacheNotifierImpl.notifyTopologyChanged(CacheNotifierImpl.java:560) > at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:201) > at org.infinispan.statetransfer.StateTransferManagerImpl.access$000(StateTransferManagerImpl.java:45) > at org.infinispan.statetransfer.StateTransferManagerImpl$1.updateConsistentHash(StateTransferManagerImpl.java:113) > at org.infinispan.topology.LocalTopologyManagerImpl.doHandleTopologyUpdate(LocalTopologyManagerImpl.java:285) > at org.infinispan.topology.LocalTopologyManagerImpl$1.run(LocalTopologyManagerImpl.java:218) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:166) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:144) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745){noformat} > * Warnings such as: {noformat}WARN [org.infinispan.transaction.impl.TransactionTable] (TxCleanupService,dist,rhel7gax86-64) ISPN000326: Remote transaction GlobalTransaction:<rhel7gax86-64>:9373:remote timed out. Rolling back after 70810 ms{noformat} > Logs from one of such play & test scenarios are attached: [^logs.zip], [^configs.zip]. > Any ideas which configuration directive or application setting might be at the bottom of this? > Needless to say any such test passes without any error with EAP 6.4 and 6.3 both with shutdown and undeploy failover scenarios. > Thx for comments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1277) Data inconsistency for CMR when connection is broken after database resource commits - missing fix from EAP 6.4

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created JBJCA-1277: --------------------------------------- Summary: Data inconsistency for CMR when connection is broken after database resource commits - missing fix from EAP 6.4 Key: JBJCA-1277 URL: https://issues.jboss.org/browse/JBJCA-1277 Project: IronJacamar Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: Jesper Pedersen Fix of BZ#1181132 [1] for EAP 6.4 in ironjacamar is not ported to EAP7. IJ version under 6.4.0 is 1.0.31 and for 7.0.0.DR4 is 1.2.4 which are handled in different branches. It seems that fix with exception sorters was not moved there. As part of EAP 6.4 we have found issue for CMR where data inconsistency occurs. This happens when CMR db resource successfully commits but the connection is broken before TM receives confirmation about such state. As connection got broken XAException.XA_RBROLLBACK is thrown and TM decides to rollback whole XA transaction. That ends in situation where db resource was committed and other XA participants are rollbacked. Details are discussed at BZ#1181132 [1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1181132 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-4280: ------------------------------------ HV-861 is marked fixed in 5.2.0.Beta1, should we upgrade WildFly 10 (master) to use HV 5.2.0.Beta1? > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hibernate-validator-5.2.0-SNAPSHOT.jar, hv-861-1.0-SNAPSHOT.jar, hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-733) Unify Drools and jBPM execution servers

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-733?page=com.atlassian.jira.plugin... ] Edson Tirelli updated DROOLS-733: --------------------------------- Tester: Karel Suta > Unify Drools and jBPM execution servers > --------------------------------------- > > Key: DROOLS-733 > URL: https://issues.jboss.org/browse/DROOLS-733 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 6.2.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 6.3.0.Final > > > This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server. > The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM. > It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment. > Initial open questions include: > * support to databases and persistence: should this be a per-container configuration or per-kjar configuration? > * can a single deployment model be used for both drools and jbpm? > * how to apply the security model from jbpm? > * does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it? > * workbench UI consolidation for exec servers -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 June 2015