[JBoss JIRA] (TEIIDDES-2404) "Preview Data" throws Exception, when user select jdbc driver which is not located under C dirive
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2404?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2404 at 12/2/14 4:02 PM:
-----------------------------------------------------------------
The jar list string property from Data Tools profiles have different delimiters depending on OS.
For Linux the jar paths are delimited with a colon >>> *:*
{code:xml}
<property name="jarList" value="/home/blafond/drivers/classes12_g.jar:/home/blafond/drivers/db2jcc4.jar:/home/blafond/drivers/sqljdbc.jar"/>
{code}
For Windows the jar paths are delimited with a semi-colon >>> *;*
{code:xml}
<property name="jarList" value="C:\users\blafond\drivers\classes12_g.jar;C:\users\blafond\drivers\db2jcc4.jar;C:\users\blafond\drivers\sqljdbc.jar"/>
{code}
The ExecutionAdmin deployJars() method splits the jarList string using only the colon, so in this use-case, with one jar, the drive letter is treated as a separate jar, hence nothing get's deployed.
{code:java}
private void deployJars(Admin admin, String jarList) {
// Path Entries are colon separated
String[] jarPathStrs = jarList.split("[:]"); //$NON-NLS-1$
{code}
[~phantomjinx] I rather not do an OS check here, but it'll work in this case. Any ideas on another solution?
was (Author: blafond):
The jar list string property from Data Tools profiles have different delimiters depending on OS.
For Linux the jar paths are delimited with a colon >>> *:*
{code:xml}
<property name="jarList" value="/home/blafond/drivers/classes12_g.jar:/home/blafond/drivers/db2jcc4.jar:/home/blafond/drivers/sqljdbc.jar"/>
{code}
For Windows the jar paths are delimited with a semi-colon >>> *;*
{code:xml}
<property name="jarList" value="C:\users\blafond\drivers\classes12_g.jar;C:\users\blafond\drivers\db2jcc4.jar;C:\users\blafond\drivers\sqljdbc.jar"/>
{code}
The ExecutionAdmin deployJars() method splits the jarList string using only the colon, so in this use-case, with one jar, the drive letter is treated as a separate jar, hence nothing get's deployed.
{code:java}
private void deployJars(Admin admin, String jarList) {
// Path Entries are colon separated
String[] jarPathStrs = jarList.split("[:]"); //$NON-NLS-1$
{code}
> "Preview Data" throws Exception, when user select jdbc driver which is not located under C dirive
> -------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2404
> URL: https://issues.jboss.org/browse/TEIIDDES-2404
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 8.3.4
> Environment: - Windows 7
> - Teiid Designer 8.3.4.Final-v20140912-1304-B264 (JBDSIS 7.0.3)
> Reporter: hisao furuichi
>
> When user select/use a jdbc driver which is not located Under C drive, "preview data" thows TEIID30504 Exception.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2404) "Preview Data" throws Exception, when user select jdbc driver which is not located under C dirive
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2404?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2404:
----------------------------------------
The jar list string property from Data Tools profiles have different delimiters depending on OS.
For Linux the jar paths are delimited with a colon >>> *:*
{code:xml}
<property name="jarList" value="/home/blafond/drivers/classes12_g.jar:/home/blafond/drivers/db2jcc4.jar:/home/blafond/drivers/sqljdbc.jar"/>
{code}
For Windows the jar paths are delimited with a semi-colon >>> *;*
{code:xml}
<property name="jarList" value="C:\users\blafond\drivers\classes12_g.jar;C:\users\blafond\drivers\db2jcc4.jar;C:\users\blafond\drivers\sqljdbc.jar"/>
{code}
The ExecutionAdmin deployJars() method splits the jarList string using only the colon, so in this use-case, with one jar, the drive letter is treated as a separate jar, hence nothing get's deployed.
{code:java}
private void deployJars(Admin admin, String jarList) {
// Path Entries are colon separated
String[] jarPathStrs = jarList.split("[:]"); //$NON-NLS-1$
{code}
> "Preview Data" throws Exception, when user select jdbc driver which is not located under C dirive
> -------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2404
> URL: https://issues.jboss.org/browse/TEIIDDES-2404
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 8.3.4
> Environment: - Windows 7
> - Teiid Designer 8.3.4.Final-v20140912-1304-B264 (JBDSIS 7.0.3)
> Reporter: hisao furuichi
>
> When user select/use a jdbc driver which is not located Under C drive, "preview data" thows TEIID30504 Exception.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2125) REST procedures created in designer prior to version 8, don't transfer the properties
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2125?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2125:
--------------------------------------
Assignee: Barry LaFond (was: Ted Jones)
> REST procedures created in designer prior to version 8, don't transfer the properties
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2125
> URL: https://issues.jboss.org/browse/TEIIDDES-2125
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework
> Affects Versions: 8.3
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> If you migrate models containing REST procedures from version 7.7.x the values for rest Method and URI do not display in designer 8.3. They are still in the xmi file but it seems the key names have changed. If I edit the xmi file and change the key names the values for the properties then show in the Designer.
> key="rest:uri" is now key="REST:URI"
> And
> key="rest:restMethod" is now key="REST:METHOD"
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2224) web service returns 500 when concurrent access
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2224?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2224:
-----------------------------------
Fix Version/s: 8.6.1
9.0.1
9.0
(was: 8.6)
> web service returns 500 when concurrent access
> ----------------------------------------------
>
> Key: TEIIDDES-2224
> URL: https://issues.jboss.org/browse/TEIIDDES-2224
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.5
> Reporter: Hisanobu Okuda
> Assignee: Ted Jones
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: reproducer.tar.gz
>
>
> Description of problem:
> web service returns 500 when concurrent access. It works fine with a single access.
> Version-Release number of selected component (if applicable):
> How reproducible:
> Please find the attached reproducer kit reproducer.tar.gz which contains
> reproducer
> ├── accounts.csv // data source
> ├── command.log // test result
> ├── SampleJDV.zip // project source code
> ├── server.log // test result
> ├── SOAP_TEST2.jmx // config file for JMeter
> ├── WSTest.vdb // VDB which contains web service model
> └── WSTest.war // generated JBossWS-CXF War
> Steps to Reproduce:
> 0. add user/user in teiid-security-users.properties
> 1. add datasource in standalone.xml
> <datasource jndi-name="java:/WSTest" pool-name="WSTest" enabled="true">
> <connection-url>jdbc:teiid:WSTest</connection-url>
> <driver>teiid</driver>
> <pool>
> <min-pool-size>100</min-pool-size>
> <max-pool-size>100</max-pool-size>
> <use-strict-min>true</use-strict-min>
> </pool>
> <security>
> <user-name>user</user-name>
> <password>user</password>
> </security>
> 2. unjar WSTest.vdb, change the path to accounts.csv in SampleJDV/sandbox/WSTest_Source.xmi, rejar WSTest.vdb.
> 3. deploy WSTest.vdb
> 4. deploy WSTest.war
> 5. run jmeter, and open SOAP_TEST2.jmx
> 6. run test on jmeter
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2403) Relax BIRT version range to 4.4.0 from 4.4.1
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2403?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2403.
------------------------------------
Resolution: Done
tested installing 9.0.0.Beta1. Successful.
> Relax BIRT version range to 4.4.0 from 4.4.1
> --------------------------------------------
>
> Key: TEIIDDES-2403
> URL: https://issues.jboss.org/browse/TEIIDDES-2403
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Affects Versions: 9.0.1
> Reporter: Paul Leacu
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 9.0.1, 9.0
>
>
> The JBT unified TP 4.41.0.Final pulls in BIRT 4.4.0. It can't pull in BIRT 4.4.1 until after SR1 goes final. The associated JBTIS/ JBDSIS TPs must back off to 4.4.0 (from 4.4.1) its BIRT plugins if we want to install into Eclipse SR0 cleanly or we will have to forge an Eclipse SR1 remediation dialog for it (messy). So - since JBTIS TP must go .Final before we can legally pull in a 4.4.1 Birt, please:
> Update meta-data ranges and feature references of BIRT 4.4.1 to use/include 4.4.0.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2278) Starting server in JBDS(TD) gets stuck on "Performing pre-launch check" (Win 8.1)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2278?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2278.
------------------------------------
Resolution: Out of Date
> Starting server in JBDS(TD) gets stuck on "Performing pre-launch check" (Win 8.1)
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2278
> URL: https://issues.jboss.org/browse/TEIIDDES-2278
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: JBDS.log, screen.png, server.log
>
>
> When I try to start server in JBDS, it gets stuck on "Performing pre-launch check..."
> Not all translators are loaded (for example, translator "ws") so I can not use some VDBs.
> I tried to completely reinstall DV and also JBDS + Teiid Designer, it didn't help.
> WINDOWS 8.1
> JBDS 7.1.1.GA
> Teiid Designer 8.3.3.Final-v20140613-1202-B88
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2288) "Starting JBoss EAP 6.1+...e Server" stays 0% on Windows
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2288?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2288.
------------------------------------
Resolution: Out of Date
> "Starting JBoss EAP 6.1+...e Server" stays 0% on Windows
> --------------------------------------------------------
>
> Key: TEIIDDES-2288
> URL: https://issues.jboss.org/browse/TEIIDDES-2288
> Project: Teiid Designer
> Issue Type: Bug
> Components: Eclipse Integration
> Affects Versions: 8.3.3
> Environment: - Windows
> - JDK 1.7.0_62
> - JDV 6.0.0
> - JBDS 7.1.0
> - JBDS-7.1.1/jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip
> Reporter: Hisanobu Okuda
> Assignee: Paul Richardson
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> A server status "Starting JBoss EAP 6.1+...e Server" which is shown in the right-bottom in the JBDS window stays 0%, when clicking "Restart the server (Ctrl+Alt+R)" button, and does not go to 100%. The issue occurs on only Windows, but not on Linux.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIIDDES-2222) Verify Teiid version discovery with remote servers
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2222?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2222.
------------------------------------
Resolution: Out of Date
> Verify Teiid version discovery with remote servers
> --------------------------------------------------
>
> Key: TEIIDDES-2222
> URL: https://issues.jboss.org/browse/TEIIDDES-2222
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> Description of problem from Jason Stokes below. Need to test teiid version discovery with remote servers.
> We had a problem connecting to a TEIID/DV 6.0 instance on Amazon AWS via Jboss Dev Studio. (Never fully figured out why.) So we FTP'd our VDB we created in Teiid designer 8.5 and deployed it via the Jboss console. I
> forget the error, but something about incompatible versions.
> For whatever reason, JB Dev studio 7.1.1 (with 8.5 teiid designer) was
> reporting that the TEIID version of the AWS server was 8.6, even though it
> was 8.4. (As far as I know, they didn't do anything different but install
> it.) So the consensus was there was a mismatch between the fact we created a TEIID 8.4 version VDB and were trying to deploy it on the AWS server. (The local server I was testing with reported the correct version of TEIID 8.4 in dev studio.) Technically both installs should have been the same version though (8.4) so not sure what was going on.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month