Suse Linux Enterprise Deskstop

versaulis · 08-14-2008, 04:44 PM

I'm trying to run BEA Weblogic on a Suse Linux Enterprise Desktop system and I cannot connect to the server from any other IP than 127.0.0.1, locally. Samba wasn't working either, but I told the firewall to allow the Samba service and now that is working. I told the firewall to allow port 7001 on TCP, which should get Weblogic working, but it does not. I still cannot connect to it, externally.

Weblogic never mentions my ip address, directly. Only the local addresses. I don't know *exactly* what I'm asking when I say this, but could it be that Weblogic is not binding to the correct address? Is that a Linux configuration issue or a Weblogic issue? How might I fix it?

Code:

startWebLogicDebug.sh
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m  -XX:MaxPermSize=128m
.
WLS Start Mode=Development
.
CLASSPATH=:/home/weblogic/bea/patch_wls1000/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.5.0_15/lib/tools.jar:/home/weblogic/bea/wlserver_10.0/server/lib/weblogic_sp.jar:/home/weblogic/bea/wlserver_10.0/server/lib/weblogic.jar:/home/weblogic/bea/modules/features/weblogic.server.modules_10.0.0.0.jar:/home/weblogic/bea/modules/features/com.bea.cie.common-plugin.launch_2.1.0.0.jar:/home/weblogic/bea/wlserver_10.0/server/lib/webservices.jar:/home/weblogic/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/weblogic/bea/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/home/weblogic/bea/wlserver_10.0/common/eval/pointbase/lib/pbclient51.jar:/home/weblogic/bea/wlserver_10.0/server/lib/xqrl.jar::
.
PATH=/home/weblogic/bea/wlserver_10.0/server/bin:/home/weblogic/bea/modules/org.apache.ant_1.6.5/bin:/usr/java/jdk1.5.0_15/jre/bin:/usr/java/jdk1.5.0_15/bin:/home/weblogic/bea/user_projects/domains/base_domain/bin:/home/weblogic/bea/user_projects/domains/base_domain/bin:/home/weblogic/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/opt/novell/iprint/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing)
Starting WLS with line:
/usr/java/jdk1.5.0_15/bin/java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m  -XX:MaxPermSize=128m -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=5555,suspend=n -Djava.compiler= -Xverify:none  -da -Dplatform.home=/home/weblogic/bea/wlserver_10.0 -Dwls.home=/home/weblogic/bea/wlserver_10.0/server -Dweblogic.home=/home/weblogic/bea/wlserver_10.0/server -Dwli.home=/home/weblogic/bea/wlserver_10.0/integration  -Dweblogic.management.discover=true  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/weblogic/bea/patch_wls1000/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogic/bea/wlserver_10.0/server/lib/weblogic.policy   weblogic.Server
Listening for transport dt_socket at address: 5555
<Aug 14, 2008 5:39:31 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/home/weblogic/bea/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/p13n/p13n_system.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/wlp/netuix_system.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/home/weblogic/bea/wlserver_10.0/platform/lib/wlp/wsrp-common.jar>
<Aug 14, 2008 5:39:32 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_15-b04 from Sun Microsystems Inc.>
<Aug 14, 2008 5:39:32 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0  Wed May 9 18:10:27 EDT 2007 933139 >
<Aug 14, 2008 5:39:34 PM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home/weblogic/bea/license.bea>
<Aug 14, 2008 5:39:34 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 14, 2008 5:39:34 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 14, 2008 5:39:35 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<Aug 14, 2008 5:39:38 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 14, 2008 5:39:44 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Aug 14, 2008 5:39:44 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 14, 2008 5:39:45 PM EDT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
<Aug 14, 2008 5:39:45 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 14, 2008 5:39:45 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Aug 14, 2008 5:39:47 PM EDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file /home/weblogic/bea/wlserver_10.0/server/lib/DemoIdentity.jks.>
<Aug 14, 2008 5:39:47 PM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea/wlserver_10.0/server/lib/DemoTrust.jks.>
<Aug 14, 2008 5:39:47 PM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /usr/java/jdk1.5.0_15/jre/lib/security/cacerts.>
<Aug 14, 2008 5:39:48 PM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<Aug 14, 2008 5:39:48 PM EDT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, https.>
<Aug 14, 2008 5:39:48 PM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode>
<Aug 14, 2008 5:39:48 PM EDT> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1>
<Aug 14, 2008 5:39:49 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Aug 14, 2008 5:39:49 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

TB0ne · 08-14-2008, 04:52 PM

I had a similar problem with OpenSuSE. Locally, things worked fine, but you couldn't access the box otherwise. The firewall rules blocked incoming web traffic, so after modifying that through YAST, and restarting the firewall, things worked fine. That may be what you're seeing here, too, but I don't know. Haven't played with Weblogic, so I don't know what's involved with it.

versaulis · 08-14-2008, 07:34 PM

I have made several changes to the firewall and tried restarting it, as well as the whole system. No luck thus far.

chort · 08-15-2008, 01:10 AM

It looks like your hostname is being detected as simply "localhost", so it's only binding to the loopback adaptor. Also, how is anyone supposed to know if the firewall changes would even help when you just say "i mad several changes"??? If you don't say what you tried, no one is going to know what else to suggest.

Also, when you post really obnoxiously long lines from a log file, wrap them in CODE /CODE tags to fix the wrapping.

versaulis · 08-15-2008, 07:27 AM

Quote:

Originally Posted by chort

It looks like your hostname is being detected as simply "localhost", so it's only binding to the loopback adaptor. Also, how is anyone supposed to know if the firewall changes would even help when you just say "i mad several changes"??? If you don't say what you tried, no one is going to know what else to suggest.

Also, when you post really obnoxiously long lines from a log file, wrap them in CODE /CODE tags to fix the wrapping.

Service with a smile :P

chort · 08-16-2008, 11:06 AM

Sigh, it looks like code tags don't auto-fit the margins any more

Any way, did you check your /etc/hosts file to see if your hostname is defined properly there?

Did you check WebLogic config files to see if any of them have the hostname listed as "localhost" instead of the real hostname?

I doubt you'll be able to connect externally until you convince WebLogic to bind to something other than 127.0.0.1.

versaulis · 09-17-2008, 04:55 PM

Turns out that there is a configuration item within Weblogic where you have to specify that you want it to bind to all local addresses. You can find it within the configuration that you generate when you create a new server.