incubator-hcatalog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olga Natkovich (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HCATALOG-123) Incorrect configuration of ActiveMQ causes hcat_server to quit unexpectedly.
Date Tue, 06 Dec 2011 01:03:03 GMT

     [ https://issues.apache.org/jira/browse/HCATALOG-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olga Natkovich resolved HCATALOG-123.
-------------------------------------

    Resolution: Invalid
    
> Incorrect configuration of ActiveMQ causes hcat_server to quit unexpectedly.
> ----------------------------------------------------------------------------
>
>                 Key: HCATALOG-123
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-123
>             Project: HCatalog
>          Issue Type: Bug
>          Components: notification
>    Affects Versions: 0.2
>            Reporter: Mithun Radhakrishnan
>            Assignee: Mithun Radhakrishnan
>             Fix For: 0.2
>
>
> When ActiveMQ is configured incorrectly (e.g. when the broker-specification is missing),
the ActiveMQ server doesn't start. When hcat_server is started, the logs indicate that ActiveMQ_server
can't be connected to.
> <hcat_server.log>
> 2011-10-05 11:39:11,523 ERROR hcatalog.YHCatListener (YHCatListener.java:createConnection(49))
- Failed to initialize connection to message busjavax.jms.JMSException: Could not connect
to broker URL: tcp://gsbl90650.blue.ygrid.yahoo.com:61616. Reason: java.net.ConnectException:
Connection refused        at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
       at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
>         at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:230)
       at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:178)
>         at com.yahoo.hcatalog.YHCatListener.createConnection(YHCatListener.java:37) 
      at org.apache.hcatalog.listener.NotificationListener.<init>(NotificationListener.java:87)
       at com.yahoo.hcatalog.YHCatListener.<init>(YHCatListener.java:23)        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:513)        at org.apache.hadoop.hive.metastore.MetaStoreUtils.getMetaStoreListener(MetaStoreUtils.java:969)
       at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:263)
       at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.<init>(HiveMetaStore.java:207)
       at org.apache.hadoop.hive.metastore.HiveMetaStore.startMetaStore(HiveMetaStore.java:3398)
       at org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:3379)   
    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 org.apache.hadoop.util.RunJar.main(RunJar.java:156)Caused
by: java.net.ConnectException: Connection refused        at java.net.PlainSocketImpl.socketConnect(Native
Method)        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:529)
>         at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:484)
>         at org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:447)
>         at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
>         at org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:126)
>         at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
>         at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
>         at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
>         at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
>         at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:266)
>         ... 19 more
> </hcat_server.log>
> Thereafter, if an operation like create/drop table/partition is attempted (or indeed
anything that modifies the metastore-server state), the hcat_server process just exits. The
logs don't indicate why. All that's logged is:
> .....
> 2011-10-05 17:10:30,009 INFO  metastore.HiveMetaStore (HiveMetaStore.java:getMS(383))
- 2: Opening raw store with implemenation class:org.apache.hadoop.hive.metastore.ObjectStore
> 2011-10-05 17:10:30,010 INFO  metastore.ObjectStore (ObjectStore.java:initialize(205))
- ObjectStore, initialize called
> 2011-10-05 17:10:30,011 INFO  metastore.ObjectStore (ObjectStore.java:setConf(188)) -
Initialized ObjectStore
> 2011-10-05 17:10:30,289 INFO  metastore.HiveMetaStore (HiveMetaStore.java:logInfo(510))
- 2: get_table : db=default tbl=dm_search_click
> 2011-10-05 17:10:30,317 INFO  metastore.HiveMetaStore (HiveMetaStore.java:logInfo(510))
- 2: alter_table: db=default tbl=dm_search_click newtbl=dm_search_click
> 2011-10-05 17:10:30,318 INFO  metastore.HiveMetaStore (HiveMetaStore.java:logInfo(510))
- 2: get_table : db=default tbl=dm_search_click
> .....
> If ActiveMQ can't be connected to, a failure to post messages is understandable. A server
exit is not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message