This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 249682 - Glassfish remote server classpath fails when setup using network path
Summary: Glassfish remote server classpath fails when setup using network path
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 8.0.2
Hardware: PC Windows Vista
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-07 22:20 UTC by steeler906
Modified: 2015-04-16 10:36 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description steeler906 2015-01-07 22:20:39 UTC
Product Version = NetBeans IDE 8.0.2 (Build 201411181905)
Operating System = Windows Vista version 6.0 running on amd64
Java; VM; Vendor = 1.8.0_25
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.25-b02

When upgrading from 7.2to 8.0.2 recently my projects using the remote glassfish servers failed to compile. The errors indicated that the classpath was missing for the JEE items. Sure enough, the libraries folder in the project showed there were no jar files under the glassfish server. 

The server was configured for network path (example: \\glassfish\glassfish3\...) and would not pull the correct files for the classpath as 7.2 did. After much troubleshooting, I was able to get it to work if I setup the glassfish server using a mapped drive rather than the relative path. Then the necessary jar files would show. 

I attached the IDE log with many errors showing attempts at setting up the servers in local and remote mode and always getting the same problem untl the mapped drive.
Comment 1 TomasKraus 2015-03-11 10:03:21 UTC
This looks like wrong server configuration.
There was Glassfish 3 on Netbeans 7.x and upgrading to 8.0 will also upgrade your glassfish to version 4.
Remember that when GF plugin is configured for remote server, this still needs local copy of Glassfosh for builds. So make sure that registered remote glassfish and path to local one contains identical GF versions. Install the same GF locally and delete and register GF server in Netbeans again.

I would also never point local directory over network because it's less reliable (depends on network and remote machine) and it may slow down builds significantly.
Comment 2 TomasKraus 2015-03-17 14:42:06 UTC
Unfortunately I do not use Windows for almost 20 years. :)
Anyway, problem may be somewhere in GF Tooling Library which takes care of resolving GlassFish library depending on pre-configured .jar search masks.
This is org.netbeans.modules.glassfish.tooling.server.config.ConfigBuilder#getLibraries
It's cached so resolving code may be executed just once.
Individual files processing and matching against pre-configured regex patterns is done in
org.netbeans.modules.glassfish.tooling.server.config.ConfigUtils#processFileset

There may be some issue with Windows network paths. I was never testing it. Paths with drive (e.g. F:\bla\bla\bla) shall work fine.
Comment 3 Petr Hejl 2015-04-16 10:36:36 UTC
Can you explain in detail how you actually used a server from network location (\\something)? I've tested different versions of GF and NetBeans, but the GF won't start in such setup.