|
| Re: JBoss Publish error on Eclipse 3.4 [message #216331 is a reply to message #216323] |
Sat, 28 June 2008 22:21   |
 David Williams
Messages: 722
Registered: July 2009 |
Senior Member |
|
|
On Sat, 28 Jun 2008 04:43:47 -0400, Raj Saini <rajsaini@gmail.com> wrote:
>
> I have rechecked the permissions on the JBoss folder. User running the
> Eclipse have full permissions to read write the JBoss folder.
>
> Any clue what wrong is happening?
>
......
> !STACK 1
> org.eclipse.core.runtime.CoreException: Could not replace with temp file /tmp/tmp46953.MF.
> at org.eclipse.jst.server.generic.core.internal.publishers.Abst ractModuleAssembler.copyModule
> (AbstractModuleAssembler.java:162)
You mention checking permmissions on "JBoss Folder", but the folder in the message is /tmp,
and OS folder.
In somce cases, for Java, people have to change the default TMP folder (used by Java and many servers) to something of their own choice, instead of the OS default.
-Djava.io.tmpdir=/myspecialtmpfolder
I am not sure if you need this in eclipse startup, or your JBoss startup.
I have _no_ idea if this applies to JBoss but I know some VMs and some servers change the assumed default occasionally when they have a new release, so the java.io.tmpdir is a good way to "force" a consistent temp folder. (especially if you need special permissions, etc).
I doubt if releated to this ... but on some Linux-like setups, the systems /tmp folder is created on a different volumn, may be smaller than some servers need, etc.
HTH
|
|
|
|
| Re: JBoss Publish error on Eclipse 3.4 [message #216385 is a reply to message #216331] |
Mon, 30 June 2008 16:30 |
Raj Saini
Messages: 53
Registered: July 2009 |
Member |
|
|
>
> You mention checking permmissions on "JBoss Folder", but the folder in the message is /tmp,
> and OS folder.
>
> In somce cases, for Java, people have to change the default TMP folder (used by Java and many servers) to something of their own choice, instead of the OS default.
>
> -Djava.io.tmpdir=/myspecialtmpfolder
>
> I am not sure if you need this in eclipse startup, or your JBoss startup.
>
> I have _no_ idea if this applies to JBoss but I know some VMs and some servers change the assumed default occasionally when they have a new release, so the java.io.tmpdir is a good way to "force" a consistent temp folder. (especially if you need special permissions, etc).
>
> I doubt if releated to this ... but on some Linux-like setups, the systems /tmp folder is created on a different volumn, may be smaller than some servers need, etc.
Thanks for your quick reply. However, I do not think this is the
problem. /tmp directly is writable by he user running Eclipse and JBoss
and many .MF files are created. Moreover 3.3 works perfectly fine with
the same JBoss version, and all others settings unchanged.
To me it clearly looks a bug in publishing logic. I have observed that
Eclipse tries to create the exploded web application structure in the
WTP deploy folder (Its location is in
${workspace.location}/.metadata/.plugins/org.eclipse.wst.ser ver.core/tmp0.
Folders are created successfully but it fails to copy the files to the
exploded directory structure.
If someone confirms this I will create a bug.
Thanks,
Raj
>
> HTH
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02472 seconds
Search
Help
Register
Login
Home
