Pinned topic DWA 126.96.36.199 hangs on Login attempt...
Interop = DOORS 188.8.131.52
Windows Server 2003 R2 SP2
DOORS Server 184.108.40.206
All system requirements ... OK ... according to DWA 220.127.116.11 release notes documentation.
However comma,... when a login attempt is made the DWA login screen hangs at
j_acegi_security_check and then eventually bails out after the timer times out.
Has anyone else here seen this or successfully got 18.104.22.168 active?
We have submitted PMR...I don't have alot of hope that will get things resolved quickly.
Go Figure: ... we had an exuberant group of new users on a special project that REALLY wanted to use DWA, and we also needed to get DOORS v22.214.171.124 server and client running sucessfully so we could be ready for pending Windows 7 & MS Office 2010 rollouts at our company...this issue will leave a bad taste in the mouth of all affected by DWA 126.96.36.199 not working...
gsdguy...this is the 3rd Monday of this dissappointing week working on DWA...
llandale 270001QM9N252 Posts
Re: DWA 188.8.131.52 hangs on Login attempt...2011-10-26T17:36:23ZThis is the accepted answer. This is the accepted answer.Ha! Got that exact situation yesterday while the IT folks translated the dos-command-batch method of invoking DWA over to a more suitable service approach. The DWA service was running but not one of the other two (one is "interop"?). Thus, your DWA was not completely activated yet.
Re: DWA 184.108.40.206 hangs on Login attempt...2011-10-26T18:43:17ZThis is the accepted answer. This is the accepted answer.
- llandale 270001QM9N
there is also the broker and something else with apache then the 3 work together to reach into the doors server data and do the fire bucket brigade of passing doors data out to a web browser...when they are all working... ;)
as it turns out there are now a couple of other limitations with DWA that are impacting us:
1.) apparently in the festival.xml file it only allows for a single license server vs. we need to post our entire group of 5 license servers as we use them in list form on the clients to ensure we can always get a license. Our present single server with 40 has been seeing all 40 checked out and thus the DWA license doling operation chimes back "all licenses used see your doors admin" when in fact our pool still has 35 unused licenses due to the nature of random user activity at each of the 5 sites.
2. a new post on 10-24-2011 by someone else who has just managed to get 220.127.116.11 running has discovered that a module with Layout DXL either in default module view will crash the interop server, and also if module is already open and a view is selected which contains a Layout DXL column will crash the interop server too... The PMR work around for now is to eliminate Layout DXL, which kind of defeats several important views in the project...torpedo off the port bow skipper!!!!
Heather_Linsk 270001TJP88 Posts
Re: DWA 18.104.22.168 hangs on Login attempt...2011-10-27T17:38:11ZThis is the accepted answer. This is the accepted answer.
In your interop startup bat file
Change 127.0.0.1 to the hostname or IP address of the machine hosting DWA.
llandale 270001QM9N252 Posts
Re: DWA 22.214.171.124 hangs on Login attempt...2011-10-27T20:08:40ZThis is the accepted answer. This is the accepted answer.
Re: DWA 126.96.36.199 hangs on Login attempt...2012-01-09T14:33:20ZThis is the accepted answer. This is the accepted answer.
- llandale 270001QM9N
according to APAR PM46906, the crash of interop server happens with a Layout DXL column that contains icons or pictures in the View being opened through DOORS Web Access v188.8.131.52 ONLY...
Like you, i was able to successfully open a view with layout DXL but it only contained text objects being pulled in by the layout DXL.
Re: DWA 184.108.40.206 hangs on Login attempt...2012-01-09T14:44:31ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
We solved our DWA 220.127.116.11 hangs on Login attempt...as follows.
We bumped our DOORS server up to a Windows 2008 64 bit and had the same issue.
Then we discovered the whole issue was being caused by DWA flaky licensing.
We had to install a temporary license.dat file for DWA features to figure this out.
eg. we had not purchased separate pool of DWA licenses as the documentation says that if DWA cannot find a DWA feature it defaults to a client license which our DOORS clients license pool is using.
Well...turns out that DWA is smart enough to not serve out a license to a DWA user request if the license.dat file has an expired maintenance date in the license.dat for the doors client feature...even thought our maintenance is paid up for another year for doors client pool but we had not yet downloaded and installed our NEW year 2012 license.dat file with maintenance end date of 30 Sept 2012.
This was not obvious since the DOORS client licenses we have are permanent variety with maintenance dates expired Oct.2011 but the clients are more tolerant and give us the extra time we need to update all the license.dat files without stopping client use.
DWA is not flexible to allow for this and thus we had to get a temporary license.dat file while we update our license.dat files.
Jana12787 270005FS4B1 Post
Re: DWA 18.104.22.168 hangs on Login attempt...2013-08-02T10:21:21ZThis is the accepted answer. This is the accepted answer.
Can someone share the solution for the time out problem "Login attempt is made the DWA login screen hangs at j_acegi_security_check and then eventually bails out after the timer times out." Facing a similar issue with DWA 9.5.1
Thanks in Advance