Unsolved
This post is more than 5 years old
3 Posts
0
14539
February 18th, 2004 21:00
Login and initializing error
After the installation had completed, the appserver icon in the task tray doesn't get any further than having a yellow indicator says it's initializing. I have let it sit here for at least 30-45 min. and still nothing. Next I started the Network Manager and the Logon screen appeared. I entered admin for the user name and nothing for the password. After a few seconds the logon screen disappeared and another screen appeared stating that the logon password has expired and promted me to enter the old password, a new password and confirm new password. I entered a new password and clicked the OK button and a few seconds after that I got the error: com.dorado.runtime.OWEventException I closed the network manager and started it again and this time at the logon screen I entered admin with the new password and it tells me Invalid Logon, so then I tried it with a blank password and it too says invalid logon. I closed it down and restarted my computer and tried it again, but I get the same result. Any ideas? I know this has been talked about before, but I don't see in the fourm that it has been resovled. Thanks!!
bcharamu
16 Posts
0
February 19th, 2004 00:00
It appears that JMS may have failed to start. Your appserver may be waiting for JMS to start so it can load dependent services.
You may be able to avoid this issue by using an IP address instead of a hostname when prompted by the installer.
However, it would be best if you posted:
OWARE.CONTEXT.SERVER.URL line from {INSTALL_DIR}\owareapps\installprops\lib\installed.properties
as well as:
{INSTALL_DIR}\oware\temp\sonicmq_appserver.log
and any log files of the form
{INSTALL_DIR}\owareapps\redcell\logs\*.log
which have a modified date corresponding to the failed login attempt.
Because the error occurred during login, it is likely that the client logs will not contain much information that is helpful (if any). We are attempting to change that, but in the meantime, the other two logs should provide us with quite a bit of information.
Below, I attach the text from an email regarding a problem which had the same appearance. In addition to the scenario outlined below, in one instance I had to add the DNS suffix for the connection (TCP\IP properties, Advanced button, DNS tab on Windows XP) before I could ping the hostname successfully and resolve the connection issue. Others have simply added entries to:
%SYSTEM_ROOT%\System32\Drivers\etc\hosts
If you run the commands detailed below, you could also attach that output if unable to resolve the issue.
It may seem like I'm asking for a lot of information, but examining the logs is the best and sometimes only way to solve these types of issues quickly, if at all.
...
I am not able to answer definitively without more information.
We have encountered a problem in house with our integration of DHCP and DNS which caused a standalone server/client to be unable to connect to JMS. If DHCP is used on the server, this is a possibility. The commands detailed below would uncover this scenario as Windows would report a different hostname than DNS, and DNS would be unable to resolve the dynamically-created hostname it returns to an IP address. I'm hoping this is a problem unique to out network, and generally uncommon.
It also is possible a reverse DNS lookup is taking place on the client. I know reverse DNS is used on the server. If a reverse DNS lookup fails on the server, the client may need to perform a lookup on the server's hostname to connect via RMI. I have not yet examined the server code to determine if reverse DNS is used during the creation of the RMI stub.
Any error messages received on the client, as well as the server logs (oware/server/jboss-3.0.8/server/oware/log/*.log), and the JMS log (oware/temp/sonicmq_appserver.log) would be necessary in order to try to pin it down. Also, I would need to know the previous and current contents of the hosts file on the client, and whether or not several different pings and nslookups succeed or fail on the server and client (for the client, before and after the hosts file change).
Although I am currently working on providing more standard debug in the case of connection failures during login, it is likely that the client will not provide much information. In the case of a failure to connect to JMS, the client login screen usually contains an exception message (not a trace) which indicates a "com.dorado.runtime.OWEventException".
Generally, when I encounter a connection problem, I perform these commands:
ipconfig /all
Note the setting of these parameters in particular:
Primary DNS Suffix
Connection-specific DNS Suffix
DHCP Enabled
DNS Servers
Currently, the released versions of our product do not support multiple NICs.
Examine %SYSTEM_ROOT%/system32/drivers/etc/hosts.
ping > --> IP (via WINS)
nslookup > --> IP
Execute these commands both with and without the proper domain suffix.
ping > --> IP (via WINS* or DNS)
nslookup > --> IP (via DNS)
Execute these commands both with and without the proper domain suffix.
ping -a --> DNS hostname
nslookup --> DNS hostname
From the client, these commands should be executed for the server's hostname and IP as well (including the server's Windows hostname if applicable).
* WINS would be used by Windows if the DNS hostname matched the DNS hostname.
This technique has been used to discover or rule out several different potential problems.
KJBorowski
3 Posts
0
February 19th, 2004 11:00
Ok here are the files you are looking for. First is the installed.properties file and the next one is the sonicmq.log
#************************************************************
# The following properties override those found in *
# oware/lib/*.properties in order to establish valid *
# properties for this installation. *
#************************************************************
oware.database.host=3u4di
# Preferred database type
# valid values:
# odbms - to use a Versant database
# rdbms - for all supported relational databases
com.dorado.bom_dbms.preferred_db_type=odbms
#************************************************************
# RDBMS Properties for Oracle
#
# Logon Information for using relational databases
com.dorado.jdbc.user=oware
com.dorado.jdbc.password=dorado
#
# Primary database server property - Oracle
# uncomment and configure when using Oracle
#com.dorado.jdbc.database_name.oracle=@host:port:SID
#
# Secondary database server property - Oracle
# This must be specified when the relational database fail-over
# property is enabled.
#com.dorado.jdbc.secondary_database_name.oracle=@host:port:SID
#
## RDBMS Replication/Failover Properties
##
## The replication_enabled property will enable support for Oracle replication.
## If this property is set to true, Oracle must be installed with the advanced
## replication option enabled. The replication catalog tables (catrep.sql) need
## to be created before Oware tables and procedures are created. Please see
## Oracle's replication documents and Oware's configuration and admin guide
## for more details.
##
## Do not modify this property once the database is created.
## Valid values are true or false.
com.dorado.jdbc.oracle_replication_enabled=false
##
## Relational database fail over enabled flag.
## A secondary database server must be specified while this property is enabled.
## Valid values are true or false.
com.dorado.rdbms.failover_enabled=false
##
## Database server failover delay in seconds
com.dorado.rdbms.db_failover_delay=10
##
oware.installed.package.name=Dell OpenManage Network Manager
oware.installed.package.version=DELLNM.1.0.0.71.3
OWARE.CONTEXT.SERVER.URL=jnp://3u4di:1099
OWJMSSonicStartupHelper is waiting for config file: c:/progra~1/dell/openma~1/networ~1/oware/temp/sonicmq/owAppServerjms172_17_23_208.ini.
...............................
Build sequence for target `startSonicMQ' is [init, buildsonicdb, startSonicMQ]
Complete build sequence is [init, buildsonicdb, startSonicMQ, buildsonicbase]
init:
Override ignored for property sonic.ini.file
Override ignored for property sonicmq.cp
Unable to find C:\progra~1\dell\openma~1\networ~1\oware\temp\sonicmq\db\AppServer\172_17_23_208\sonicmqdb\cloudscape.db
buildsonicdb:
Created dir: C:\progra~1\dell\openma~1\networ~1\oware\temp\sonicmq\log\AppServer\172_17_23_208
Running createdb ...
Current OS is Windows 2000
Executing 'c:\progra~1\dell\openma~1\networ~1\oware3rd\sonicmq\bin\createdb' with arguments:
'c:/progra~1/dell/openma~1/networ~1/oware/temp/sonicmq/db/AppServer/172_17_23_208/sonicmqdb'
The ' characters around the executable and arguments are
not part of the command.
Running dbtool ...
Current OS is Windows 2000
Executing 'c:\progra~1\dell\openma~1\networ~1\oware3rd\sonicmq\bin\dbtool' with arguments:
'-f'
'c:/progra~1/dell/openma~1/networ~1/oware/temp/sonicmq/owAppServerjms172_17_23_208.ini'
'-c'
'b'
'i'
The ' characters around the executable and arguments are
not part of the command.
startSonicMQ:
Could not find file C:\progra~1\dell\openma~1\networ~1\oware\temp\sonicmqdownflagfile.txt to delete.
Current OS is Windows 2000
Executing 'c:\progra~1\dell\openma~1\networ~1\oware\bin\execsonic' with arguments:
'c:/progra~1/dell/openma~1/networ~1/oware/temp/sonicmq/owAppServerjms172_17_23_208.ini'
The ' characters around the executable and arguments are
not part of the command.
.
Creating table TxnMessages.
Creating table SyncPoint.
Creating table BrokerMode.
Creating table PBMsgInfo.
Creating index PBMsgInfoIdx.
Creating table PBMsgs.
Creating index PBMsgIdx.
Creating table CbrSubs.
Creating index CBRSubIdx.
Creating table MFR.
Creating index MfrIdx.
Setting security mode
Setting sync point
Creating table LogTime.
Creating table BrokerInfo.
Creating table QueueRegistry.
Creating index QRegIdx.
Creating table RoutingConns.
Creating index RConnsIdx.
Creating table RouteInfo.
Creating index NodeGlBrIdx.
Creating table RBRegistry.
Creating index RBRegCIDIdx.
Setting log time
Initializing broker recovery log files...
Broker Database initialization is complete.
Creating table TxnIndices.
Creating index TxnIndicesIdx.
InitBrokerDatabase terminates.
Creating table IBDBVer.
Creating table Topology.
Creating index TopoIdx.
Creating table BrokerConnS.
Creating index BCSIdx.
Creating table IBUCount.
Creating table IBSTime.
Interbroker Database initialization is complete.
InitInterbrokerDatabase terminates.
Executing Sonic: -ms128m -mx256m -Xss84k -XX:MaxPermSize=128m -ms16m -mx256m -Dant.home=c:/progra~1/dell/openma~1/networ~1/oware3rd/ant-1.5.1 -Doware.appserver.password=trustnoone -DSonicMQ.TCP_NODELAY=true -Dsun.net.inetaddr.ttl=-1 -Doware.jms.vendor=sonicmq -Dsonicmq.home=c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq -Doware.home=c:/progra~1/dell/openma~1/networ~1/oware -Djvi.os=nt -Djdk.os.ver=jdk1.3 -Doware.user.root=c:/progra~1/dell/openma~1/networ~1 -Doware.3rdparty=c:/progra~1/dell/openma~1/networ~1/oware3rd -Doware.user.class.path=c:/progra~1/dell/openma~1/networ~1/owareapps;. -Doware.meta.class.path=c:/progra~1/dell/openma~1/networ~1/oware/lib/owmeta.jar -Doware.ver= -Doracle.home= -Dversant.version=6_0_0 -Doware.owjavac=c:/progra~1/dell/openma~1/networ~1/oware/bin/owjavac.exe -Djava.protocol.handler.pkgs=com.dorado.protocols -Dcp.conf.file=c:/progra~1/dell/openma~1/networ~1/oware/conf/owlaunch.xml -DJBOSS_ROOT=c:/progra~1/dell/openma~1/networ~1/oware/jboss-3.0.8 -DOWARE_ROOT=c:/progra~1/dell/openma~1/networ~1/oware -DOWARE_USER_ROOT=c:/progra~1/dell/openma~1/networ~1 -DJAVA_HOME=c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt -DVERSANT_LIB=c:/progra~1/dell/openma~1/networ~1/oware3rd/versant/6_0_0/nt/lib -DVERSANT_JVI_ARCHIVE=jvi6.0.0-jdk1.2.jar -DORACLE_JDBC_CLASSES= -Doware.first.primary.server=3u4di -DMULTICAST_IP= -Dsonic.conf.file=c:/progra~1/dell/openma~1/networ~1/oware/conf/sonicmq.xml -Dsonicmq.cp=c:/progra~1/dell/openma~1/networ~1/oware3rd/ant-1.5.1/lib/ant.jar;c:/progra~1/dell/openma~1/networ~1/oware/lib/sonicdsp.jar;c:/progra~1/dell/openma~1/networ~1;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/broker.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jetty.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/defdb_server.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/certj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/sslj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jsafe.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/bridgeAdmin.jar -Dnode.num= -Doware.server.type=AppServer -Doware.processid=1824 -Dsonic.conf.file=c:/progra~1/dell/openma~1/networ~1/oware/conf/sonicmq.xml -Dsonicmq.cp=c:/progra~1/dell/openma~1/networ~1/oware3rd/ant-1.5.1/lib/ant.jar;c:/progra~1/dell/openma~1/networ~1/oware/lib/sonicdsp.jar;c:/progra~1/dell/openma~1/networ~1;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/broker.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jetty.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/defdb_server.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/certj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/sslj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jsafe.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/bridgeAdmin.jar -Dant.home=c:/progra~1/dell/openma~1/networ~1/oware3rd/ant-1.5.1 -Doware.appserver.password=trustnoone -DSonicMQ.TCP_NODELAY=true -Dsun.net.inetaddr.ttl=-1 -Doware.jms.vendor=sonicmq -Dsonicmq.home=c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq -Doware.home=c:/progra~1/dell/openma~1/networ~1/oware -Djvi.os=nt -Djdk.os.ver=jdk1.3 -Doware.user.root=c:/progra~1/dell/openma~1/networ~1 -Doware.3rdparty=c:/progra~1/dell/openma~1/networ~1/oware3rd -Doware.user.class.path=c:/progra~1/dell/openma~1/networ~1/owareapps;. -Doware.meta.class.path=c:/progra~1/dell/openma~1/networ~1/oware/lib/owmeta.jar -Doware.ver= -Doracle.home= -Dversant.version=6_0_0 -Doware.owjavac=c:/progra~1/dell/openma~1/networ~1/oware/bin/owjavac.exe -Djava.protocol.handler.pkgs=com.dorado.protocols -Dcp.conf.file=c:/progra~1/dell/openma~1/networ~1/oware/conf/owlaunch.xml -DJBOSS_ROOT=c:/progra~1/dell/openma~1/networ~1/oware/jboss-3.0.8 -DOWARE_ROOT=c:/progra~1/dell/openma~1/networ~1/oware -DOWARE_USER_ROOT=c:/progra~1/dell/openma~1/networ~1 -DJAVA_HOME=c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt -DVERSANT_LIB=c:/progra~1/dell/openma~1/networ~1/oware3rd/versant/6_0_0/nt/lib -DVERSANT_JVI_ARCHIVE=jvi6.0.0-jdk1.2.jar -DORACLE_JDBC_CLASSES= -cp c:/progra~1/dell/openma~1/networ~1/oware3rd/ant-1.5.1/lib/ant.jar;c:/progra~1/dell/openma~1/networ~1/oware/lib/sonicdsp.jar;c:/progra~1/dell/openma~1/networ~1;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/broker.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jetty.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/defdb_server.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/certj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/sslj.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/jsafe.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/sonicmq/lib/bridgeAdmin.jar;c:/progra~1/dell/openma~1/networ~1/oware/jboss-3.0.8/server/oware/deploy/oware.sar;c:/progra~1/dell/openma~1/networ~1/oware;c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt/lib/dt.jar;c:/progra~1/dell/openma~1/networ~1/oware/lib3rd/gnu-regexp-114.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt/jre/lib/rt.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt/jre/lib/security;c:/progra~1/dell/openma~1/networ~1/oware3rd/jdk1.3nt/lib/jpda.jar;;c:/progra~1/dell/openma~1/networ~1/oware/lib/owjoshua.jar;;c:/progra~1/dell/openma~1/networ~1/oware/oware.sar/oware.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/loox/jloox13.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/loox/jlm13.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/loox/OWLoox.jar;c:/progra~1/dell/openma~1/networ~1/oware3rd/loox/jlayout.jar;c:/progra~1/dell/openma~1/networ~1/owareapps;. progress.message.broker.Broker c:/progra~1/dell/openma~1/networ~1/oware/temp/sonicmq/owAppServerjms172_17_23_208.ini
SonicMQ Professional Developer Edition [Serial Number 62005468]
Release 4.0.2 Build Number 106 Protocol P24
Copyright (c) 2001 Sonic Software Corporation. All Rights Reserved.
Starting broker "b3u4di_trp2506".
There is no limit on the number of concurrent connections.
Interbroker is enabled.
Routing node name is "P3U4DIPartition".
Security is disabled.
Waiting to connect to config server at 3u4di:2506
bcharamu
16 Posts
0
February 19th, 2004 17:00
The startup process was unable to determine that "3u4di" was the local machine. It is likely that this is the machine's Windows hostname, and that the DNS hostname differs, of that lookup requires that the domain suffix be appended to it. Did you execute these commands?
ping Windows hostname --> IP (via WINS)
nslookup Windows hostname --> IP
Execute these commands both with and without the proper domain suffix.
ping DNS hostname --> IP (via WINS* or DNS)
nslookup DNS hostname --> IP (via DNS)
Execute these commands both with and without the proper domain suffix.
ping -a IP --> DNS hostname
nslookup IP --> DNS hostname
You may find that WINS returns the proper IP, but that DNS does not.
Adding an entry to the hosts file containing the IP for the host "3u4di" may solve the problem. Ensure you do an:
ipconfig /flushdns
after modifying it.
The best current workaround I can come up with, provided you are unable to resolve the issue through configuration changes to DNS or WINS, would be to add these lines to the indicated files:
{INSTALL_DIR}\oware\lib\owappserver.properties:
uncomment the line:
##com.dorado.local.host=
and add your IP after the =, e.g. com.dorado.local.host=192.168.0.100
similarly for:
#oware.config.server=localhost
uncomment the line and replace localhost with your IP.
{INSTALL_DIR}\oware\lib\pmstartup.dat:
modify:
application.server.config.server=default
replace default with the IP of the box.
{INSTALL_DIR}\owareapps\installprops\installed.properties:
modify:
oware.database.host=localhost
again, replacing localhost with your IP.
I have verified that the application runs properly with these settings, although I could not reproduce your scenario, and consequently, can't guarantee there is no possibility of a lookup failure. I strongly recommend you try to resolve the lookup issues to elimnate any chance of this, with the hosts file approach being the simplest approach by far.
The changes to these properties are low-risk, (provided you key in the IP properly).
AFTER MAKING ANY OF THE ABOVE CHANGES , STOP THE SERVER AND ANY CLIENTS, AND DELETE THE ENTIRE {INSTALL_DIR}\oware\temp DIRECTORY.
This should be enough to get you going, good luck.