[JBoss JIRA] Created: (TEIID-1220) Change Data Roles from a Global (server-wide) to a VDB-based property
by Paul Nittel (JIRA)
Change Data Roles from a Global (server-wide) to a VDB-based property
---------------------------------------------------------------------
Key: TEIID-1220
URL: https://jira.jboss.org/browse/TEIID-1220
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
Assignee: Steve Hawkins
By having Data Roles check server-wide, administrators are forced to create data roles for each VDB deployed, even if only for testing. (This is MetaMatrix legacy behavior.) What we're suggesting is this:
Data roles are enabled and disabled at the server level, but
A VDB will only be subject to roles checking if it has one, or more data role defined
This way, it is possible to deploy a VDB without roles checking and yet it remains possible to disable all roles checking by disabling it server-wide.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1191) Dynamic portfolio throws NullPointerException
by Boris Belovic (JIRA)
Dynamic portfolio throws NullPointerException
---------------------------------------------
Key: TEIID-1191
URL: https://jira.jboss.org/browse/TEIID-1191
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1
Reporter: Boris Belovic
Assignee: Steve Hawkins
Priority: Minor
I removed Account model from portfolio-vdb.xml (see attached file), then deployed marketdata-file-ds.xml and subsequent deployment of portfolio-vdb.xml caused NullPointerException
Here is a stacktrace from SOA-P 5.1 DEV2 build:
16:28:00,361 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=marketdata-file' to JNDI name 'java:marketdata-file'
16:28:10,485 INFO [RUNTIME] VDB "DynamicPortfolio-1" - "MarketData" model metadata is currently being loaded. Start Time: 8/9/10 4:28 PM
16:28:10,489 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/home/bbelovic/jbosssoa-51/jboss-as/server/production/deploy/portfolio-vdb.xml state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/bbelovic/jbosssoa-51/jboss-as/server/production/deploy/portfolio-vdb.xml
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at org.teiid.deployers.VDBDeployer.buildDynamicMetadataStore(VDBDeployer.java:322)
at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:118)
at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:61)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
... 24 more
16:28:10,503 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/home/bbelovic/jbosssoa-51/jboss-as/server/production/deploy/portfolio-vdb.xml -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/bbelovic/jbosssoa-51/jboss-as/server/production/deploy/portfolio-vdb.xml
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/home/bbelovic/jbosssoa-51/jboss-as/server/production/deploy/portfolio-vdb.xml" is in error due to the following reason(s): java.lang.NullPointerException
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
I am also attaching server.log files from plain JBoss AS and server.log from SOA-P 5.1 dev2 build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1232) Cannot create LDAP connection.
by John Doyle (JIRA)
Cannot create LDAP connection.
------------------------------
Key: TEIID-1232
URL: https://jira.jboss.org/browse/TEIID-1232
Project: Teiid
Issue Type: Bug
Components: LDAP Connector
Affects Versions: 7.1
Environment: Teiid 7.1 on RHEL 5.
Reporter: John Doyle
Assignee: Steve Hawkins
I'm trying to create an LDAP connection from Designer and getting an error. I think the package structure for the LDAPManagedConnectionFactory has changed. It's in /org/teiid/resource/adapter/ldap/ in the connector-ldap jar.
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/NotBackedUp/jdoyle/Teiid7.1Final/jboss-5.1.0.GA/server/default/deploy/ldap-ds.xml" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: Could not find ManagedConnectionFactory class: org.teiid.resource.cci.ldap.LDAPManagedConnectionFactory
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1159) Exception Creating Data Source Using Admin API
by Dan Florian (JIRA)
Exception Creating Data Source Using Admin API
----------------------------------------------
Key: TEIID-1159
URL: https://jira.jboss.org/browse/TEIID-1159
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 7.0
Environment: Macintosh OS X 10.6.4
Reporter: Dan Florian
Assignee: Steve Hawkins
Priority: Critical
>From Teiid Designer code I am calling AdminApi method createDataSource(String, String, Properties) but I get the below exceptions. One problem I see in the FileNotFoundException messages is that the application is looking for a path that has spaces where the file system actually has plus signs. So for instance, on the file system this folder does exist: /var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk+++TI/.
[AdminComponentException]Failed to process template.
1 [AdminComponentException]Failed to process template.
2 [RuntimeException]Failed to process template.
3 [FileNotFoundException]/var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml
at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72)
at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:191)
at $Proxy262.createDataSource(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187)
at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160)
at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149)
at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210)
at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:98)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:117)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:391)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: [AdminComponentException]Failed to process template.
1 [RuntimeException]Failed to process template.
2 [FileNotFoundException]/var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml
at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:630)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121)
at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:185)
... 36 more
Caused by: java.lang.RuntimeException: Failed to process template.
at org.jboss.profileservice.management.AbstractTemplateCreator.checkComplete(AbstractTemplateCreator.java:197)
at org.jboss.profileservice.management.AbstractTemplateCreator.distribute(AbstractTemplateCreator.java:164)
at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:102)
at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1361)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$3.applyTemplate(AOPProxy$3.java)
at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:626)
... 42 more
Caused by: java.io.FileNotFoundException: /var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml
at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:105)
at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:112)
at org.jboss.virtual.plugins.context.AbstractURLHandler.openStream(AbstractURLHandler.java:203)
at org.jboss.virtual.VirtualFile.openStream(VirtualFile.java:230)
at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93)
at java.net.URL.openStream(URL.java:1010)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:105)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:177)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:82)
at org.jboss.profileservice.management.AbstractTemplateCreator.distribute(AbstractTemplateCreator.java:161)
at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:102)
at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1361)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$3.applyTemplate(AOPProxy$3.java)
at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:626)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121)
at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:185)
at $Proxy262.createDataSource(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190)
at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187)
at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160)
at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149)
at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210)
at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:98)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:117)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:391)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
... 49 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1178) Jopr VDB loading error when Data Source is not available
by Ramesh Reddy (JIRA)
Jopr VDB loading error when Data Source is not available
--------------------------------------------------------
Key: TEIID-1178
URL: https://jira.jboss.org/browse/TEIID-1178
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.1
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.1
While loading a dynamic VDB, that does not have a DS file configured correctly or while the database is down, the following exception shows up when the "admin-console" is loaded.
java.lang.IllegalStateException: Deployment file ':/home/rareddy/testing/jboss-5.1.0.GA/server/default/deploy/teiid-artifacts/portfolio-vdb.xml' for Teiid Virtual Database does not exist.
at org.teiid.rhq.plugin.Facet.discoverDeployedPackages(Facet.java:429)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1219) Metadata for XML Document models not being showing up after Admin API mergeVDB() call.
by Barry LaFond (JIRA)
Metadata for XML Document models not being showing up after Admin API mergeVDB() call.
--------------------------------------------------------------------------------------
Key: TEIID-1219
URL: https://jira.jboss.org/browse/TEIID-1219
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1
Reporter: Barry LaFond
Assignee: Steve Hawkins
Testing the Preview Data feature in pre-7.1 Teiid Designer with 7.1 Teiid has resulted in errors previewing Web Service models because the XML Document model metadata isn't being being property merged and exposed.
The logged console exception is:
[PROCESSOR] Processing exception 'Group does not exist: PartsOracle_Output_View.PARTS_OutputView' for request 48+ANjgClxMi.0. Exception type org.teiid.api.exception.query.QueryPlannerException thrown from org.teiid.query.resolver.util.ResolverUtil.handleUnresolvedGroup(ResolverUtil.java:852). Enable more detailed logging to see the entire stacktrace.
Looking through Designer's DTP connection in data source explorer, it's appears that the XML Doc model isn't part of the VDB, so I'm assuming the merge doesn't property handle XML.
NOTE: that creating a real VDB from the SAME model set in Designer, then deploying, DOES show the model. Accessing the Metadata from Designer's JDBC Import connection shows that the XML Document nodes are there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1218) AdminShell help for changeVDBConnectionType is "Cancel a request"
by Paul Nittel (JIRA)
AdminShell help for changeVDBConnectionType is "Cancel a request"
-----------------------------------------------------------------
Key: TEIID-1218
URL: https://jira.jboss.org/browse/TEIID-1218
Project: Teiid
Issue Type: Bug
Components: Tools
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
Assignee: Steve Hawkins
Priority: Trivial
Start AdminShell and enter \ah (to get help). In the list, you'll see the following:
groovy:000> \ah
/* method(arg count) -- description */
addDataRoleMapping(4) -- Adds a role to the specified policy
adminHelp() -- Show help for all admin methods
adminHelp(1) -- Show help for the given admin method
assignToModel(6) -- Assign a translator and data source to a source Model
cancelRequest(2) -- Cancel a request
changeVDBConnectionType(3) -- Cancel a request
clearCache(1) -- Clear the given cache
It looks like a cut & paste error for the changeVDBConnectionType method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months