October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-1334) java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1334?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1334. --------------------------------- Resolution: Done URL class does not care about the spaces in its URL. It does not automatically encode them, However URI class does. Doing URL->URI->URL code to remove the spaces in the URL for System VDB from a JAR file. > java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1334 > URL: https://jira.jboss.org/browse/TEIID-1334 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Reporter: Barry LaFond > Assignee: Van Halbert > Fix For: 7.1.1 > > > Installed jboss-soa-p-5 in a folder under a "Test Designer Folder" folder. Installed EDS on top of it and ran the "ant" build to configure SOA for Teiid and Modeshape. > Installed JBDS and created/started an instance of JBoss AS server connection > On start-up got errrors: > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "VDBDeployer" is missing the following dependencies: > Dependency "SystemVDBDeployer" (should be in state "Create", but is actually in state "**ERROR**") > DEPLOYMENTS IN ERROR: > Deployment "SystemVDBDeployer" is in error due to the following reason(s): java.net.URISyntaxException: Illegal character in path at index 23: file:/home/blafond/Test Designer Folder/ServerInstalls/jboss-soa-p-5/jboss-as/server/default/deployers/teiid.deployer/teiid-metadata-7.1.1.jar/System.vdb, **ERROR** > I changed the containing folder and removed the spaces, restarted everything and did NOT receiver the error. > See attached file for Stack Trace. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1334) java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1334?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy updated TEIID-1334: -------------------------------- Fix Version/s: (was: 7.2) Affects Version/s: 7.1 Workaround Description: do not use folders with spaces for JBoss AS Workaround: [Workaround Exists] Complexity: Low Component/s: Server > java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1334 > URL: https://jira.jboss.org/browse/TEIID-1334 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Reporter: Barry LaFond > Assignee: Van Halbert > Fix For: 7.1.1 > > > Installed jboss-soa-p-5 in a folder under a "Test Designer Folder" folder. Installed EDS on top of it and ran the "ant" build to configure SOA for Teiid and Modeshape. > Installed JBDS and created/started an instance of JBoss AS server connection > On start-up got errrors: > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "VDBDeployer" is missing the following dependencies: > Dependency "SystemVDBDeployer" (should be in state "Create", but is actually in state "**ERROR**") > DEPLOYMENTS IN ERROR: > Deployment "SystemVDBDeployer" is in error due to the following reason(s): java.net.URISyntaxException: Illegal character in path at index 23: file:/home/blafond/Test Designer Folder/ServerInstalls/jboss-soa-p-5/jboss-as/server/default/deployers/teiid.deployer/teiid-metadata-7.1.1.jar/System.vdb, **ERROR** > I changed the containing folder and removed the spaces, restarted everything and did NOT receiver the error. > See attached file for Stack Trace. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1318) Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1318?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1318. --------------------------------- Resolution: Duplicate Issue This is error is not anything to do with the version. It was because of the null connection supplied to the WS translator. I suspect TEIID-1333 error here, where you configured a wrong DS name, that is not available, but VDB got flipped to active, thus you could make connection and issue a query. Since there is no active connection thus NPE. I verified the error with soa-p-5-ea3, and fixed for the next release. > Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1318 > URL: https://jira.jboss.org/browse/TEIID-1318 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Len DiMaggio > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > Attachments: interoperability-vdb.xml, interoperability2-vdb.xml, VDB_version_server.log > > > Server log is attached. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1318) Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1318?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy updated TEIID-1318: -------------------------------- Assignee: Ramesh Reddy Fix Version/s: 7.1.1 > Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1318 > URL: https://jira.jboss.org/browse/TEIID-1318 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Len DiMaggio > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > Attachments: interoperability-vdb.xml, interoperability2-vdb.xml, VDB_version_server.log > > > Server log is attached. -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1334) java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1334?page=com.atlassian.jira.plugin.s... ] Van Halbert moved SOA-2514 to TEIID-1334: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1334 (was: SOA-2514) Security: (was: Public) Component/s: (was: EDS) Fix Version/s: 7.1.1 7.2 (was: 5.1.0 GA) > java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1334 > URL: https://jira.jboss.org/browse/TEIID-1334 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Van Halbert > Fix For: 7.1.1, 7.2 > > > Installed jboss-soa-p-5 in a folder under a "Test Designer Folder" folder. Installed EDS on top of it and ran the "ant" build to configure SOA for Teiid and Modeshape. > Installed JBDS and created/started an instance of JBoss AS server connection > On start-up got errrors: > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "VDBDeployer" is missing the following dependencies: > Dependency "SystemVDBDeployer" (should be in state "Create", but is actually in state "**ERROR**") > DEPLOYMENTS IN ERROR: > Deployment "SystemVDBDeployer" is in error due to the following reason(s): java.net.URISyntaxException: Illegal character in path at index 23: file:/home/blafond/Test Designer Folder/ServerInstalls/jboss-soa-p-5/jboss-as/server/default/deployers/teiid.deployer/teiid-metadata-7.1.1.jar/System.vdb, **ERROR** > I changed the containing folder and removed the spaces, restarted everything and did NOT receiver the error. > See attached file for Stack Trace. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1325) Teiid Admin connection re-connect fails every time

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1325?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1325. --------------------------------- Resolution: Done Removed the code where the admin connection was setting to null. Now it should through an exception which will be handled by the tools properly. > Teiid Admin connection re-connect fails every time > -------------------------------------------------- > > Key: TEIID-1325 > URL: https://jira.jboss.org/browse/TEIID-1325 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Environment: F12, JBDS4.0.0-Beta1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > > 1) Start the Teiid Server (JBoss AS) then start the JBoss Tools with Teiid Designer. > 2) Configure the Designer to connect to Teiid Server using the Admin Connection. > 3) Make sure the it has valid connection > 4) Shutdown the Teiid Server > 5) Refresh the Teiid Connection in Desinger, which will fail to connect to server (expected as the Server is down) > 6) Now start the Server back up, and then using Designer, try to re-connect. This operation always fails with below exception > java.lang.NullPointerException > 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.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) > at $Proxy2.getTranslators(Unknown Source) > at org.teiid.designer.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:318) > at org.teiid.designer.runtime.ui.ReconnectToServerAction$1.run(ReconnectToServerAc > The only way to fix it discard the connection information, and create a new Teiid Instance. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1318) Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request

by Len DiMaggio (JIRA)

[ https://jira.jboss.org/browse/TEIID-1318?page=com.atlassian.jira.plugin.s... ] Len DiMaggio updated TEIID-1318: -------------------------------- Attachment: interoperability-vdb.xml interoperability2-vdb.xml > Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1318 > URL: https://jira.jboss.org/browse/TEIID-1318 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Len DiMaggio > Attachments: interoperability-vdb.xml, interoperability2-vdb.xml, VDB_version_server.log > > > Server log is attached. -- 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

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-1325) Teiid Admin connection re-connect fails every time

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1325?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy reassigned TEIID-1325: ----------------------------------- Assignee: Ramesh Reddy > Teiid Admin connection re-connect fails every time > -------------------------------------------------- > > Key: TEIID-1325 > URL: https://jira.jboss.org/browse/TEIID-1325 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Environment: F12, JBDS4.0.0-Beta1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > > 1) Start the Teiid Server (JBoss AS) then start the JBoss Tools with Teiid Designer. > 2) Configure the Designer to connect to Teiid Server using the Admin Connection. > 3) Make sure the it has valid connection > 4) Shutdown the Teiid Server > 5) Refresh the Teiid Connection in Desinger, which will fail to connect to server (expected as the Server is down) > 6) Now start the Server back up, and then using Designer, try to re-connect. This operation always fails with below exception > java.lang.NullPointerException > 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.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) > at $Proxy2.getTranslators(Unknown Source) > at org.teiid.designer.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:318) > at org.teiid.designer.runtime.ui.ReconnectToServerAction$1.run(ReconnectToServerAc > The only way to fix it discard the connection information, and create a new Teiid Instance. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1325) Teiid Admin connection re-connect fails every time

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1325?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-1325: ---------------------------------- Fix Version/s: 7.1.1 Affects Version/s: 7.1.1 (was: 7.1) It looks like the issue is caused by the reconnection logic being removed from the admin proxy. Setting the admin to null now causes the npe rather than triggering a npe > Teiid Admin connection re-connect fails every time > -------------------------------------------------- > > Key: TEIID-1325 > URL: https://jira.jboss.org/browse/TEIID-1325 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Environment: F12, JBDS4.0.0-Beta1 > Reporter: Ramesh Reddy > Fix For: 7.1.1 > > > 1) Start the Teiid Server (JBoss AS) then start the JBoss Tools with Teiid Designer. > 2) Configure the Designer to connect to Teiid Server using the Admin Connection. > 3) Make sure the it has valid connection > 4) Shutdown the Teiid Server > 5) Refresh the Teiid Connection in Desinger, which will fail to connect to server (expected as the Server is down) > 6) Now start the Server back up, and then using Designer, try to re-connect. This operation always fails with below exception > java.lang.NullPointerException > 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.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) > at $Proxy2.getTranslators(Unknown Source) > at org.teiid.designer.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:318) > at org.teiid.designer.runtime.ui.ReconnectToServerAction$1.run(ReconnectToServerAc > The only way to fix it discard the connection information, and create a new Teiid Instance. -- 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

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1325) Teiid Admin connection re-connect fails every time

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1325?page=com.atlassian.jira.plugin.s... ] Steven Hawkins moved TEIIDDES-681 to TEIID-1325: ------------------------------------------------ Project: Teiid (was: Teiid Designer) Key: TEIID-1325 (was: TEIIDDES-681) Affects Version/s: 7.1 (was: 7.1) Component/s: AdminApi (was: Teiid Integration) > Teiid Admin connection re-connect fails every time > -------------------------------------------------- > > Key: TEIID-1325 > URL: https://jira.jboss.org/browse/TEIID-1325 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1 > Environment: F12, JBDS4.0.0-Beta1 > Reporter: Ramesh Reddy > Fix For: 7.1.1 > > > 1) Start the Teiid Server (JBoss AS) then start the JBoss Tools with Teiid Designer. > 2) Configure the Designer to connect to Teiid Server using the Admin Connection. > 3) Make sure the it has valid connection > 4) Shutdown the Teiid Server > 5) Refresh the Teiid Connection in Desinger, which will fail to connect to server (expected as the Server is down) > 6) Now start the Server back up, and then using Designer, try to re-connect. This operation always fails with below exception > java.lang.NullPointerException > 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.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) > at $Proxy2.getTranslators(Unknown Source) > at org.teiid.designer.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:318) > at org.teiid.designer.runtime.ui.ReconnectToServerAction$1.run(ReconnectToServerAc > The only way to fix it discard the connection information, and create a new Teiid Instance. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010