[biker_ron]

– System Setup ——————————-
Operating System and version: Windows XP Home
Eclipse version: 3.0.2
Eclipse build id: 200503110845
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8.4+QF2
Eclipse JDK version: 1.4.2
Application Server JDK version: 1.4
Are there any exceptions in the Eclipse log file? ??

If this is a DB related question please answer the following:

RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:

– Message Body ——————————-

I’ve tried to set up the MyEclipse connector to Sun App Server 8.0 with no luck.

Settings are:

enabled
home dir: c:\j2ee14
config dir: c:\j2ee14\config
server name: server
domain: domain1
domain dir: C:\j2ee14\domains\domain1

Have set up JDK to point to the directory c:\j2ee14\jdk

Here is what I get when I try to start it:

Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) …
[#|2005-08-17T12:47:55.812-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]

[#|2005-08-17T12:47:57.203-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]

[#|2005-08-17T12:47:57.468-0700|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]

ALSO It asks me to confirm perspective switch to debug and the debug screen stack shows:

Thread [main] (Suspended (exception NullPointerException))
InputStreamReader(Reader).<init>(Object) line: 61
InputStreamReader.<init>(InputStream, String) line: 80
Properties.load(InputStream) line: 266
BasicQueue(AdministeredObject).<init>(String) line: 166
BasicQueue(Destination).<init>(String) line: 46
BasicQueue.<init>(String) line: 38
QueueSessionImpl(UnifiedSessionImpl).createQueue(String) line: 65
JMSAdminImpl.connectToProvider() line: 418
JmsProviderLifecycle.attachToJmsProvider() line: 283
JmsProviderLifecycle.onInitialization(ServerContext) line: 224
ApplicationServer.onInitialization(ServerContext) line: 220
PEMain.run(String) line: 210
PEMain.main(String[]) line: 172

Furthermore I tried setting the Sun App Server 8.0 up as externally launched and while I can get it to work there seem to be some issues such as when selecting the deployment location I pick the …\domain1\autodeploy directory and it leaves out the \ path separator between the autodeploy directory name and the web archive file. It also doesn’t put any extension on the deployed file if you select the package archive option.

And one last complaint while I could work around this by renaming the deployed archive with .war and things work I also tried to deploy as exploded archive so I can use the debug capabilities and the Sun App server may not support this or I don’t have an option set correctly in the app server config. It doesn’t autodeploy the exploded archive.

Any and all help/suggestion appreciated..

thx,

Ron

[Riyad Kalla]

Ron,
I believe all of this things were fixed in our most recent 4.0 Milestone 3 release for Eclipse 3.1. You will need to perform a fresh install of Eclipse 3.1 and MyEclipse 4.0 Milestone 3 however.

Your preferences and projects can be reimported into the new workspace and shouldn’t cause you any issues. I HIGHLY recommend you don’t use the same workspace.

[biker_ron]

Upgrading to eclipse 3.1 and MyEclipse 4 fixed everything (almost). It seems the Sun App Server 8.0 doesn’t support exploded archive files though as I can only get it to work when I deploy as a packaged archive (at least to autodeploy). Guess I just have to redeploy each time.

Thanks,

Ron

[Riyad Kalla]

Try this:

1) Deploy packaged archive, let the app server deploy it so it’s running.
2) Shut down the app server
3) remove the deployment and change it to an exploded deployment, hit OK to redeploy it.
4) Start up the app server again, try and run the app. Is it still running?
5) Go make a change in a JSP and save it (make sure Project > Build automatically is on) now refresh the page, did it change?

[Author]

Posts