Who's On?

	Membership:
	Latest: Alanna
	Past 24 Hours: 0
	Prev. 24 Hours: 1
	Overall: 5294

	People Online:
	Visitors: 98
	Members: 0
	Total: 98

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244

Cannot start RDB server

3 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

John Costa

Veteran Member Send Private Message

Posts: 154

5/13/2007 6:31 PM

Lawson applications version 8.1.0, MSP3
Environment version 8.0.3, ESP3
Logan remote configuration with separate application/database and web servers
SQL-Server 2003
Windows 2003 - Enterprise Edition
Java SDK 1.3.1, release 18
Tomcat 4.0.6

Rebooted my Lawson application and web servers today and am now unable see the Process Flow In-Basket within Portal. Using Lawson KB article 556239, I have verified that the WFUSER attribute for the 'lawson' user ID is properly set. I've also run "http:///servlet/Profile?" and can see the WFUSER attribute is present. However, the results of the Profile call displays numerous java exception errors under the "inbasket" attribute (see below). I've verified the inbasket.jar and remotedb.jar file versions are the same on both the application and web servers and the inbasket.class file is present in $SERVLET_DIR%. I suspect a problem with java or perhaps a port issue, but nothing has changed as far as the Lawson system configuration goes. Any suggestions?

I've attached the results of the Profile call made above. Thanks for any help you can provide.

Attachments

1513312348471.txt

John Henley

Posts: 3355

5/14/2007 12:08 AM

I'd guess it's one of two possibilties:

1) a port/firewall issue for the rdb server not being able to talk to the law app server. Look at start_rdb_server.sh and see if the port listed as 'REG_PORT' is open (you can use telnet to verify).
2) One of the pf servers is failing to start because the specified port is already in use.

John Costa

Veteran Member Send Private Message

Posts: 154

5/14/2007 12:05 PM

I was finally able to figure it out. Sometime this last week, the server environment path variable was modified as a result of a program being installed by another member of our IT team. When the program was installed, the path variable was appended, reflecting the path to the new application, which coincidentally has its own version of the java virtual machine. What this did was put the entry to the correct java directory (C:\JDK131) in the middle of the path statement. As a result, when I tried to execute "start_rdb_server.bat", the path to the correct java executable could not be determined by the operating system, hence the RDB start-up would fail and the ProcessFlow in-basket would not display in Portal. What made this so difficult to troubleshoot was that the other ProcessFlow servers started normally (Event Manager, ProcessFlow Server, WFController, and Scheduler) so I had a difficult time narrowing down the issue.

What I did was modify the PATH variable so that the Java executable directory was moved to the end of the statement as required. Once I reset the path variable, ProcessFlow started correctly.

Deleted User

New Member Send Private Message

Posts: 0

5/14/2007 6:36 PM

Thanks for the explanation. User's willingness to share the resolution makes this website great.