1 2 Previous Next 15 Replies Latest reply on Aug 26, 2014 8:05 AM by Steven Hawkins

    jboss eap 6.2+ teiid 8.8

    文芳 张 Newbie

      Now i use JBOSS EAP 6.2-GA with teiid 8.8 , when i start JBOSS, it occurs following problem:

       

      16:47:30,174 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.teiid

              at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:607) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:485) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:269) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:291) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.server.ServerService.boot(ServerService.java:349) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.server.ServerService.boot(ServerService.java:324) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

      Caused by: java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.jboss.as.controller.OperationDefinition.<init>(Ljava/lang/String;Lorg/jboss/as/controller/registry/OperationEntry$EntryType;Ljava/util/EnumSet;Lorg/jboss/dmr/ModelType;Lorg/jboss/dmr/ModelType;ZLorg/jboss/as/controller/DeprecationData;[Lorg/jboss/as/controller/AttributeDefinition;[Lorg/jboss/as/controller/AttributeDefinition;)V

              at java.util.concurrent.FutureTask.report(FutureTask.java:122) [rt.jar:1.7.0_51]

              at java.util.concurrent.FutureTask.get(FutureTask.java:188) [rt.jar:1.7.0_51]

              at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              ... 10 more

      Caused by: java.lang.NoSuchMethodError: org.jboss.as.controller.OperationDefinition.<init>(Ljava/lang/String;Lorg/jboss/as/controller/registry/OperationEntry$EntryType;Ljava/util/EnumSet;Lorg/jboss/dmr/ModelType;Lorg/jboss/dmr/ModelType;ZLorg/jboss/as/controller/DeprecationData;[Lorg/jboss/as/controller/AttributeDefinition;[Lorg/jboss/as/controller/AttributeDefinition;)V

              at org.teiid.jboss.ListVDBs$1.<init>(TeiidOperationHandler.java:1033)

              at org.teiid.jboss.ListVDBs.getOperationDefinition(TeiidOperationHandler.java:1033)

              at org.teiid.jboss.BaseOperationHandler.register(BaseOperationHandler.java:60)

              at org.teiid.jboss.TeiidSubsytemResourceDefinition.registerOperations(TeiidSubsytemResourceDefinition.java:48)

              at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:151) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.extension.ExtensionRegistry$SubsystemRegistrationImpl.registerSubsystemModel(ExtensionRegistry.java:671) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.teiid.jboss.TeiidExtension.initialize(TeiidExtension.java:52)

              at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

              at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

              at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

              at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]

       

       

      16:47:30,190 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

       

      i'm wondering thart if there have some version match problems? And any JBOSS EAP 6+ can use teiid 8.4 +? and if i want to use a stable version JBOSS with teiid 8.8 ,which version is beterr?

      thanks.

        • 1. Re: jboss eap 6.2+ teiid 8.8
          Steven Hawkins Master

          It is not possible to mix and match Teiid and EAP versions.  The EAP/AS apis have version specific changes, so we just target the Teiid releases accordingly.  Teiid 8.8 is intended for EAP 6.1 Alpha.  You may contact support about where to get the productized versions of Teiid intended to target EAP 6.1 Final and EAP 6.3.

          • 2. Re: jboss eap 6.2+ teiid 8.8
            Ramesh Reddy Master

            To explain further, JBoss EAP 6.2 license is not LGPL. Teiid will not provide any community releases of Teiid, like version 8.7, 8.8 ..8.x on software that does not meet the it's license requirements.  Redhat does provide a product called Redhat JBoss Data Virtualiation, that is based on JBoss EAP 6.x versions and Teiid. The license on it is a different from LGPL, which is free to use in development but you would need to buy subscription from Redhat if you want to use in production.

             

            Ramesh..

            • 3. Re: Re: jboss eap 6.2+ teiid 8.8
              文芳 张 Newbie

              i tried JBOSS EAP 6.1 Alpha.with teiid 8.8,and it can startup successful ,but when i use a vdb ,it still occurs error:

               

              14:06:19,238 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1)  JBAS018565: Replaced deployment "MyTest-vdb.xml" with deployment "MyTest-vdb.xml"

              14:06:19,349 INFO  [org.teiid.CONNECTOR] (teiid-async-threads - 2)  SybaseExecutionFactory Commit=true;DatabaseProductName=Sybase IQ;DatabaseProductVersion=Sybase IQ/15.4.0.6567/111107/P/GA/Enterprise Linux64 - x86_64 - 2.6.9-67.0.4.ELsmp/64bit/2011-11-07 00:40:24;DriverMajorVersion=7;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/7.00(Build 26544)/P/EBF19093/JDK16/Fri May 13  4:16:47 2011;IsolationLevel=1

              14:06:51,770 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 2)  TEIID50030 VDB MyTest.1 model "sybiq" metadata loaded. End Time: 8/19/14 2:06 PM

              14:06:51,982 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2)  TEIID31152 More the one constraint with the name sybiq.dmpiq2.SYS.ISYSFKEY.ISYSIDX001.

              14:06:51,983 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2)  TEIID31152 More the one constraint with the name sybiq.dmpiq2.SYS.ISYSIDX.ISYSIDX_unique.

              14:06:51,983 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2)  TEIID31152 More the one constraint with the name sybiq.dmpiq2.SYS.ISYSIQIDX.ISYSIDX001.

              14:06:51,983 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2)  TEIID31152 More the one constraint with the name sybiq.dmpiq2.SYS.ISYSIQJOINIXCOLUMN.ISYSTABCOL001.

              14:06:51,984 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2)  TEIID31152 More the one constraint with the name sybiq.dmpiq2.SYS.ISYSTABCOL.ISYSTABCOL_unique.

              14:06:51,986 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 2)  TEIID40073 The metadata for the VDB MyTest.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.

              14:06:51,986 INFO  [org.teiid.RUNTIME.VDBLifeCycleListener] (teiid-async-threads - 2)  TEIID40003 VDB MyTest.1 is set to FAILED

               

              and following is my vdb configuration:

               

              <vdb name="MyTest" version="1">

              <description>My Test sybiq VDB</description>

              <property name="UseConnectorMetadata" value="cached" />

               

                      <model visible="true" type="PHYSICAL"  name="sybiq">

                              <property name="importer.useFullSchemaName" value="true"/>

                              <property name="importer.excludeTables" value="test"/>

                              <property name="supports-multi-source-bindings" value="true"/>

                              <source name="sybiq88" translator-name="sybase" connection-jndi-name="java:sybiq88DS"/>

                              <source name="sybiq85" translator-name="sybase" connection-jndi-name="java:sybiq85DS"/>

                      </model>

              </vdb>

               

              i don't know  what the problem is ? i can use this configuration in jboss AS 7.1 successfully.

              • 4. Re: Re: jboss eap 6.2+ teiid 8.8
                Ramesh Reddy Master

                I think you should only import the schema that has user tables and exclude the system tables. You can specify importer property like below to achieve it

                 

                <property name = "importer.schemaPattern" value ="my-schema"/>

                 

                Ramesh..

                1 of 1 people found this helpful
                • 5. Re: Re: jboss eap 6.2+ teiid 8.8
                  Steven Hawkins Master

                  There is a change starting in Teiid 8.4 - Teiid Designer requested that we validate against allowing multiple constraints with the same name:  [TEIID-2922] Extra unique constraint in dynamic vdb schema - JBoss Issue Tracker

                   

                  We do check to ensure that the primary key is not also reported as an index, but sybase system tables may have their metadata reported oddly.  As Ramesh says it would be best exclude these tables if they are not needed.

                  • 6. Re: Re: Re: jboss eap 6.2+ teiid 8.8
                    文芳 张 Newbie

                    after i update the vdb , it start success, but when i use vdb via JBDC, it also have errors:

                     

                    15:32:25,470 WARN  [org.teiid.SECURITY] (New I/O worker #6) null TEIID40011 Processing exception 'TEIID50072 The username "user" and/or password and/or payload token could not be authenticated by any membership domain.' for session null.  Exception type org.teiid.client.security.LogonException thrown from org.teiid.jboss.JBossSessionService.authenticate(JBossSessionService.java:78). Enable more detailed logging to see the entire stacktrace.

                    15:32:25,538 WARN  [org.teiid.TRANSPORT] (New I/O worker #6) null TEIID40113 Unhandled exception, aborting operation: java.io.IOException: Broken pipe

                     

                    and following is my connection code:

                     

                    String url = "jdbc:teiid:MyTest@mm://192.168.7.88:31000";

                        String sql ="select hour(start_time) as start_time, count(*) cnt from GPRS_USER_SERVICE_BDR131231 where roam_city=20 Group by hour(start_time)";

                        try

                          {

                          Class.forName("org.teiid.jdbc.TeiidDriver").newInstance();

                          Connection connection = DriverManager.getConnection(url, "user", "user");

                          Statement statement = connection.createStatement();

                     

                    and i didn't change anything for default user,so i user user/user. but what's the problem?

                    • 7. Re: Re: Re: jboss eap 6.2+ teiid 8.8
                      Ramesh Reddy Master

                      See https://issues.jboss.org/browse/TEIID-3013

                       

                      There is announcement banner on the forum "Teiid User/password" not working?? see Teiid

                      1 of 1 people found this helpful
                      • 8. Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                        文芳 张 Newbie

                        thanks Ramesh Reddy very much , i can query vdb , but there have some warning when i query vdb every time,

                         

                        14:44:00,628 WARN  [org.teiid.TRANSPORT] (New I/O worker #7) null TEIID40113 Unhandled exception, aborting operation: java.io.IOException: Broken pipe

                                at sun.nio.ch.FileDispatcherImpl.write0(Native Method) [rt.jar:1.7.0_25]

                                at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) [rt.jar:1.7.0_25]

                                at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:94) [rt.jar:1.7.0_25]

                                at sun.nio.ch.IOUtil.write(IOUtil.java:51) [rt.jar:1.7.0_25]

                                at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:466) [rt.jar:1.7.0_25]

                                at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:198) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:145) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.handler.stream.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:280) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:121) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.Channels.write(Channels.java:725) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.teiid.transport.ObjectEncoder.handleDownstream(ObjectEncoder.java:140) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final]

                                at org.jboss.netty.channel.Channels.write(Channels.java:704) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.Channels.write(Channels.java:671) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.teiid.transport.SSLAwareChannelHandler$ObjectChannelImpl.write(SSLAwareChannelHandler.java:93) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final]

                                at org.teiid.transport.SocketClientInstance.exceptionOccurred(SocketClientInstance.java:117) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final]

                                at org.teiid.transport.SSLAwareChannelHandler.exceptionCaught(SSLAwareChannelHandler.java:199) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final]

                                at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:377) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:74) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

                                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

                                at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

                         

                         

                        14:44:00,630 WARN  [org.teiid.TRANSPORT] (New I/O worker #7) null TEIID40113 Unhandled exception, aborting operation: java.io.IOException: Connection reset by peer

                                at sun.nio.ch.FileDispatcherImpl.read0(Native Method) [rt.jar:1.7.0_25]

                                at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) [rt.jar:1.7.0_25]

                                at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225) [rt.jar:1.7.0_25]

                                at sun.nio.ch.IOUtil.read(IOUtil.java:193) [rt.jar:1.7.0_25]

                                at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375) [rt.jar:1.7.0_25]

                                at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]

                                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

                                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

                                at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

                         

                        if i have some incorrect operation?

                        • 9. Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                          Ramesh Reddy Master

                          Close your JDBC connections after you are done using them, the above will go away

                          • 10. Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                            Ramesh Reddy Master

                            Or you may be using wrong JDBC jar version (old) than what came with installation.

                            • 11. Re: Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                              文芳 张 Newbie

                              i have tried to close the connection and alos i use the new jdbc version(jboss eap 6.1 GA+teiid 8.8 + teiid  jdbc 8.8.0 final). and it still occurs warnings,following is my client code:

                              package teiid_jdbc;

                              import java.sql.Connection;

                              import java.sql.DriverManager;

                              import java.sql.ResultSet;

                              import java.sql.SQLException;

                              import java.sql.Statement;

                              import java.text.SimpleDateFormat;

                              import java.util.Date;

                              import org.teiid.client.plan.PlanNode;

                              import org.teiid.jdbc.TeiidStatement;

                                public class teiid_test {

                                  public static void main(String[] args)

                                  {

                                  int i=0 ;

                                String url = "jdbc:teiid:MyTest@mm://192.168.7.88:31000";

                                    String sql ="select hour(start_time) start_time, count(*) cnt from GPRS_USER_SERVICE_BDR131231 where roam_city=20 Group by hour(start_time)";

                                    try

                                    {

                                    Class.forName("org.teiid.jdbc.TeiidDriver").newInstance();

                                    Connection connection = DriverManager.getConnection(url, "user", "user_123");

                                    Statement statement = connection.createStatement();

                                    statement.execute("set showplan on");

                                    statement.execute("set partialResultsMode true");

                                    ResultSet results = statement.executeQuery(sql);

                                    TeiidStatement tstatement = statement.unwrap(TeiidStatement.class);

                                    PlanNode queryPlan = tstatement.getPlanDescription();

                                    System.out.println(queryPlan);

                                    while(results.next())

                                    {

                                    i++;

                                    }

                                    results.close();

                                    statement.close();

                                    System.out.println("count_result: " + i);

                                    connection.close();

                                    }

                                    catch(Exception e)

                                    {

                                    e.printStackTrace();

                                    }

                                    }

                              }

                              • 12. Re: Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                                文芳 张 Newbie

                                and also , sybase is different from others db, eg mysql . when i use mysql as datasources , my vdb config is :

                                <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                                <vdb name="mysql" version="1">

                                <description>My Test mysql VDB</description>

                                <property name="UseConnectorMetadata" value="cached" />

                                        <model visible="true" type="PHYSICAL"  name="mysql">

                                                <property name="importer.useFullSchemaName" value="true"/>

                                                <property name="supports-multi-source-bindings" value="true"/>

                                                <source name="mysql82" translator-name="mysql5" connection-jndi-name="java:mysql82DS"/>

                                                <source name="mysql85" translator-name="mysql5" connection-jndi-name="java:mysql85DS"/>

                                        </model>

                                </vdb>

                                 

                                but when i use sybase , if i use the same properties , the vdb will fali to startup , and after i try several times, following is correct, i add a tableNamePattern properties , but if i add "<property name="importer.excludeTables" value="SYSOPTIONDEFAULTS"/> " it also doesn't work. but we have many tables , i should add every table name to vdb tableNamePattern property, shouldn't i ? thus , it's so complex. so is there some other solutions? thanks....

                                 

                                <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                                <vdb name="MyTest" version="1">

                                <description>My Test sybiq VDB</description>

                                <property name="UseConnectorMetadata" value="cached" />

                                        <model visible="true" type="PHYSICAL"  name="sybiq">

                                                <property name="importer.useFullSchemaName" value="true"/>

                                                <property name="importer.tableNamePattern" value="GPRS_USER_SERVICE_BDR131231"/>

                                                <property name="supports-multi-source-bindings" value="true"/>

                                                <source name="sybiq88" translator-name="sybase" connection-jndi-name="java:sybiq88DS"/>

                                                <source name="sybiq85" translator-name="sybase" connection-jndi-name="java:sybiq85DS"/>

                                        </model>

                                </vdb>

                                • 13. Re: Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                                  Steven Hawkins Master

                                  Assuming your client is behaving normally, you can simply ignore those warnings.  Netty, our IO framework, reports all exceptions to us even if they are related to normal closure of the client connections.  This will only get logged at a warning level if the socket is still reported as open and if the IOException is not rooted by a ClosedChannelException or a SocketException.  What is your client/server vm?  We can investigate if there are additional checks needed to eliminate erroneous warnings.

                                  • 14. Re: Re: Re: Re: Re: jboss eap 6.2+ teiid 8.8
                                    文芳 张 Newbie

                                    thanks very much ,

                                    and also , sybase is different from others db, eg mysql . when i use mysql as datasources , my vdb config is :

                                    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                                    <vdb name="mysql" version="1">

                                    <description>My Test mysql VDB</description>

                                    <property name="UseConnectorMetadata" value="cached" />

                                            <model visible="true" type="PHYSICAL"  name="mysql">

                                                    <property name="importer.useFullSchemaName" value="true"/>

                                                    <property name="supports-multi-source-bindings" value="true"/>

                                                    <source name="mysql82" translator-name="mysql5" connection-jndi-name="java:mysql82DS"/>

                                                    <source name="mysql85" translator-name="mysql5" connection-jndi-name="java:mysql85DS"/>

                                            </model>

                                    </vdb>

                                     

                                    but when i use sybase , if i use the same properties , the vdb will fali to startup , and after i try several times, following is correct, i add a tableNamePattern properties , but if i add "<property name="importer.excludeTables" value="SYSOPTIONDEFAULTS"/> " it also doesn't work. but we have many tables , i should add every table name to vdb tableNamePattern property, shouldn't i ? thus , it's so complex. so is there some other solutions? thanks....

                                     

                                    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                                    <vdb name="MyTest" version="1">

                                    <description>My Test sybiq VDB</description>

                                    <property name="UseConnectorMetadata" value="cached" />

                                            <model visible="true" type="PHYSICAL"  name="sybiq">

                                                    <property name="importer.useFullSchemaName" value="true"/>

                                                    <property name="importer.tableNamePattern" value="GPRS_USER_SERVICE_BDR131231"/>

                                                    <property name="supports-multi-source-bindings" value="true"/>

                                                    <source name="sybiq88" translator-name="sybase" connection-jndi-name="java:sybiq88DS"/>

                                                    <source name="sybiq85" translator-name="sybase" connection-jndi-name="java:sybiq85DS"/>

                                            </model>

                                    </vdb>

                                    1 2 Previous Next