[JBoss JIRA] Created: (TEIID-1211) Refine load-balancing support in AS
by Steve Hawkins (JIRA)
Refine load-balancing support in AS
-----------------------------------
Key: TEIID-1211
URL: https://jira.jboss.org/browse/TEIID-1211
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1.1
In an AS connection pool, an XAConnection does not receive a notification of a connection.close, so our post-connection load-balancing logic will never kick in. For environments with a low/infrequent number of client connections, this will produce a poor load distribution.
Possible Solutions:
1. Ensure proper tracking of the transation state and switch servers after a commit/rollback. This however would also require that session level temporary tables are replicated (although that replication logic should be added as part of the materialization feature). And would cause potential cache misses or other minor issues with session level deterministic functions.
2. Promote the use of Teiid directly through our own DataSource and handle transaction enlist/delist logic appropriately. Users would instead use a jboss beans.xml file to create a named instance of the datasource in JNDI. The appeal of this solution is that it we are architected to not require the use of a pool (settings for max connections, statement pooling, are mostly irrelevant for local connections to Teiid). We have our own thread pooling, etc.
3. See if we can get some AS patch to also pass connection events to PooledConnections.
Another thing that may need addressed is runtime discovery of additional hosts, if not we could also add an option to pick up hosts and connection information from an external file.
--
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
[JBoss JIRA] Created: (TEIID-1188) Error while reading the template properties for LDAP
by Ramesh Reddy (JIRA)
Error while reading the template properties for LDAP
----------------------------------------------------
Key: TEIID-1188
URL: https://jira.jboss.org/browse/TEIID-1188
Project: Teiid
Issue Type: Bug
Components: LDAP Connector
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Minor
Fix For: 7.1
groovy:000> getTemplatePropertyDefinitions("connector-ldap");
ERROR org.teiid.adminapi.AdminComponentException:
Failed to find template for: translator-connector-ldap
at org.teiid.client.util.ExceptionUtil.convertException (ExceptionUtil.java:72)
at org.teiid.net.socket.SocketServerConnection$ServerConnectionInvocationHandler.invoke (SocketServerConnection.java:239)
at $Proxy7.getTemplatePropertyDefinitions (Unknown Source
--
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
[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, 7 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, 7 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, 7 months