JVM Peer Gone in WebLogic T3 connection

So I have this exception when connecting to a FileNet P8 API from my Linux Machine:

com.filenet.api.exception.EngineRuntimeException: FNRCE0040E: E_NOT_AUTHENTICATED: The user is not authenticated. Message was: java.net.ConnectException: t3://1.2.3.4:9210: Bootstrap to 1.2.3.4/1.2.3.4:9210 failed. It is likely that the remote side declared peer gone on this JVM  at com.filenet.apiimpl.core.UserPasswordToken.getSubject(UserPasswordToken.java:121)
 at com.filenet.api.util.UserContext.createSubject(UserContext.java:288)

This happens when my application is connecting to FileNet P8 Content Engine deployed into a WebLogic Cluster and not into a single node (Well it might happen with a single node…). The connection point used by the application is a single node address.

The solution for this error message?

Just add to the host files of the client machine the name and ip address of each weblogic cluster physical machine.

Advertisements

LogStash and IBM FileNet P8 5.2 logs

At work, the production environment of FileNet P8 5.2 is deployed on several Oracle WebLogic server instances. This means when a problem crops up, I have a lot of of log files to analyze…. Not an easy task to find and correlate an error with so many instances and log files.

A solution exists for this madness of log files… In fact we have Splunk to ingest and to manage the log files of several applications. But Splunk is licensed by volume, and it’s expensive, and I can’t touch it… Not helping my work, so…

So I’m checking out logstash and it’s web interface Kibana.

The main FileNet P8 5.2 log files are the p8_server_error.log file and the pesvr_system.log file, for Content Engine and Process Engine.

These files are located under the Content Engine domain on a directory named FileNet and sub-divided by server instance.

So to keep thing short, here it is a logstash agent file that monitors and sends the logs to a REDIS remote instance:

input {
        ## P8 Content Engine CE1 Server Log
        file {
                type => “IBMP8_CE”
                path => [ “/weblogic/user_projects/domains/fnce/FileNet/CeServer01/p8_server_error.log” ]
                codec => multiline {
                        ##pattern => “^\s”
                        pattern => “^%{TIMESTAMP_ISO8601}”
                        negate => true
                        what => “previous”
                }
                tags => [“P8CEServerLog”]
        }

        ## P8 Process Engine CE1 System Log
        file {
                type => “IBMP8_PE”
                path => [ “/weblogic/user_projects/domains/fnce/FileNet/CeServer01/pesvr_system.log” ]
                codec => multiline {
                        ##pattern => “^\s”
                        pattern => “^(?>\d\d){1,2}”
                        negate => true
                        what => “previous”
                }
                tags => [“P8CEServerLog”]
        }
}

output {
  stdout { codec => rubydebug }
  redis { host => “redis_server.domain.com” data_type => “list” key => “logstash” }
}

You should change the redis_server.domain.com to your redis real ip/name, and after debugging, disable the stdout line.

Yo can add several input files for each server instance that is co-located on the same server machine.

 

P8 Process Engine Process Administrator Date Format

For those that are using the P8 FileNet products, specifically the Process Engine Process Administrator tool, may have the need to do a search based in dates values, like, for example, if F_StartTime is greater than yesterday.

The date format for using as the parameter is the following: MM/DD/YYYY HH:MM AM/PM

For example: 06/20/2012 15:00 pm or 06/20/2012 08:00 am

The Process Administrator then inserts the date value with the UNIX timestamp format on the search condition.

An online tool as: http://www.onlineconversion.com/unix_time.htm can be used to convert the values back and forth between formats.

P8 5.0 on CentOS/Redhat install

If by any chance, during the setup launching this happens:

Preparing to install…
Extracting the JRE from the installer archive…
Unpacking the JRE…
Extracting the installation resources from the installer archive…
Configuring the installer for this system’s environment…

Launching installer…

Graphical installers are not supported by the VM. The console mode will be used instead…

Preparing CONSOLE Mode Installation…

=======================================================

Installer User Interface Mode Not Supported

The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The valid UI modes identifiers are GUI, Console, and Silent.

=======================================================

Just install de compatibility libstd to your system:

yum install compat-libstdc++-33.i386