Solving xcb_xlib.c:50: xcb_xlib_unlock: Assertion 'c->xlib.lock' failed. on fedora 8

Yesterday i decided to upgrade osb 3.0 to OSB 10gr3 on my linux box. During installation i have first locate the famous error "xcb_xlib.c:50: xcb_xlib_unlock: Assertion 'c->xlib.lock' failed.". Through google, i have found a few solution to solve the problem but all the solutions gone in vain.
I have had following configuration:
[recon@localhost home]$ cat /etc/redhat-release
Fedora release 8 (Werewolf)
[recon@localhost home]$ java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_14-b03, mixed mode)
[recon@localhost home]$ rpm -q libxcb libX11
libxcb-1.0-3.fc8
libX11-1.1.3-4.fc8
First of all, i have tried to patch the library libmawt.so by sed -i 's/XINERAMA/FAKEEXTN/g' of my current JVM, but it was not help me to run the installer to install OSB 10gR3. Even i installed latest 1.6 JDK and patch the libmawt.so but in vain.
From one of linux forum, i found a suggestion to upgrade libxcb file and try again. Here is my all the step to resolve the problem:
1) upgrade yum install (nothing updated)
2) update libxcb
[recon@localhost home]$ sudo yum update libxcv
[recon@localhost tmp]$ rpm -q libxcb
libxcb-1.1-1.1.fc8
which will upgrade my libxcb to version 1.1
3) patch the libmawt.so for current JVM (it was unnecessary, because i have done it before)
4) run installer and all goes well.
For more information, you can visit the following post on oracle forum.

Comments

Tip: SQL client for Apache Ignite cache

A new SQL client configuration described in The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Apache Ignite provides SQL queries execution on the caches, SQL syntax is an ANSI-99 compliant. Therefore, you can execute SQL queries against any caches from any SQL client which supports JDBC thin client. This section is for those, who feels comfortable with SQL rather than execute a bunch of code to retrieve data from the cache. Apache Ignite out of the box shipped with JDBC driver that allows you to connect to Ignite caches and retrieve distributed data from the cache using standard SQL queries. Rest of the section of this chapter will describe how to connect SQL IDE (Integrated Development Environment) to Ignite cache and executes some SQL queries to play with the data. SQL IDE or SQL editor can simplify the development process and allow you to get productive much quicker. Most database vendors have their own front-en

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b

Load balancing and fail over with scheduler

Every programmer at least develop one Scheduler or Job in their life time of programming. Nowadays writing or developing scheduler to get you job done is very simple, but when you are thinking about high availability or load balancing your scheduler or job it getting some tricky. Even more when you have a few instance of your scheduler but only one can be run at a time also need some tricks to done. A long time ago i used some data base table lock to achieved such a functionality as leader election. Around 2010 when Zookeeper comes into play, i always preferred to use Zookeeper to bring high availability and scalability. For using Zookeeper you have to need Zookeeper cluster with minimum 3 nodes and maintain the cluster. Our new customer denied to use such a open source product in their environment and i was definitely need to find something alternative. Definitely Quartz was the next choose. Quartz makes developing scheduler easy and simple. Quartz clustering feature brings the HA and

My workspace

Search This Blog