[JBoss JIRA] Created: (TEIID-451) Running svcmgr.sh ls option throws exception
by Van Halbert (JIRA)
Running svcmgr.sh ls option throws exception
---------------------------------------------
Key: TEIID-451
URL: https://jira.jboss.org/jira/browse/TEIID-451
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.1.0
Reporter: Van Halbert
Assignee: Steven Hawkins
The following exception is seen when trying the "ls" option when runngin svcmgr.sh :
java.lang.ArrayIndexOutOfBoundsException: 30
at com.metamatrix.server.ServiceManager.processCommand(ServiceManager.java:268)
at com.metamatrix.server.ServiceManager.startInteractiveMode(ServiceManager.java:236)
at com.metamatrix.server.ServiceManager.run(ServiceManager.java:216)
at com.metamatrix.server.ServiceManager.main(ServiceManager.java:1214)
It's seen when running: svcmgr.sh ls
or after starting svcmgr.sh and then entering "ls" option
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (TEIID-445) Threading cleanup
by Steven Hawkins (JIRA)
Threading cleanup
-----------------
Key: TEIID-445
URL: https://jira.jboss.org/jira/browse/TEIID-445
Project: Teiid
Issue Type: Task
Components: Common, Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.1.0
WorkerPools should expose the ability to schedule tasks (repeated and delayed). This can then be used at the connector layer to replace per connector timers with calls to the connector workerpool via the connectorenvironment. Next the nio and socket server worker threads should be combined. There is very little gain from having them be separate pools - (continuing i/o work while all the socket server workers are busy probably means that the workers should be increased, rather than queuing the server work).
Finally it would nice to have a workerpool implementation that provides a shared thread pool so that connector specific pool sizings are less of consideration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (TEIID-439) NPE Getting Resource From VDB
by Ted Jones (JIRA)
NPE Getting Resource From VDB
-----------------------------
Key: TEIID-439
URL: https://jira.jboss.org/jira/browse/TEIID-439
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Steven Hawkins
Fix For: 6.1.0
While attempting to execute System.getUpdatedCharacterVDBResource() to get WSDL from a VDB, I received the following exception:
com.metamatrix.jdbc.MMSQLException: Error trying to execute a statement {?=call System.getUpdatedCharacterVDBResource(?,?,?)}.
at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:75)
at com.metamatrix.jdbc.MMCallableStatement.internalExecute(MMCallableStatement.java:394)
at com.metamatrix.jdbc.MMPreparedStatement.internalExecuteQuery(MMPreparedStatement.java:225)
at com.metamatrix.jdbc.MMPreparedStatement.execute(MMPreparedStatement.java:178)
at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.getResource(MMGetVDBResourceServlet.java:283)
at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.doPost(MMGetVDBResourceServlet.java:184)
at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.doGet(MMGetVDBResourceServlet.java:106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.metamatrix.jdbc.MMSQLException: java.lang.NullPointerException
at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:82)
at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:63)
at com.metamatrix.jdbc.MMStatement.executeAsynchAndWait(MMStatement.java:815)
at com.metamatrix.jdbc.MMStatement.sendRequestMessageAndWait(MMStatement.java:1007)
at com.metamatrix.jdbc.MMCallableStatement.internalExecute(MMCallableStatement.java:392)
... 25 more
Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException
at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.convertResult(SocketServerInstanceImpl.java:267)
at com.metamatrix.dqp.client.ResultsFuture.get(ResultsFuture.java:110)
at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:310)
at com.metamatrix.jdbc.MMStatement.executeAsynchAndWait(MMStatement.java:813)
... 27 more
Caused by: java.lang.NullPointerException
at com.metamatrix.vdb.runtime.VDBKey.<init>(VDBKey.java:33)
at org.teiid.dqp.internal.process.DQPCore$ConnectorCapabilitiesCache.getVDBConnectorCapabilities(DQPCore.java:99)
at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:227)
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 com.metamatrix.common.comm.platform.socket.server.ServerWorkItem.run(ServerWorkItem.java:116)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
... 1 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months