Databases
StackOverflow2013
Postsdbo
PO64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1
    primarykey
    data
    text
    <p>I am running the 64-bit install of IBM Rational Application Developer (RAD) 8.0.4 on Windows 7. I have WebSphere Application Server (WAS) v6.1 running within it. To be honest, I'm not completely sure if the WAS server is 32- or 64-bit. <strong>My problems are:</strong></p> <ol> <li><p>Except for a few useless lines of logging at WAS startup, <strong>I get no logging in the RAD console at all</strong>. Not even when there's an exception thrown-- no strack trace, nothing. I cannot find the SystemOut.log file in the place that the WebSphere Properties dialog claims that it is. However, there is one in <code>C:\Users\myUser\AppData\Local\VirtualStore\Program Files\IBM\SDP\runtimes\base_v61\profiles\was61profile1\logs\server1\SystemOut.log</code>, but I do not know how to configure RAD/Eclipse to see it.</p> <p>I <em>do</em> see an <code>Access is Denied</code> message as the first line of what I <em>can</em> see in the Console. But RAD is not clear about what or whom is being denied access, and in all other ways the server works just fine, except...</p></li> <li><p><strong>I cannot seem to get the WAS instance to run in Debug mode</strong>. If I "Restart in Debug...", RAD complies, but the server in the Servers panel of Eclipse does not show "Degugging, Synchronized"-- it simply shows "Started, Synchronized"-- just like it would if started normally. The Debug panel in Eclipse shows the server there, and claims that the debugger is listening on Port 8001. But the application will not stop on any breakpoints.</p></li> </ol> <p>My colleagues are running identical Windows 7 machines, but have the 32-bit RAD 8.0.4, and don't seem to have this problem. <strong>I'm not ready to concede and re-install RAD down to 32-bit, nor do I have the time. There's got to be some other solution.</strong></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpnuts
    1. USPattMauler
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere doesn't *have* to be another solution :-) It wouldn't surprise me if the two versions have to match. To see what version of WebSphere you have, run java -version from the AppServer/java/bin directory.
      singulars
      1. PO64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1
      1. USdbreaux
    2. CO@dbreaux I've confirmed that WAS is 32-bit.I think I've also come across a potential lead: in Windows7, if I start RAD with the Right-click > "Run as Administrator..." combo, and then start WAS... I actually get the logging output in the RAD Console. If I start RAD plain-jane, I don't get the same logging (and I get the "Access is denied" line logged as the first bit that IS logged in the Console). There must be some permissions inconsistencies somewhere in the file-system from when I installed RAD.
      singulars
      1. PO64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1
      1. USPattMauler
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload