[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, 6 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, 6 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, 6 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, 6 months
[JBoss JIRA] Created: (TEIID-1216) Cannot pass xml result from one select as critera to another select
by John Doyle (JIRA)
Cannot pass xml result from one select as critera to another select
-------------------------------------------------------------------
Key: TEIID-1216
URL: https://jira.jboss.org/browse/TEIID-1216
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1
Environment: Teiid 7.1 CR2 on RHEL 5
Reporter: John Doyle
Assignee: Steve Hawkins
I've created a VDB with procedures to create and parse XML, as wall as one to invoke the WS connector. SQL that unites them all into a single call passing the created XML into the invoke procedure is failing:
SELECT t.* FROM table (EXEC cis.CountryInfoServiceXML.CapitalCity.create_CapitalCity('US')) AS request, table (EXEC CountryInfoService.invoke('SOAP11', '', request.xml_out, 'http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso')) AS response, table (EXEC cis.CountryInfoServiceXML.CapitalCity.extract_CapitalCityResponse(RESPONSE.result)) AS t;
13:23:02,501 ERROR [PROCESSOR] Unexpected exception for request wHnSpxDdmkGB.5
[TeiidComponentException] ERR.015.006.0033: Error Code:ERR.015.006.0033 Message:Unable to evaluate request.xml_out: No value was available
at org.teiid.query.util.CommandContext.getFromContext(CommandContext.java:389)
at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:629)
--
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, 6 months
[JBoss JIRA] Created: (TEIID-1245) exception trying to get a test connection through admin console to a text file based connection factory
by Aleksandar Kostadinov (JIRA)
exception trying to get a test connection through admin console to a text file based connection factory
-------------------------------------------------------------------------------------------------------
Key: TEIID-1245
URL: https://jira.jboss.org/browse/TEIID-1245
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1
Environment: RHEL5, openjdk, SOA-P 5.1dev3
Reporter: Aleksandar Kostadinov
Assignee: Steven Hawkins
Attachments: exception.txt
I'm not completely sure there is a bug and if it is in teiid or admin console but it looks like a confusing behavior. When someone deploys a text file based connection factory like this attached to TEIID-1242 and without modifying login-config.xml, then trying to get a test connection results in an exception in the server log (see attached exception.txt).
If login-config.xml is modified to have the "other" application policy be the same as the "soa" policy, then this error does not appear in the server log. I'm not sure where should policy name be configured but IMHO user should be able to perform admin console actions by default given she/he is logged in as admin to the console.
--
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, 7 months