[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3492:
---------------------------------------
> The one issue I can think here is the duplicated name of the translator/resource-adapter. Currently we do not have way to inject this from a configuration. Not sure how this affects? Do you think we need to support to have multiple translators simultaneously ?
Generally yes, you could need to support multiple versions. And I don't believe we can have the user change built-in parts of the module structure - that's a dangerous precedent.
One path with kitting multiple versions is that we explicitly have a v 22 and a v 34 translator / resource adapter. We can also provide the full instructions for creating custom translator / resource adapters that reference whatever version the user needs.
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
I started out with "34" and then renamed to "custom" such that user can use this to copy their API jars into this, rather than creating a additional module etc. My thinking is the user is going to be using at most yet one another version, so tried to limit the editing as much as possible for them. Another is if I leave as "34" Teiid will be pegging to another version, we need to maintain for eternity. So, here 34 is just an example.
New translator/connector is possible, if we can define separate modules for that, with different Partner API modules. The one issue I can think here is the duplicated name of the translator/resource-adapter. Currently we do not have way to inject this from a configuration. Not sure how this affects? Do you think we need to support to have multiple translators simultaneously ?
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3492:
---------------------------------------
Is it necessary to kit the custom jars and/or shouldn't we just call that slot 34 instead? Also wouldn't the expectation be that the user isn't altering the existing salesforce translator/connector, but rather copying and adding new ones?
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3492.
---------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Resolution: Done
I found a little hack in the build where I could add another version without much hassle to the build.
Designed the modules and their dependencies such that Partner API modules can be easily replaced with user's choice of API modules and update the translator and resource-adapter. This model will work as along as Salesforce keeps the compatibility of the API intact between version. If that is changed then this option will end up in errors during runtime.
Added version 34 as sample version to the build.
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3578:
-------------------------------------
[~shawkins] I believe the URL is created by the DV install script against the test H2 instance, than user configured
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3578:
------------------------------------
Sorry, wasn't clear. The 6.2 configuration default will be file based, using the async-handlers. Which we didn't do before.
I committed those 2 CLI scripts that will be used for default installation.
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3578:
---------------------------------------
> It sounds like our database logging option in general is a bad design. Definitely needs rethinking. And in 6.2, the default will be configuring the command/audit logging with async handlers.
It's not necessarily bad, it's just not something that should be used in production. And again it's not clear in this scenario what else is going wrong with the AS.
> 2) Change the overflow-action to "DISCARD", but in this situation the log messages will be lost
It would probably be best to default to error.
>From the startup log, the new startup contains errors not shown in the initial log:
Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set
Which appears to be the result of:
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1911)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:605)
Similarly dashboard could not make connections:
2015-07-17 10:47:36,818 [ServerService Thread Pool -- 61] WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
These errors are similar to ones seen in https://issues.jboss.org/browse/AGPUSH-890 and http://stackoverflow.com/questions/25257507/would-database-connection-lea...
More than likely you just have the wrong url.
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3578:
-------------------------------------
[~van.halbert]They are already ASYNC handlers. When the queue depth reaches to the maximum, then they lock up
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Jorge Herrera commented on TEIID-3578:
--------------------------------------
I have changed the overflow-action to "DISCARD" as you suggested. Will monitor and report back. I also attached the server.log with the startup sequence information, there are some exceptions regarding the teiid logging for your review.
Thanks,
Jorge.-
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Jorge Herrera updated TEIID-3578:
---------------------------------
Attachment: server_startup.log
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months