Recent Posts
Archives

PostHeaderIcon TibrvException[error=4,message=Tibrv not initialized]

Case

In a JUnit test, I send a message on a TibcoRV, but I get the following error:

TibrvException[error=4,message=Tibrv not initialized]

Fix

In order, proceed as this:

  1. check an RVD daemon is running 😉
  2. check tibrvj.jar is in your classpath 😉
  3. check the instanciation of transport layer new TibrvRvdTransport(service, network, daemon); is done within your public void testXXX(), and not in the setUp().

PostHeaderIcon Windows Mobile 6.1: which browser?

Here is a short comparative of webbrowsers available on Windows Mobile 6.1. I used them on a Acer X960 on French VirginMobile network.

Browser Pros Cons WebSite
Internet Explorer 5
  • already installed on devices
  • slow
  • no tabs
  • no Flash
  • GMail doesn’t work
  • Micro$oft!
Mozilla Fennec 1.0a1
  • open source
  • tabs
  • very slow
  • very heavy in memory
  • no Flash
  • GMail doesn’t work
http://www.mozilla.org/projects/fennec/1.0a1/releasenotes/
Opera Mobile 10
  • tabs
  • fluidity
  • speed
  • no Flash
  • heavy in memory
  • GMail doesn’t work
  • not open-source
http://www.opera.com/
SkyFire 1.5
  • GMail works
  • Flash supported
  • speed
  • no tabs
  • confidentiality
  • not open-source
http://get.skyfire.com

As a conclusion, what do I do?

  • In most cases, I use Opera, for its speedness and tabs.
  • When I need watch a video
    • my Acer X960 displays YouTube videos in a specific player
    • on other websites, I use SkyFire.
  • For Google applications (GMail, Reader, Docs, etc.), I use SkyFire, too.

PostHeaderIcon org.springframework.beans.factory.xml.XmlBeanDefinitionReader: Ignored XML validation warning org.xml.sax.SAXParseException: SchemaLocation: schemaLocation value = … must have even number of URI’s

Context

Mule 2.2.1 ESB config file with a TibcoRV connector, under Windows XP SP2 and Java 5.
The error happened in this context, yet I assume it would occur in any occurence related to XSD / XML schemas.

Error

org.springframework.beans.factory.xml.XmlBeanDefinitionReader: Ignored XML validation warning
org.xml.sax.SAXParseException: SchemaLocation: schemaLocation value = 'http://www.mulesource.org/schema/mule/management/2.2                http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd                http://www.mulesource.org/schema/mule/core/2.2                http://www.mulesource.org/schema/mule/core/2.2/mule.xsd                http://www.springframework.org/schema/beans                http://www.springframework.org/schema/beans/spring-beans-2.5.xsd                http://www.mulesource.org/schema/mule/core/2.2/mule.xsd                http://www.mulesource.org/schema/mule/vm/2.2                http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
http://www.mulesource.org/schema/mule/tibcorv/2.2                http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd' must have even number of URI's.

Headers of XML config file:

[xml]<mule xmlns=&amp;quot;http://www.mulesource.org/schema/mule/core/2.2&amp;quot;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns:management="http://www.mulesource.org/schema/mule/management/2.2"
xmlns:tibcorv="http://www.mulesource.org/schema/mule/tibcorv/2.2
xsi:schemaLocation="http://www.mulesource.org/schema/mule/management/2.2
http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd
http://www.mulesource.org/schema/mule/core/2.2
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
http://www.mulesource.org/schema/mule/vm/2.2
http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
http://www.mulesource.org/schema/mule/tibcorv/2.2
http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd">[/xml]

Explanation – Fix

Each time, the attribute xsi:schemaLocation must have an even number of lines: a “public” XSD address and a “non-public” one. For non English-fluent speakers, I remind that a number is even if, and only if, it is a multiple of 2 ; otherwise it is odd.

In our case, one line is redundant. To fix this issue, you have to remove the redundant line, and ensure each line belongs to a consistent pair of lines: for instance:

http://www.mulesource.org/schema/mule/tibcorv/2.2
and
http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd

PostHeaderIcon TibrvException[error=901,message=Library not found: tibrvjsd]

Stacktrace

TibrvException[error=901,message=Library not found: tibrvjsd]

and below:

java.lang.UnsatisfiedLinkError: no tibrvjsd in java.library.path

The error appears also with tibrv instead of tibrvjsd.

Context

Mule ESB 2.2.1 using TibcoRV 8.1.2, under Windows XP, with Java 1.5

Explanation – Fix

  • Explanation:
    • the Mule tries to load a DLL, here tibrvjsd.dll. Its path should be available in the property java.library.path.
    • Unlike what may be found on the net, the right DLL cannot be found under
      %TIBRV_HOME%/lib, where only jars are available, not DLLs.
  • Backup the file %MULE_HOME%/conf/wrapper.conf
  • Edit it
  • After the lines

[java]# Java Native Library Path (location of .DLL or .so files)
wrapper.java.library.path.1=%LD_LIBRARY_PATH%
wrapper.java.library.path.2=%MULE_HOME%/lib/boot[/java]

add the line:

[java]wrapper.java.library.path.3=%TIBRV_HOME%/bin[/java]

PostHeaderIcon Use TibcoRV connector with Mule ESB

Installation

Prerequisites

Priori to following the current tutorial, you must have installed

  • a Java JDK/JRE 1.5+, with a parameter JAVA_HOME already set
  • a TibcoRV 8.1, with a parameter TIBRV_HOME already set. You can consult a short tutorial here to perform this.

Main

  • Get Zip version of “Mule ESB Full Distribution”, version 2.2.1, on this page.
  • Unzip the content in a folder, eg: C:\exe\mule-standalone-2.2.1
  • Add a environment variable MULE_HOME and update your path, eg:
    set MULE_HOME=C:\win32app\mule-standalone-2.2.1
    set PATH=%PATH%;%MULE_HOME%\bin
  • To check the Mule is well installed, you can launch the “Hello World” application:
    %MULE_HOME%\examples\hello\hello.bat

Specific for TibcoRV

  • Get mule-transport-tibcorv-2.2.1.jar, available at this link.
  • Copy it into %MULE_HOME%/lib/mule
  • Get the jar %TIBRV_HOME%\lib\tibrv.jar
  • Copy and rename it into %MULE_HOME%/lib/opt/tibrvj-8.1.2.jar
  • Tip: to know the exact version of the Jar you have just copied, you can open it, explore and decompile the class com.tibco.tobrv.tibrvj_id. The exact version must appear.
  • Copy %MULE_HOME%/conf/wrapper.conf as %MULE_HOME%/conf/wrapper.conf.old
  • Edit %MULE_HOME%/conf/wrapper.conf:
    • replace
      wrapper.java.library.path.1=%LD_LIBRARY_PATH%
      wrapper.java.library.path.2=%MULE_HOME%/lib/boot

      with:

      wrapper.java.library.path.1=%LD_LIBRARY_PATH%
      wrapper.java.library.path.2=%MULE_HOME%/lib/boot
      wrapper.java.library.path.3=%TIBRV_HOME%/bin

Here is for the very configuration.

“Hello world” for “TibcoRV via Mule”

Configuration file for Mule/TibcoRV “Hello World”

Code below is commented. Save it into a file named mule-config.xml.

[xml]<?xml version="1.0" encoding="UTF-8" ?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns:management="http://www.mulesource.org/schema/mule/management/2.2"
xmlns:tibcorv="http://www.mulesource.org/schema/mule/tibcorv/2.2"
xmlns:stdio="http://www.mulesource.org/schema/mule/stdio/2.2"
xsi:schemaLocation="http://www.mulesource.org/schema/mule/management/2.2
http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd
http://www.mulesource.org/schema/mule/core/2.2
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.mulesource.org/schema/mule/vm/2.2
http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
http://www.mulesource.org/schema/mule/tibcorv/2.2
http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd
http://www.mulesource.org/schema/mule/stdio/2.2
http://www.mulesource.org/schema/mule/stdio/2.2/mule-stdio.xsd">
<!– The TibcoRV we’re listening is on the IP#127.0.0.1 –>
<tibcorv:connector name="myTibcoConnector" network="127.0.0.1"/>
<model name="fromTibco2stout">
<service name="fromTibco">
<inbound>
<!– We follow all subjects, on the TibcoRV connector defined above–>
<tibcorv:inbound-endpoint connector-ref="myTibcoConnector" subject="*"/>
</inbound>
<echo-component/>
<outbound>
<pass-through-router>
<!– Messages received are displayed on standard output –>
<stdio:outbound-endpoint address="stdio://OUT"/>
</pass-through-router>
</outbound>
</service>
</model>
</mule>
[/xml]

Run TibcoRV

Launch the daemon

Launch the daemon on localhost on port 7580:

%TIBRV_HOME\bin\rvd -http 7580

Launch a listener

Possibly, you can run a listener in a separate frame, in order to double check whether messages are sent and received in the right way, independantly of what happens on Mule side.
Listen to all messages with subject mySubject on localhost:7580

%TIBRV_HOME\bin\tibrvlisten.exe" -network localhost mySubject

Launch the Mule

  • Now run the ESB:
    %MULE_HOME%\bin\mule.bat -config path\to\file\mule-config.xml
  • Send a message:
    %TIBRV_HOME\bin\tibrvsend.exe -network 127.0.0.1  mySubject HelloWorld
  • Expected outputs:
    • On sending frame:
      Publishing: subject=mySubject "HelloWorld"
    • On listening frame:
      tibrvlisten: Listening to subject mySubject
      2010-01-21 17:51:43 (2010-01-21 16:51:43.109000000Z): subject=mySubject, message={DATA="HelloWorld"}
    • On Mule ESB frame:
      INFO  2010-01-21 17:53:02,860 [Bus] org.mule.transport.tibrv.TibrvMessageReceiver: message received
      on: *
      INFO  2010-01-21 17:53:02,860 [fromTibco.4] org.mule.transport.tibrv.TibrvMessageAdapter: The newThreadCopy method in AbstractMessageAdapter is being used directly. This code may be susceptible to 'scribbling' issues with messages. Please consider implementing the ThreadSafeAccess interface in the message adapter.
      INFO  2010-01-21 17:53:02,860 [fromTibco.4] org.mule.component.simple.LogComponent:
      ********************************************************************************
      * Message received in service: fromTibco. Content is: '{                       *
      * DATA="HelloWorldOfTheWorld" }'                                               *
      ********************************************************************************
      INFO  2010-01-21 17:53:02,860 [connector.stdio.0.dispatcher.3] org.mule.transport.stdio.StdioMessageDispatcher: Connected: endpoint.outbound.stdio://OUT
      {DATA=HelloWorldOfTheWorld, __send__subject__=mySubject}

PostHeaderIcon Tibco RendezVous quick-start tutorial

When I was introduced to TIBCO Rendezvous (also spelled “Tibco Rendez-Vous” or, shorterly, “TiboRV”), I faced a embarrassing issue: the lack of documentation and tutorials on the web.

The purpose of this -short- tutorial is to guide you until you can send and read a “HelloWorld” message passing through Tibco RendezVous

Installation

  • Set the variable JAVA_HOME
    Eg, in my case:

    set JAVA_HOME=C:\exe\java\jdk150_10
  • Get the file to be installed:
    TIB_rv_8.1.2_win_x86_vc8.zip
  • Unzip the content in your local drive
  • Launch the installer (.exe)
    • select Custom installation
    • choose the installation folder, eg: C:\exe\tibco
    • keep default options for other requests
  • Set the variable TIBRV_HOME
    Eg, in my case:

    set TIBRV_HOME=C:\exe\tibco\tibrv\8.1

Main Runnables

RVD: Daemon

  • Launching the daemon on local host on port 8181 (default port: 7580):
    rvd -http 8181

    You should see the following trace:

    C:\exe\tibco\tibrv\8.1\bin>rvd -http 8181
    
    TIB/Rendezvous daemon
    Copyright 1994-2008 by TIBCO Software Inc.
    All rights reserved.
    
    Version 8.1.2 V8 9/26/2008
    2010-01-19 16:37:02 rvd: Command line: rvd -http 8181
    2010-01-19 16:37:02 rvd: Hostname: MYLOCALMACHINE
    2010-01-19 16:37:02 rvd: Hostname IP address: 123.123.123.123
    2010-01-19 16:37:02 rvd: Detected IP interface: 123.123.123.123 (IP00)
    2010-01-19 16:37:02 rvd: Detected IP interface: 127.0.0.1 (loopback)
    2010-01-19 16:37:02 rvd: Unable to find ticket file tibrv.tkt in PATH
    2010-01-19 16:37:02 rvd: Http interface - http://myLocalMachine.myDomain:8181/

tibrvsend: send a message

To send a message on myLocalMachine:7580:

.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage

Expected output:

C:\exe\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage
Publishing: subject=mySubject "myMessage"
2010-01-19 16:52:11 RV: TIB/Rendezvous Error Not Handled by Process:
{ADV_CLASS="WARN" ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" expiretime=2010-01-19 16:02:11Z host="10.30.226.147"}

tibrvlisten: listen to messages

Abstract

To listed to messages published on MYLOCALMACHINE:7580, related to subject mySubject:

tibrvlisten -service 7580 -network MYLOCALMACHINE mySubject

Use case: HelloWorld

For instance, let’s assume that you launch this command from one frame:

C:\exe\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network localhost mySubject HelloWorld
Publishing: subject=mySubject "HelloWorld"

Here is what appears in the “listening” frame:

2010-01-19 17:01:32 (2010-01-19 16:01:32.990000000Z): subject=mySubject, message={DATA="HelloWorld"}

Notice you can have many instances listening to the same messages.

Other runnables

Launch the daemon manager

  • Launch:
    cd %TIBRV_HOME%/RVDM
    ./RVDM.bat -http 8282 .
  • You should see following messages, that you can ignore:
    2010-01-19 13:01:48 rvdm: RVDM has activated.
    2010-01-19 13:02:03 RV: TIB/Rendezvous Error Not Handled by Process:
    {ADV_CLASS="WARN" ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" e
    xpiretime=2010-01-19 12:11:48Z host="123.123.123.123"}
  • To check the daemon is on, you can open the address http://localhost:8282 on your favorite browser.

Example sources

Example sources are available in folder %TIBRV_HOME%/src/examples/java

Misc

TIBRV_HOME\bin folder fosters a couple of binaries:

  • rvntscfg.exe: Services Configuration Program

PostHeaderIcon Servlet of class org.apache.catalina.servlets.CGIServlet is privileged and cannot be loaded by this web application

Case:

Under Windows / Tomcat 6:

[java]java.lang.SecurityException: Servlet of class org.apache.catalina.servlets.CGIServlet is privileged and cannot be loaded by this web application[/java]

Fix:

In the web.xml file, add the following block:

[xml]
<context-param>
<param-name>privileged</param-name>
<param-value>true</param-value>
</context-param>[/xml]

PostHeaderIcon SkyFire: Flash for Windows Mobile 6.1

By default, animations in Adobe Flash are not readable on Windows Mobile 6.1 smartphones. I tried to download a plugin for Internet Explorer, Mozilla Fennec and Opera Mobile 10, with no success.

At last, I found this very nice browser: SkyFire. At first glance, I think the browser works thanks to a proxy deployed in SkyFire headquarters. I did not investigate more than that.

Yet, what is sure is that from now and then, I can watch Adobe Flash SWF, WMA and even SilverLight animations.

In the upcoming days, I will publish a short comparative study of browsers available on Windows Mobile.

PostHeaderIcon Use p6spy with BEA WebLogic 9.2

Case:

You need debug information on SQL queries, for an application within BEA WebLogic 9.2. You need p6spy.

P6spy is a jar which play the role of a bridge between your application and your actual JDBC driver (in my case: oracle.jdbc.driver.OracleDriver for Oracle 10g)

Solution:

  • Change JDBC Driver in Weblogic Web Console
    • Services > JDBC > Data Sources > (your data source) > Configuration > Connection Pool > Driver Classname  =  com.p6spy.engine.spy.P6SpyDriver
  • Copy p6spy-1.3.jar and spy.properties in %WL_HOME%/servers/lib/ext
  • Check that spy.properties contains : realdriver=oracle.jdbc.driver.OracleDriver
  • In the spy.properties choose the stdoutLogger,  rather than log4jLogger appender
  • In the CLASSPATH of startManagedWebLogic.cmd, add the following path:%WL_HOME%/servers/lib/ext/p6spy-1.3.jar;%WL_HOME%/servers/lib/ext

PostHeaderIcon JAXB2 in WebLogic 9.2

Case:

We need use JAXB2 packaged version, rather than the version which is provided within WebLogic 9.2.

Fix:

In the weblogic-application.xml, add the following block:

[xml]
<prefer-application-packages>
<package-name>javax.xml.bind.*</package-name>
</prefer-application-packages>
[/xml]