Error Creating Transactional Connection Factory Nested Throwables
Contents |
here for a quick overview
Error Creating Transactional Connection Factory Spark
of the site Help Center Detailed answers to any questions you spark-shell error creating transactional connection factory might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow error creating transactional connection factory datanucleus the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7
Failed To Get Database Default, Returning Nosuchobjectexception
million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Hive doesn't work on install up vote 6 down vote favorite 2 I get the following error in Hive when executing any command. hive> show tables; FAILED: Error in metadata: javax.jdo.JDOFatalInternalException: Unexpected exception caught. NestedThrowables: java.lang.reflect.InvocationTargetException FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask This is in the hive.log. 2011-07-27 19:10:57,526 ERROR exec.DDLTask (SessionState.java:printError(343)) - FAILED: Error in metadata: javax.jdo.JDOFatalInternalException: Unexpected exception caught. NestedThrowables: java.lang.reflect.InvocationTargetException org.apache.hadoop.hive.ql.metadata.HiveException: javax.jdo.JDOFatalInternalException: Unexpected exception caught. NestedThrowables: java.lang.reflect.InvocationTargetException at org.apache.hadoop.hive.ql.metadata.Hive.getDatabase(Hive.java:1028) at org.apache.hadoop.hive.ql.metadata.Hive.databaseExists(Hive.java:1013) at org.apache.hadoop.hive.ql.exec.DDLTask.showTables(DDLTask.java:1691) at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:289) at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130) at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57) at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1063) at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:900) at org.apache.hadoop.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings spark dataframe and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it http://stackoverflow.com/questions/6853445/hive-doesnt-work-on-install only takes a minute: Sign up Error while creating tables on Hive up vote 0 down vote favorite I created this table in Hive: hive> CREATE TABLE twitter_data(datePosted TIMESTAMP , userId BIGINT , userName STRING , tweets STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t'; But it displays this error message: FAILED: Error in metadata: javax.jdo.JDOFatalInternalException: Error creating transactional connection http://stackoverflow.com/questions/14643954/error-while-creating-tables-on-hive factory NestedThrowables: java.lang.reflect.InvocationTargetException FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask Does anyone know what this error message means? hadoop hive share|improve this question edited Sep 19 '15 at 1:54 spenibus 3,328111526 asked Feb 1 '13 at 10:11 Sherry Leann 11 what is the version of hive you are using? –WR10 Feb 1 '13 at 12:19 A similar issue is discussed here: stackoverflow.com/questions/6853445/hive-doesnt-work-on-install –Lorand Bendig Feb 3 '13 at 11:08 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote I recently met with this problem and the issue was related to the Hive JDBC driver which was not available to the client while making the request to Hive. This is what I did to solve my problem: I did verify that I do have the Hive JDBC connector installed in my cluster I modified the following settings in hive-site.xml correctly depending on my local settings:
library Understanding connection transitions: Avoiding multi-threaded access to a JCA connection in WebSphere Application Server IBM® WebSphere® Application Server JCA connection manager provides connection pooling and enables administrators to establish a pool of http://www.ibm.com/developerworks/websphere/techjournal/1205_ramachandra/1205_ramachandra.html connections that can be shared by applications running on an application server. However, the sharing of a JCA connection across multiple threads by an application can result in various exceptions. http://docs.spring.io/spring-framework/docs/2.5.x/api/org/springframework/jms/listener/AbstractMessageListenerContainer.html This article describes some of the application coding practices that lead to connection sharing across multiple threads, and explains the multi-threaded detection capabilities provided by WebSphere Application Server. This error creating content is part of the IBM WebSphere Developer Technical Journal. PDF (814 KB) | Share: Anoop Ramachandra (anramach@in.ibm.com), Senior Staff Software Engineer , IBM China Close [x] Anoop Ramachandra is a Senior Staff Software Engineer in IBM India Software Labs. He has over eight years of experience on WebSphere Application Server product as a Technical Lead, developer and error creating transactional Level 3 support engineer. His major areas of expertise in WebSphere Application Server include System Management, Java EE Connector Architecture, Virtual Member Manager, Scheduler and Asynchronous beans. He is an IBM Certified System Administrator for WebSphere Application Server. Rispna Jain (rispjain@in.ibm.com), Software Deployment Manager, IBM China Close [x] Rispna Jain is a Technical Software Deployment Manager for WebSphere suite of products in IBM Global Technology Services and works with clients in North America. She has seven years of experience on WebSphere Application Server product development at IBM Software Group in various roles such as development, L3 support and test. Rispna has also been a technical speaker for WebSphere Application Server related topics at various WebSphere conferences. She is an IBM Certified SOA associate and holds a Master of Technology degree in Computer Science. 09 May 2012
Table of contents Introduction Connection sharing terminology Connection transition Multi-threaded access to a connection Related topics Detecting MultiThreaded access to a connection Conclusion Acknowledgements Resources Comments IntroductionThe IBM WebSphere Application Server connection pool helps to alleviateorg.springframework.jms.support.JmsAccessor org.springframework.jms.support.destination.JmsDestinationAccessor org.springframework.jms.listener.AbstractJmsListeningContainer org.springframework.jms.listener.AbstractMessageListenerContainer All Implemented Interfaces: BeanNameAware, DisposableBean, InitializingBean, Lifecycle Direct Known Subclasses: AbstractPollingMessageListenerContainer, ServerSessionMessageListenerContainer, SimpleMessageListenerContainer public abstract class AbstractMessageListenerContainerextends AbstractJmsListeningContainer Abstract base class for message listener containers. Can either host a standard JMS MessageListener or a Spring-specific SessionAwareMessageListener. Usually holds a single JMS Connection that all listeners are supposed to be registered on, which is the standard JMS way of managing listeners. Can alternatively also be used with a fresh Connection per listener, for J2EE-style XA-aware JMS messaging. The actual registration process is up to concrete subclasses. NOTE: The default behavior of this message listener container is to never propagate an exception thrown by a message listener up to the JMS provider. Instead, it will log any such exception at the error level. This means that from the perspective of the attendant JMS provider no such listener will ever fail. The listener container offers the following message acknowledgment options: "sessionAcknowledgeMode" set to "AUTO_ACKNOWLEDGE" (default): Automatic message acknowledgment before listener execution; no redelivery in case of exception thrown. "sessionAcknowledgeMode" set to "CLIENT_ACKNOWLEDGE": Automatic message acknowledgment after successful listener execution; no redelivery in case of exception thrown. "sessionAcknowledgeMode" set to "DUPS_OK_ACKNOWLEDGE": Lazy message acknowledgment during or after listener execution; potential redelivery in case of exception thrown. "sessionTransacted" set to "true": Transactional acknowledgment after successful listener execution; guaranteed redelivery in case of exception thrown. The exact behavior might vary according to the concrete listener container and JMS provider used. There are two solutions to the duplicate processing problem: Either add duplicate message detection to your listener, in the form of a business entity existence check or a protocol table check. This usually just needs to be done in case of the JMSRedelivered flag being set on the incoming message (else just process