簡體   English   中英

WSO2 BAM 2.1.0安裝

[英]WSO2 BAM 2.1.0 installation

我已經將WSO2 Bam 2.1.0安裝到了本地環境,並且將日志重定向到bam。 我可以在cassandra上看到我的日志,但是當我嘗試在bam上執行service_stats時,出現異常。 您可以在下面看到錯誤。

你有什么建議嗎?

[2013-01-22 12:33:53,659]錯誤{org.wso2.carbon.rssmanager.core.service.RSSAdmin}-檢索租戶'carbon.super'org.wso2.carbon的數據庫列表時發生錯誤。 rssmanager.core.RSSManagerException:檢索org.wso2.carbon.rssmanager.core.internal上的org.wso2.carbon.rssmanager.core.internal.dao.RSSDAOImpl.getAllDatabases(RSSDAOImpl.java:291)上的所有數據庫時發生錯誤。位於org.wso2.carbon.rssmanager.core.service.RSSAdmin.getDatabases(RSSAdmin.java:101)的manager.RSSManager.getDatabases(RSSManager.java:146),位於org.wso2.carbon.rssmanager.core.service.RSSAdmin。 getDatabasesForTenant(RSSAdmin.java:336)位於sun.reflect.NativeMethodAccessorImpl.invoke0(本地方法)位於sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)位於sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI)在org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)在java.lang.reflect.Method.invoke(Method.java:616) org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)位於org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)位於org.apache.axis2.receivers.AbstractMessageReceiver。在org.org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)在org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)處接收(AbstractMessageReceiver.java:110) org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)上的.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)在javax.servlet.http.HttpServlet.service上(HttpServlet.java:641),位於org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90),位於javax.servlet.http.HttpServlet.service(HttpServlet.java:722)。 eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)位於org.eclipse.equinox.http.s org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java.servlet.http.HttpServlet.service(HttpServlet.java:722)中的ervlet.internal.ProxyServlet.service(ProxyServlet.java:67)。 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)處org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)處org.wso2.carbon.tomcat org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)的.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java :210)位於org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225),位於org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)位於org.apache.catalina.authenticator。 org.apache.catalina.core.StandardHostV上的AuthenticatorBase.invoke(AuthenticatorBase.java:472) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)的alve.invoke(StandardHostValve.java:168)org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java: 172),位於org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)的org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)。 .tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)位於org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)位於org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter .java:407),位於org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001),位於org.apache.coyote.AbstractProtocol $ AbstractConnectionHandler.process(AbstractProtocol.java:579),位於org.apache.tomcat。 util.net.NioEndpoint $ SocketProcessor.run(NioEndpoint.java:1653)在java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1110),位於java.util.concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:603),位於java.lang.Thread.run(Thread.java:679),原因:org.h2.jdbc.JdbcSQLException :找不到“ D.ID”列; SQL語句:SELECT d.ID AS DATABASE_ID,d.NAME,d.TENANT_ID,s.NAME AS RSS_INSTANCE_NAME,s.SERVER_URL,s.TENANT_ID AS RSS_INSTANCE_TENANT_ID,d.TYPE FROM RM_SERVER_INSTANCE s,RM_DATABASE d WHERE s.ID = RSS_INSTANCE_ID AND d.TENANT_ID =嗎? [42122-140]在org.h2.message.DbException.get(org.h2.message.DbException.getJdbcSQLException(DbException.java:327)在org.h2.message.DbException.get(DbException.java:167) org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:127)位於org.h2.expression.Alias.optimize(Alias.java:47)位於org.h2.command.dml.Select處的DbException.java:144)在org.h2.command.Parser.parser.prepare(Parser.java:202)在org.h2.command.Parser.prepareCommand(Parser.java:214)在org.h2.engine的.prepare(Select.java:738)。在org.h2.engine.Session.prepareCommand(Session.java:384)在org.h2.jdbc的Session.prepareLocal(Session.java:434)在org.h2.jdbc的org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1071) org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:234)上的.JdbcPreparedStatement。 java:43),位於java.lang.reflect.Method.invoke(Meth od.java:616)位於org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)位於org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99) org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)上的.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51)在org.apache.tomcat.jdbcpool上。 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)處的.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67)在org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke (ConnectionState.java:153)在org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)在org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51) org.apache.tomcat.jdbc.pool.in上的org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99) 在org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)的terceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67)在org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke( org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)的org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)的ConnectionState.java:153) org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:63)上的.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)at $ Proxy20.prepareStatement(Unknown Source)at org.wso2.carbon.rssmanager.core.internal.dao.RSSDAOImpl.getAllDatabases(RSSDAOImpl.java:277)...還有44個[2013-01-22 12:33:53,674]錯誤{org.wso2.carbon.analytics .hive.multitenancy.HiveRSSMetastoreManager}-初始化租戶Hive元存儲時出錯。org.wso2.carbon.rssmanager.ui.stub.RSSAdminRSSManagerExceptionException:RSSAdminRSSManagerExcepti java.45上sun.reflect.NativeConstructorAccessorImpl.newInstance0(本機方法)處的onException(sun.reflect.NativeConstructorAccessorImpl.java:57處sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)處的onException。 org.wso2.carbon.rssmanager.ui上的java.lang.Class.newInstance0(Class.java:372)上的Constructor.newInstance(Constructor.java:532) org.wso2.carbon.analytics.hive.multitenancy.HiveRSSMetastoreManager.getHiveMetaDatabase(HiveRSSMetastoreManager.java:259)上的.stub.RSSAdminStub.getDatabasesForTenant(RSSAdminStub.java:819)在org.wso2.carbon.analytics.hive。 org.wso2.carbon.analytics.hive.multitenancy.HiveRSSMetastoreManager.prepareRSSMetaStore(HiveRSSMetastoreManager.java:212)上的.getRSSMetaStore(HiveRSSMetastoreManager.java:236)在org.wso2.carbon.hive.data.source.access.util.DataSourceAccessUtil .getMetaStoreConne org.apache.hadoop.hive.metastore.HiveContext.getCurrentContext(org.wso2.carbon.hive.data.source.access.util.DataSourceAccessUtil.getJdoConnectionUrl(DataSourceAccessUtil.java:98)的ctionURL(DataSourceAccessUtil.java:85) HiveContext.java:104)位於org.apache.hadoop.hive.jdbc.HiveConnection。(HiveConnection.java:63)位於org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java:104)位於java。 org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java)上的java.sql.DriverManager.getConnection(DriverManager.java:200)上的sql.DriverManager.getConnection(DriverManager.java:620): 234),位於org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:217),位於java.util.concurrent.FutureTask $ Sync.innerRun(FutureTask.java:334),位於java.util。 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)上的.concurrent.FutureTask.run(FutureTask.java:166)在java.util.concurrent.ThreadPoolExe上 cutor $ Worker.run(ThreadPoolExecutor.java:603)at java.lang.Thread.run(Thread.java:679)[2013-01-22 12:33:53,678]錯誤{org.wso2.carbon.analytics.hive .multitenancy.HiveRSSMetastoreManager}-檢索設置租戶域的配置單元元存儲時出錯:carbon.super [2013-01-22 12:33:53,680]錯誤{org.apache.hadoop.hive.metastore.HiveContext}-無法執行在org.wso2.carbon.hive.data.source處從org.wso2.carbon.analytics.hive.multitenancy.HiveRSSMetastoreManager.getMetaDataStoreConnectionURL(HiveRSSMetastoreManager.java:275)處獲取元存儲的JDO連接URL。 org.wso2.carbon.hive.data.source.access.util.DataSourceAccessUtil.getJdoConnectionUrl(DataSourceAccessUtil.java:98)上的.access.util.DataSourceAccessUtil.getMetaStoreConnectionURL(DataSourceAccessUtil.java:89)在org.apache.hadoop.hive位於org.apache.hadoop.hive.jdbc.HiveConnection的.metastore.HiveContext.getCurrentContext(HiveContext.java:104),位於org.apache.hadoop的(HiveConnection.java:63)。 org.wso2.carbon上的java.sql.DriverManager.getConnection(DriverManager.java:620)處的hive.jdbc.HiveDriver.connect(HiveDriver.java:104)在org.wso2.carbon處的java.sql.DriverManager.getConnection(DriverManager.java:200) org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:217)的.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:234)在java.util.concurrent Java的.FutureTask $ Sync.innerRun(FutureTask.java:334)在java.util.concurrent.FutureTask.run(FutureTask.java:166)在java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)在Java。 util.concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:603)at java.lang.Thread.run(Thread.java:679)[2013-01-22 12:33:53,682]錯誤{org.wso2.carbon .analytics.hive.impl.HiveExecutorServiceImpl}-查詢執行期間發生錯誤。java.util.concurrent.ExecutionException:java.lang.RuntimeException:無法獲取元存儲的JDO連接URL。 在org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl的java.util.concurrent.FutureTask.get(FutureTask.java:111)處的java.util.concurrent.FutureTask $ Sync.innerGet(FutureTask.java:252) org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(Task.org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask.execute(HiveScriptExecutorTask.java:60)處的execute(HiveExecutorServiceImpl.java:91) .java:56),位於org.quartz.core.JobRunShell.run(JobRunShell.java:213),位於java.util.concurrent.Executors $ RunnableAdapter.call(Executors.java:471),位於java.util.concurrent.FutureTask $ Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)at java.util.concurrent .ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:603),位於java.lang.Thread.run(Thread.java:679),原因:java.lang.RuntimeException:無法獲取元存儲的JDO連接URL。要么 g.apache.hadoop.hive.metastore.HiveContext.handleException(HiveContext.java:265)位於org.apache.hadoop.hive.metastore.HiveContext.getCurrentContext(HiveContext.java:113)位於org.apache.hadoop.hive。 java.sql.DriverManager.getConnection(DriverManager.java:620)上的org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java:104)上的jdbc.HiveConnection。(HiveConnection.java:63)。 org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:234)處的sql.DriverManager.getConnection(DriverManager.java:200)在org.wso2.carbon.analytics.hive.impl HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:217)... 5更多原因:org處的org.wso2.carbon.analytics.hive.multitenancy.HiveRSSMetastoreManager.getMetaDataStoreConnectionURL(HiveRSSMetastoreManager.java:275)上的java.lang.NullPointerException org.wso2.ca上的.wso2.carbon.hive.data.source.access.util.DataSourceAccessUtil.getMetaStoreConnectionURL(DataSourceAccessUtil.java:89) org.apache.hadoop.hive.metastore.HiveContext.getCurrentContext(HiveContext.java:104)的rbon.hive.data.source.access.util.DataSourceAccessUtil.getJdoConnectionUrl(DataSourceAccessUtil.java:98)...還有11個[2013 -01-22 12:33:53,684]錯誤{org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask}-執行腳本時出錯:service_stats_336 org.wso2.carbon.analytics.hive.exception.HiveExecutionException:查詢期間出錯在org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask.execute(HiveScriptExecutorTask.java:60)在org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl.execute(HiveExecutorServiceImpl.java:97)處執行org.quartz.core.JobRunShell.run(JobRunShell.java:213)上的org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:56)在java.util.concurrent.Executors $ RunnableAdapter處。在java.util.concurrent.FutureTask.run(FutureTask.jav)處調用(Executors.java:471)在java.util.concurrent.FutureTask $ Sync.innerRun(FutureTask.java:334) a:166)在java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)在java.util.concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:603)在java.lang.Thread.run(Thread .java:679)原因:java.util.concurrent.ExecutionException:java.lang.RuntimeException:無法獲取元存儲的JDO連接URL。java.util.concurrent.FutureTask $ Sync.innerGet(FutureTask.java :252)at org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl.execute(HiveExecutorServiceImpl.java:91)上的java.util.concurrent.FutureTask.get(FutureTask.java:111)... 9造成原因:java.lang.RuntimeException:無法在org.apache.hadoop.hive.metastore上獲取org.apache.hadoop.hive.metastore.HiveContext.handleException(HiveContext.java:265)的元存儲的JDO連接URL。 org.apache.hadoop.hive.jdbc.HiveConnection.HiveContext.getCurrentContext(HiveContext.java:113)org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java)處的.HiveConnection.java:63) :104),位於org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable的java.sql.DriverManager.getConnection(DriverManager.java:200)的java.sql.DriverManager.getConnection(DriverManager.java:620)處。在org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl $ ScriptCallable.call(HiveExecutorServiceImpl.java:217)處調用(HiveExecutorServiceImpl.java:234)... 5更多原因:org.wso2處的java.lang.NullPointerException org.wso2.carbon.hive.data.source.access.util.DataSourceAccessUtil.getMetaStoreConnectionURL(DataSourceAccessUtil.java:89)上的.carbon.analytics.hive.multitenancy.HiveRSSMetastoreManager.getMetaDataStoreConnectionURL(HiveRSSMetastoreManager.java:275)在org.wso2 .carbon.hive.data.source.access.util.DataSourceAccessUtil.getJdoConnectionUrl(DataSourceAccessUtil.java:98)在org.apache.hadoop.hive.metastore.HiveContext.getCurrentContext(HiveContext.java:104)...另外11個

您能否放置完整的異常跟蹤? 並且您是否已將租戶添加到BAM,並且您正在以租戶模式運行? 您在此處使用的端口偏移是多少?

您可能需要使用正確的詳細信息更新$ BAM_HOME / repository / conf / advanced / hive-rss-config.xml。 如下所述:

rss-server-url-您可以為此使用相同的BAM服務器/外部BAM服務器/存儲服務器。 請輸入您要用於RSS的正確服務器。 如果要僅在獨立模式下運行,則https://127.0.0.1:9443+<port-offset> /將起作用。

rss-server-admin-userName-具有所有特權用戶名的SuperAdmin / superadmin用戶。

rss-server-admin-password-具有所有特權密碼的SuperAdmin / superadmin用戶。

請重新啟動服務器以反映更改。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM