June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2533) ConcurrentModificationException when list-sessions operation is issued

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2533?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2533: ------------------------------------- It was trivial change, not sure why I was hesitant before. Made it into stateless. > ConcurrentModificationException when list-sessions operation is issued > ---------------------------------------------------------------------- > > Key: TEIID-2533 > URL: https://issues.jboss.org/browse/TEIID-2533 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: Teiid 8.4.CR2 and EAP 6.1 Alpha > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.4 > > > Saw the following exception in the server log, but not sure what I did to trigger it (unable to reproduce): > 07:31:32,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("list-sessions") failed - address: ([("subsystem" => "teiid")]): java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_13] > at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_13] > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:245) > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:225) > at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:72) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2533) ConcurrentModificationException when list-sessions operation is issued

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2533?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2533. --------------------------------- Labels: Final (was: ) Fix Version/s: 8.4 Resolution: Done Ideally this should not use any state in this class, but since that is going to be a bigger change I opted to just placing synchronized block around the methods and made proactive copy of the list where the exception occurred to avoid issues like this. > ConcurrentModificationException when list-sessions operation is issued > ---------------------------------------------------------------------- > > Key: TEIID-2533 > URL: https://issues.jboss.org/browse/TEIID-2533 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: Teiid 8.4.CR2 and EAP 6.1 Alpha > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.4 > > > Saw the following exception in the server log, but not sure what I did to trigger it (unable to reproduce): > 07:31:32,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("list-sessions") failed - address: ([("subsystem" => "teiid")]): java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_13] > at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_13] > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:245) > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:225) > at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:72) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2532) When the Infinisan connector obtains the cache needs to be corrected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2532?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2532: --------------------------------------- No, I can just do that locally. > When the Infinisan connector obtains the cache needs to be corrected > -------------------------------------------------------------------- > > Key: TEIID-2532 > URL: https://issues.jboss.org/browse/TEIID-2532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4, 8.5 > Reporter: Van Halbert > Assignee: Van Halbert > > The Infinispan connector needs to change when its obtaining the cache. Its currently only trying to get the cache from JNDI one time, but will change it to obtain it each time a connection is obtained. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2532) When the Infinisan connector obtains the cache needs to be corrected

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2532?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2532: ------------------------------------ Sorry. Yes. Can you easily back port it or do you want me to resubmit? > When the Infinisan connector obtains the cache needs to be corrected > -------------------------------------------------------------------- > > Key: TEIID-2532 > URL: https://issues.jboss.org/browse/TEIID-2532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4, 8.5 > Reporter: Van Halbert > Assignee: Van Halbert > > The Infinispan connector needs to change when its obtaining the cache. Its currently only trying to get the cache from JNDI one time, but will change it to obtain it each time a connection is obtained. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2398) Web console in domain mode loose active servers and shows just inactive ones

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2398?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2398: -------------------------------- Attachment: teiid-console-dist-1.1.0-SNAPSHOT-jboss-as7.zip This needs to used with EAP 6.1 alpha or Final > Web console in domain mode loose active servers and shows just inactive ones > ---------------------------------------------------------------------------- > > Key: TEIID-2398 > URL: https://issues.jboss.org/browse/TEIID-2398 > Project: Teiid > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2 > Environment: Centos 6.3, JBoss 7.1.1 TEIID 8.2, Java 1.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > Labels: console, domain, web > Fix For: 8.4 > > Attachments: teiid-console-dist-1.1.0-SNAPSHOT-jboss-as7.zip, teiid.png, teiid2.png, teiid3.png, teiid4.png, teiid5.png > > > I have a domain environment (for now just one host with both the domain controllere and tow servers instances) with two server groups and one servre in each group; it will be configured to be in HA. > I added the web console to the installation (copyed the stuff in the folder and hope this was the correct way of doing) > When I go to the runtime only the stopped server are present and canno select the running one. > This makes the console un-usable since not choosing the server stop all other activity with errors. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2398) Web console in domain mode loose active servers and shows just inactive ones

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2398?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2398: ------------------------------------- Luca, can you please give this zip a try and see if Teiid console is working. Thanks > Web console in domain mode loose active servers and shows just inactive ones > ---------------------------------------------------------------------------- > > Key: TEIID-2398 > URL: https://issues.jboss.org/browse/TEIID-2398 > Project: Teiid > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2 > Environment: Centos 6.3, JBoss 7.1.1 TEIID 8.2, Java 1.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > Labels: console, domain, web > Fix For: 8.4 > > Attachments: teiid-console-dist-1.1.0-SNAPSHOT-jboss-as7.zip, teiid.png, teiid2.png, teiid3.png, teiid4.png, teiid5.png > > > I have a domain environment (for now just one host with both the domain controllere and tow servers instances) with two server groups and one servre in each group; it will be configured to be in HA. > I added the web console to the installation (copyed the stuff in the folder and hope this was the correct way of doing) > When I go to the runtime only the stopped server are present and canno select the running one. > This makes the console un-usable since not choosing the server stop all other activity with errors. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2532) When the Infinisan connector obtains the cache needs to be corrected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2532?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2532: --------------------------------------- Just to make sure, you intended this for 8.4.x correct? > When the Infinisan connector obtains the cache needs to be corrected > -------------------------------------------------------------------- > > Key: TEIID-2532 > URL: https://issues.jboss.org/browse/TEIID-2532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4, 8.5 > Reporter: Van Halbert > Assignee: Van Halbert > > The Infinispan connector needs to change when its obtaining the cache. Its currently only trying to get the cache from JNDI one time, but will change it to obtain it each time a connection is obtained. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2532) When the Infinisan connector obtains the cache needs to be corrected

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2532?page=com.atlassian.jira.plugin... ] Work on TEIID-2532 stopped by Van Halbert. > When the Infinisan connector obtains the cache needs to be corrected > -------------------------------------------------------------------- > > Key: TEIID-2532 > URL: https://issues.jboss.org/browse/TEIID-2532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4, 8.5 > Reporter: Van Halbert > Assignee: Van Halbert > > The Infinispan connector needs to change when its obtaining the cache. Its currently only trying to get the cache from JNDI one time, but will change it to obtain it each time a connection is obtained. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2381) Expanded source hint support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ] Work on TEIID-2381 started by Steven Hawkins. > Expanded source hint support > ---------------------------- > > Key: TEIID-2381 > URL: https://issues.jboss.org/browse/TEIID-2381 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1 > > Attachments: HintsExecutionFactory.java, RandomExecutionFactory.java, RandomNumberStoredProcedureExecution.java, SysviewHintsExecutionTest.java > > > We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2533) ConcurrentModificationException when list-sessions operation is issued

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2533?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2533: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > ConcurrentModificationException when list-sessions operation is issued > ---------------------------------------------------------------------- > > Key: TEIID-2533 > URL: https://issues.jboss.org/browse/TEIID-2533 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: Teiid 8.4.CR2 and EAP 6.1 Alpha > Reporter: Van Halbert > Assignee: Ramesh Reddy > > Saw the following exception in the server log, but not sure what I did to trigger it (unable to reproduce): > 07:31:32,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("list-sessions") failed - address: ([("subsystem" => "teiid")]): java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_13] > at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_13] > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:245) > at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:225) > at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:72) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013