September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2649) NoClassDefFoundError when trying to run adminshell

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2649?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2649: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1004770|https://bugzilla.redhat.com/show_bug.cgi?id=1004770] from NEW to ASSIGNED > NoClassDefFoundError when trying to run adminshell > -------------------------------------------------- > > Key: TEIID-2649 > URL: https://issues.jboss.org/browse/TEIID-2649 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > adminshell is throwing the following exception when trying to be run: > Exception in thread "main" java.lang.NoClassDefFoundError: jline/History > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521) > at java.lang.Class.getDeclaredMethods(Class.java:1845) > at org.codehaus.groovy.reflection.CachedClass$3$1.run(CachedClass.java:83) > at java.security.AccessController.doPrivileged(Native Method) > at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:80) > at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:78) > at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) > at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) > at org.codehaus.groovy.reflection.CachedClass.getMethods(CachedClass.java:249) > at groovy.lang.MetaClassImpl.populateMethods(MetaClassImpl.java:341) > at groovy.lang.MetaClassImpl.fillMethodIndeMetaClassImpl.java:291) > at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:2912) > at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:166) > at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:182) > at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:210) > at org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:701) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallConstructorSite(CallSiteArray.java:69) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:52) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:192) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:200) > at org.codehaus.groovy.tools.shell.Main.main(Main.groovy:124) > at org.teiid.adminshell.GroovyAdminShell.main(GroovyAdminShell.java:30) > Caused by: java.lang.ClassNotFoundException: jline.History > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 23 more -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2650: ------------------------------------- Runtime version and Active Sessions are added as Runtime attributes of the Teiid Subsystem, so they are not part of the configuration like other attributes you see with the "read-resource". So, in the domain mode when you make a call {code} /profile=ha/subsystem=teiid:read-resource {code} it will only returns the configurable attributes. However, if you issue the command against a running node server like {code} /host=master/server=server-one/subsystem=teiid:read-resource {code} it will return right results, however there seems to another bug in AS code that is not being reported correctly. I see the invocations correctly. however, the correct way to look for attribute is to {code} /host=master/server=server-one/subsystem=teiid:read-attribute(name=runtime-version) {code} That does work! So, there is nothing Teiid can fix I can think of, unless we make this property static in the standalone.xml or domain.xml. The idea in AS is each server node could possibly running a different Teiid subsystem. Designer needs to probe first for available hosts, then select one, then probe for available servers under that group, then use equivalent to above to get the right version. > A jboss server in domain mode does not advertise its teiid runtime-version > -------------------------------------------------------------------------- > > Key: TEIID-2650 > URL: https://issues.jboss.org/browse/TEIID-2650 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version. > Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version. > However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'. > This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Yes, finidhDeployment may be much later than startup finish. I wish we could use based on metadata caching, but it is optional with Dynamic VDBs > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2584: --------------------------------------- > Ah. Then we'll need to undo the change I just made to rename the property from create to start. But won't isStartInProgress be misleading potentially? As our metadata loads are happening on an asynch basis even for index metadata. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2650: -------------------------------- Fix Version/s: 8.4.1 8.5 > A jboss server in domain mode does not advertise its teiid runtime-version > -------------------------------------------------------------------------- > > Key: TEIID-2650 > URL: https://issues.jboss.org/browse/TEIID-2650 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version. > Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version. > However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'. > This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2650: ----------------------------------- Assignee: Ramesh Reddy (was: Van Halbert) > A jboss server in domain mode does not advertise its teiid runtime-version > -------------------------------------------------------------------------- > > Key: TEIID-2650 > URL: https://issues.jboss.org/browse/TEIID-2650 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Ramesh Reddy > Priority: Blocker > > A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version. > Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version. > However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'. > This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2652) Dependencies set on OLAP translator's module.xml are incomplete

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2652?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2652: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1004892 > Dependencies set on OLAP translator's module.xml are incomplete > --------------------------------------------------------------- > > Key: TEIID-2652 > URL: https://issues.jboss.org/browse/TEIID-2652 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > The OLAP translator is missing dependency on OLAP4J library -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2652) Dependencies set on OLAP translator's module.xml are incomplete

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2652?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2652: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1004892|https://bugzilla.redhat.com/show_bug.cgi?id=1004892] from NEW to ASSIGNED > Dependencies set on OLAP translator's module.xml are incomplete > --------------------------------------------------------------- > > Key: TEIID-2652 > URL: https://issues.jboss.org/browse/TEIID-2652 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > The OLAP translator is missing dependency on OLAP4J library -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2652) Dependencies set on OLAP translator's module.xml are incomplete

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2652: ----------------------------------- Summary: Dependencies set on OLAP translator's module.xml are incomplete Key: TEIID-2652 URL: https://issues.jboss.org/browse/TEIID-2652 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.4.1, 8.5 The OLAP translator is missing dependency on OLAP4J library -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2651) Embedded missing dependencies

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2651?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2651. ----------------------------------- Resolution: Done Added the missing dependency. This was not seen in builds/tests as the staxmapper dependency was also being brought in by the cli via admin. > Embedded missing dependencies > ----------------------------- > > Key: TEIID-2651 > URL: https://issues.jboss.org/browse/TEIID-2651 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.5 > > > With TEIID-2444 the embedded kit no longer contained all of the dependencies needed by infinispan. -- 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

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013