Usage Note 16562: A WebLogic connection error occurs when you attempt to log in to SASĀ® Campaign Studio
You might receive the following error from Oracle WebLogic when you attempt to log in to SAS Campaign Studio:
Caused by: weblogic.jms.common.JMSException:
Error creating connection on the server.
The error is further defined in the WebLogic logs, as follows:
weblogic.jms.dispatcher.DispatcherException: Could not register a
HeartbeatMonitorListener for ...
This message might appear if a firewall is in place and a callback process is being terminated.
The Java client calls Oracle WebLogic on port 7001, and then Oracle Weblogic starts the Java Message Service and a bean that functions as a "listener" in order to monitor the status of the client connection.
This listener in Oracle WebLogic is a Java class that is trying to connect
back to the Java client (in this case, SAS Campaign Studio or SAS® Management Console).
The firewall stops this callback to the Java client, because the call is on a new port.
In addition to the preceding error, you might also see the following error if you are trying to create a definition in SAS Management Console:
CORBA MARSHAL 0
If this problem occurs in SAS® Customer Intelligence,
then add the following JVM argument to the sasmaclient.ini file:
SAS Customer Intelligence 5.1 - Dweblogic.corba.client.bidir=true
SAS Customer Intelligence 5.3 - JavaArgs_9=-Dweblogic.corba.client.bidir=true
Adding this argument defines that SAS Customer Intelligence Studio shall use the same port for the calls back and forward.
If the error occurs in the SAS Customer Intelligence plug-ins for SAS Management Console, then modify the sasmc.ini file and add the same JVM argument as shown above.
The argument needs to be added before the -cp option in the command line arguments string:
CommandLineArgs=-Xms128m -Xmx1024m -Djava.system.class.loader=com.sas.app.AppClassLoader -Dsas.app.class.dirs="C:\Program
Files\SAS\SASMarketingAutomation\4.1" -Dsas.app.class.path=sas.analytics.crm.ma.app.jar;. -Dsas.ext.config=sas.java.ext.config -
Dweblogic.corba.client.bidir=true -cp sas.launcher.jar com.sas.analytics.crm.app.Client
Operating System and Release Information
| SAS System | SAS Customer Intelligence Studio | Microsoft Windows Server 2003 Datacenter Edition | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2008 | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 5.1 | | 9.1 TS1M3 SP4 | |
| Windows Vista | 5.1 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The note describes the situations in which you might receive WebLogic errors and explains what to do about them.
| Type: | Usage Note |
| Priority: | high |
| Topic: | System Administration ==> Installation
|
| Date Modified: | 2019-05-09 09:53:09 |
| Date Created: | 2005-11-21 16:27:18 |