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 70391 - DeploymentException when deploying EJB in glassfish from NB EE5 - Localized WindowsI18N -
Summary: DeploymentException when deploying EJB in glassfish from NB EE5 - Localized W...
Status: VERIFIED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2005-12-14 12:18 UTC by mperezma
Modified: 2006-07-13 09:49 UTC (History)
4 users (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 mperezma 2005-12-14 12:18:50 UTC
When I try to deploy a simple stateless session EJB to Glassfish 9.0-B30 using 
NB EE5 (200512122300) in my spanish Windows 2000 I get:

----8<----8<----8<----8<----8<----8<----8<----
com.sun.enterprise.admin.common.exception.DeploymentException: Cannot determine 
the Java EE module type for C:\Documents and Settings\Administrador\Configuraci?
n local\Temp\s1astempdomain1server306308522\EJBModule1.jar
	at 
com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile
(DeploymentServiceUtils.java:880)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy
(PEDeploymentService.java:662)
	at com.sun.enterprise.management.deploy.DeployThread.deploy
(DeployThread.java:163)
	at com.sun.enterprise.management.deploy.DeployThread.run
(DeployThread.java:192)
Caused by: java.io.FileNotFoundException: C:\Documents and 
Settings\Administrador\Configuraci?n local\Temp\s1astempdomain1server306308522
\EJBModule1.jar
	at 
com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistFo
rArchive(PluggableArchivistsHelper.java:64)
	at 
com.sun.enterprise.deployment.archivist.ArchivistFactory.getArchivistForArchive
(ArchivistFactory.java:91)
	at 
com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile
(DeploymentServiceUtils.java:875)
	... 3 more
----8<----8<----8<----8<----8<----8<----8<----

And I think it's similar to Mobility Pack Beta 2 problem with localized Windows 
wich I saw in 23 Nov netbeans.org news.

"Configuraci?n local" should be "Configuración local"... (can't understand how 
could somebody decide to give a name like this to a system critical folder...)

mariO
Comment 1 Lukas Hasik 2005-12-14 13:52:46 UTC
The problem is caused by multibyte characters in path to the TEMP directory. It
can happend either on some localized window that translate "Local Settings" or
when user's userdir contains multibyte characters.

We(mobility) had to re-spin Beta2 build due to this problem - see
http://www.netbeans.org/community/news/index.html#753 

Seems like serious problem to me - P2?
Comment 2 Petr Blaha 2005-12-14 14:04:13 UTC
Reporter, can you reproduce the issue in NetBeans 5.0? Thanks
Comment 3 mperezma 2005-12-14 16:26:43 UTC
Hi blaha, I've installed IDE 5 beta2 and yes, problem is in this branch too.

The only difference is that, in addition to the error shown in the Output 
window for the build.xml ant process, the IDE shows a modal dialog with the 
error "Deploying application in domain failed; Cannot determine the Java EE 
module type for C:\Documents and Settings\Administrador\Configuraci?n local..."
Comment 4 _ ludo 2005-12-14 17:39:11 UTC
What is the target in this last case? AS 8.2 or AS 9.0 GlassFish?

Thanks for clarification
Comment 5 _ ludo 2005-12-14 17:39:48 UTC
What is the target in this last case? AS 8.2 or AS 9.0 GlassFish?

Thanks for clarification
Comment 6 _ ludo 2005-12-14 17:42:03 UTC
In any case, this would be a backend bug, not a netbeans bug...
When we have a P2 bug number for AS product, we can close this bug on nb side.
But we need to know if this happens also on AS 8.2 
Comment 7 mperezma 2005-12-14 19:15:43 UTC
Hi ludo, I've installed sjsas_pe-8_1_02_2005Q2 and in this case deploy works 
fine from NB5 beta2. Surelly it will work with NBEE too (not tested).

May be I will get the error on NB4.1 using glassfish?

Sorry, don't have AS8.2 here now, nor NB4.1. I'm going to download them and 
will make the tests to give more information on wich cases you get the error.

PS: changing user TEMP environment variable in windows to point to a non-
multibyte folder name like c:\temp it works..
Comment 8 mperezma 2005-12-15 10:31:22 UTC
- NB5 beta 2 + GlassFish = TEMP path error when deploying EJB.

- NB5 beta 2 + AS8.1 = EJB deployment ok.

- NB5 EE + GlassFish = TEMP path error when deploying EJB.

- NB5 EE + AS8.1 = I got a new issue: If you register only this server in NB5 
EE, you 

will get an empty combo box for J2EE version in the New EJB Module wizard, and 
it will 

not complete (null pointer ex). If you register both AS8.1 and GlassFish, 
sometimes 

you will be able to choose "Java EE 5.0" in the combo box, and other times it 
will be 

empty, but I have never seen "J2EE 1.4" in this combo. You can complete the 
wizard 

selecting Java EE 5.0 version on any server, and after it, go to properties in 
the 

project and set AS8.1 with J2EE 1.4 there, but deploy fails due to a error in 
the 

descriptor (can't find the EJB)

- NB4.1 + GlassFish = NB4.1 doesn't recognize glassfish as app server. I saw 
one trick 

some time ago to get NB4.1 working with glassfish. If you say wich files have 
to be 

replaced I will make the test.

- NB4.1 + AS8.1 = It still working fine :))

NOTE that the TEMP path error on localized Windows DOES NOT fail with a web app 

deployment! I completed Pavel Buzek's persistence demo successfully with NB5 EE 
+ 

GlassFish. I encountered the trouble when working with EJB module..

PS: Can't find AS8.2 anywere. May be you refer AS8.1 UR2 wich is what I've 
using here.
Comment 9 Vince Kraemer 2005-12-19 23:31:35 UTC
this may be related to this AS bug: 6333828

I have asked for a bit more clarification
Comment 10 Vince Kraemer 2005-12-20 04:53:50 UTC
I just tried this with nb 5.0 [from the release branch] and AS 8.2 on Mac {I think}.

i was not able to duplicate the issue.

I was able to get the deployment to go through for a simple ear w/web app test.
Comment 11 mperezma 2005-12-20 09:35:28 UTC
Please note that the TEMP path error on localized Windows DOES NOT fail with a 
web app deployment! I completed Pavel Buzek's persistence demo successfully 
with NB5 EE + GlassFish. I encountered the trouble when working with EJB 
module..

I'm using a localized version of Windows 2000, a spanish one.
Comment 12 Petr Blaha 2006-01-16 17:06:18 UTC
move from temp component
Comment 13 mperezma 2006-02-03 10:35:04 UTC
Verified: issue persist in NB5 (final) with AS8.2.
Workaround: Set TMP environment variable in the system to point to a no 
multibyte char path, i.e. c:\temp. Restart NB and deploy.
Comment 14 Vince Kraemer 2006-04-25 22:31:20 UTC
opened https://glassfish.dev.java.net/issues/show_bug.cgi?id=601
Comment 15 tjquinn 2006-04-26 21:01:46 UTC
Can the original poster (or anyone, really) attach an ear that is known to
illustrate this problem?  

I want to be sure I am using an app that is known to cause the error as I try to
duplicate the problem on my system.

Thanks.

- Tim
Comment 16 tjquinn 2006-04-26 23:12:39 UTC
Also, can you post what locale and/or character set config you have on your system?
Comment 17 tjquinn 2006-04-27 03:16:40 UTC
I think I have identified the source of the problem.  Please see the GlassFish
issue Vince created at

https://glassfish.dev.java.net/issues/show_bug.cgi?id=601

for the latest info.
Comment 18 Vince Kraemer 2006-04-29 00:42:13 UTC
About all we can do is fail with a better message....

That may lower the priority.  It looks like 9.0 UR 1 will be the release that
takes care of this server bug with a fix in the server code.
Comment 19 Petr Blaha 2006-07-11 20:41:13 UTC
It seems the issue is already fixed in the latest build of Glassfish UR1.
mprezma can you verify this?
 Thanks,
Petr
Comment 20 mperezma 2006-07-12 09:18:17 UTC
At least in GF v2 b08 it has been solved. With the default system temp now you
will get this in the server log:

[#|2006-07-12T10:01:25.359+0200|INFO|sun-appserver-pe9.1|javax.enterprise.system.tools.admin|_ThreadID=12;_ThreadName=httpWorkerThread-4848-3;C:\Documents
and Settings\mperez\Configuración
local\Temp\s1astempdomain1server306308522\AppReloaded.ear;|ADM1006:Uploading the
file to:[C:\Documents and Settings\mperez\Configuración
local\Temp\s1astempdomain1server306308522\AppReloaded.ear]|#]

And the thing works :))
Thanks
Mario
Comment 21 Petr Blaha 2006-07-12 09:34:43 UTC
Thanks for verification. I'm closing this issue.
Comment 22 Petr Blaha 2006-07-12 09:35:14 UTC
It's working with the latest GF build.
Comment 23 Pavel Rehak 2006-07-12 09:47:50 UTC
works for me with latest gf 9 + nb5.5
Comment 24 Vince Kraemer 2006-07-12 16:25:38 UTC
Please try to check it against a GF v1 update 1 build...  That is probably going
to be the build that ships with nb 5.5...
Comment 25 mperezma 2006-07-13 09:49:03 UTC
Checked against last build of v1 ur1 (currently b03), and it works.

Mario