[JBoss JIRA] Created: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
7:44 a.m.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does not
work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter updated JBIDE-4156:
-----------------------------------------
Attachment: testapp.zip
I've attached a simple seam test-app which I've created to test the full-publish
feature. I've removed all seam-specific jar files.
BTW: This works perfectly in JBoss Tools 3.0 Alpha Version!
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker reassigned JBIDE-4156:
----------------------------------
Assignee: Rob Stryker
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
As was mentioned in the thread, I've executed the following and am unable to reproduce
an untouched application.xml.
[rob@localhost deploy]$ du -a | grep "application.xml"
8 ./testapp-ear.ear/META-INF/application.xml
[rob@localhost deploy]$ du -a | grep "application.xml"
[rob@localhost deploy]$ pwd
/home/rob/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy
[rob@localhost deploy]$ ls -l testapp-ear.ear/META-INF/application.xml
-rw-rw-r-- 1 rob rob 545 2009-04-13 15:23 testapp-ear.ear/META-INF/application.xml
# wait a bit
[rob@localhost deploy]$ ls -l testapp-ear.ear/META-INF/application.xml
-rw-rw-r-- 1 rob rob 545 2009-04-13 15:24 testapp-ear.ear/META-INF/application.xml
Note the timestamp changes from 15:23 to 15:24.
Is there anything in your error view or your server log?
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
I did notice some errors if the project is out of sync with the workspace.
Try Refreshing your projects to see if that fixes anything. Eclipse won't give a good
file handle to resources that are out of sync with the workspace.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Ok, just retested everything - the workspace is in sync with the filesystem, everything is
refreshed (tested with manual and automatic refresh).
Due to the auto-publish feature, everytime (!) I save a java- or xhtml-file the console
shows the following entries:
09:08:23,561 INFO [PersistenceUnitDeployment] Stopping persistence unit
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,561 INFO [SessionFactoryImpl] closing
09:08:23,561 INFO [SessionFactoryObjectFactory] Unbinding factory from JNDI name:
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,561 INFO [NamingHelper] JNDI InitialContext
properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory,
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
09:08:23,561 INFO [SessionFactoryObjectFactory] Unbound factory from JNDI name:
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,562 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=testappDatasource' from JNDI name
'java:testappDatasource'
09:08:23,624 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=testappDatasource' to JNDI name
'java:testappDatasource'
09:08:23,624 INFO [PersistenceUnitDeployment] Starting persistence unit
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,640 INFO [Configuration] Reading mappings from resource : META-INF/orm.xml
09:08:23,640 INFO [Ejb3Configuration] [PersistenceUnit: testapp] no META-INF/orm.xml
found
09:08:23,640 INFO [ConnectionProviderFactory] Initializing connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
09:08:23,640 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
09:08:23,687 INFO [SettingsFactory] RDBMS: MySQL, version: 5.1.22-rc-community
09:08:23,687 INFO [SettingsFactory] JDBC driver: MySQL-AB JDBC Driver, version:
mysql-connector-java-5.1.6 ( Revision: ${svn.Revision} )
09:08:23,687 INFO [Dialect] Using dialect: org.hibernate.dialect.MySQL5InnoDBDialect
09:08:23,687 INFO [TransactionFactoryFactory] Transaction strategy:
org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
09:08:23,687 INFO [TransactionManagerLookupFactory] instantiating
TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
09:08:23,687 INFO [TransactionManagerLookupFactory] instantiated
TransactionManagerLookup
09:08:23,687 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled
09:08:23,687 INFO [SettingsFactory] Automatic session close at end of transaction:
disabled
09:08:23,687 INFO [SettingsFactory] JDBC batch size: 15
09:08:23,687 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
09:08:23,687 INFO [SettingsFactory] Scrollable result sets: enabled
09:08:23,687 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): enabled
09:08:23,687 INFO [SettingsFactory] Connection release mode: auto
09:08:23,687 INFO [SettingsFactory] Default schema: test
09:08:23,687 INFO [SettingsFactory] Maximum outer join fetch depth: 2
09:08:23,687 INFO [SettingsFactory] Default batch fetch size: 1
09:08:23,687 INFO [SettingsFactory] Generate SQL with comments: disabled
09:08:23,687 INFO [SettingsFactory] Order SQL updates by primary key: disabled
09:08:23,687 INFO [SettingsFactory] Order SQL inserts for batching: disabled
09:08:23,687 INFO [SettingsFactory] Query translator:
org.hibernate.hql.ast.ASTQueryTranslatorFactory
09:08:23,687 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
09:08:23,687 INFO [SettingsFactory] Query language substitutions: {}
09:08:23,687 INFO [SettingsFactory] JPA-QL strict compliance: enabled
09:08:23,687 INFO [SettingsFactory] Second-level cache: enabled
09:08:23,687 INFO [SettingsFactory] Query cache: disabled
09:08:23,687 INFO [SettingsFactory] Cache provider:
org.hibernate.cache.HashtableCacheProvider
09:08:23,687 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
09:08:23,687 INFO [SettingsFactory] Cache region prefix: testapp-ear_ear,testapp
09:08:23,687 INFO [SettingsFactory] Structured second-level cache entries: disabled
09:08:23,687 INFO [SettingsFactory] Echoing all SQL to stdout
09:08:23,687 INFO [SettingsFactory] Statistics: disabled
09:08:23,687 INFO [SettingsFactory] Deleted entity synthetic identifier rollback:
disabled
09:08:23,687 INFO [SettingsFactory] Default entity-mode: pojo
09:08:23,687 INFO [SettingsFactory] Named query checking : enabled
09:08:23,687 INFO [SessionFactoryImpl] building session factory
09:08:23,687 INFO [SessionFactoryObjectFactory] Factory name:
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,687 INFO [NamingHelper] JNDI InitialContext
properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory,
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
09:08:23,687 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.units:ear=testapp-ear.ear,unitName=testapp
09:08:23,687 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
09:08:23,687 INFO [SchemaUpdate] Running hbm2ddl schema update
09:08:23,687 INFO [SchemaUpdate] fetching database metadata
09:08:23,687 INFO [SchemaUpdate] updating schema
09:08:23,702 INFO [SchemaUpdate] schema update complete
09:08:23,702 INFO [NamingHelper] JNDI InitialContext
properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory,
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
I did notice a working full-publishing sometimes, however, the application.xml is never
touched - this must be because of another descriptor or something...
I'll test this on another vista-machine today and see if the problem is somehow
related to my vista-setup (however, I can't imagine what it could be...)
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Ok, I've just tested this on another machine running Vista with the same result.
The appliaction.xml is never touched and even a simple filesafe of an xhtml-file causes
the persistence-unit to restart (with the same console printout above).
So maybe I'm doing something wrong (the same thing worked with JBoss Tools 3 alpha) or
this is a vista- or configuration-issue.
So again, here's the configuration I've tested:
- Windows Vista Business
- Eclipse 3.4.2 (eclipse-jee-ganymede-SR2-win32)
- JBoss Tools 3.0.0.GA (JBossTools-ALL-win32-3.0.0.GA-R200903141626-H5)
- JBoss AS 4.2.2/4.2.3 (tested on both)
- Java 1.5.0_15/1.5.0_17
- Seam 2.1.0/Seam 2.1.1 (tested both)
Is this configuration ok to run JBoss Tools on or did I miss something?
Maybe the problem is WTP-related or comes from another plugin - should I maybe use another
Eclipse version instead?
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
If you right-click on your server and select show in -> server log, you should see more
fine-grained deployment information.
The only reason the persistence unit would be republishing all the time is if someone or
something is touching it. The tools deployment checks timestamps to see if it should copy
a file over. Even if auto-publish is called every single second, if there's been no
change to the file, it should not be being touched (and thus not being republished). In
the server's view, what does it say next to the persistence unit module?
"synchronized" ? or "resync"
Unfortunately I don't have a windows vista machine to test this on. A full publish
deletes the entire deployment (yes physically deletes it) and then recopies each file
over. IMO it'd be very hard to see how the timestamp WOULDNT change unless the file
was never deleted.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Ok, now we have more information. Forgive me, but I've never used the Server Log View
before.
To answer your first question, the "testapp-ear" module switches to
"Synchronized" after a full-publish, but the "testapp-ds.xml" remains
in "Republish" state (see below).
The publishing of a single xhtml-file shows 2 log-entries:
- The module cannot be published
- 1 files modified in module testapp
The auto-publish seems to recognize the "testapp-ds.xml" as changed an copies it
over to the "jbosstoolsTemp" directory. However, it remains there and cannot be
copied over to the deploy directory (which probably causes this module to stay in
"Republish" state - ?).
The server-log shows the following stack-trace:
java.lang.Exception: Move from
C:\jboss\jboss-4.2.2.GA\server\default\tmp\jbosstoolsTemp\testapp-ds.xml to
C:\jboss\jboss-4.2.2.GA\server\default\deploy\testapp-ds.xml failed.
at
org.jboss.ide.eclipse.as.core.publishers.SingleFilePublisher.publish(SingleFilePublisher.java:79)
at
org.jboss.ide.eclipse.as.core.publishers.SingleFilePublisher.publishModule(SingleFilePublisher.java:56)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:86)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:947)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1037)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:871)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:707)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2492)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:270)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
This happens everytime (!) I safe a file in eclipse, which explains the rebuilding of the
persistence-unit I guess.
The same error appears when using the .metadata-deploy directory...
The full-publishing shows 6 log-entries:
- The module cannot be published (same error and stacktrace as above)
- Full Publish Failed for module testapp-ear (no stacktrace)
- 8 files modified in module testapp-ejb
- Full Publish Failed for module testapp (no stacktrace)
- 1 files modified in module lib/testapp-ear/EarContent/jboss-seam.jar
- 1 files modified in module lib/testapp-ear/EarContent/mvel14.jar
So the log-entries show the failure of the full-publishing. Unfortunately I don't get
any stack-trace or detailed error information. Is there any other place to look for
detailed error-information?
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Just a suspicion:
I see the SingleFilePublisher does:
boolean success = tempDestFile.renameTo(destFile);
As I remembered, there is an issue with renameTo under windows, see:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4017593
(this was reported against 1.1, but still seems to be an issue)
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:43 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
I've added a delete call to the SingleFilePublisher, which should hopefully fix the
constant redeployment of the xml file.
As for the JST publisher i'll be looking into what's going on but again, I lack a
windows box to do this with. In case you're curious, the JSTPublisher also uses a file
PublishCopyUtil, which was originally a WTP class that was "liberated". If you
look at this class you'll see it's pretty much crafted to try to get around the
sun bug, constantly attempting to delete the file before doing the renameTo.
I can also try to look where I can improve the error reporting for JSTPublisher.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
SingleFilePublisher was updating the timestamp (touching) the file no matter whether the
success worked or not. This obviously was bad. fixed it.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4156:
---------------------------------------
Fix Version/s: 3.0.1.GA
Ouch - that should be fixed in 3.0.1.GA
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.0.1.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-4156:
-------------------------------
Fix Version/s: 3.1.0.M1
(was: 3.0.1.GA)
did not make it into 3.0.1
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4156:
---------------------------------------
Fix Version/s: 3.0.1.GA
eh what ? Isn't this a rather critical issue we already have a patch for and
codefreeze of 3.0.1.GA isn't until wednesday ?
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.0.1.GA, 3.1.0.M1
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4156:
---------------------------------------
Fix Version/s: 3.0.2.GA
(was: 3.0.1.GA)
Moving to 3.0.2
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
No we do not have a patch for the core part of this issue. We had a patch for the
redeployment of the single-file deployment but we did not have a patch at all for the full
publish not working.
In fact I am completely unable to replicate it and have pored over the code dozens of
times looking for anywhere that could be preventing or hiding some overwriting failures.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Have you tested this on any Windows OS, as the problem should occur on XP too? I don't
think this is a Vista-related problem, as the file-handling should be the same in my
opinion...
When I have some free time I'll dig into the code and try to debug to see what's
going on...
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:05 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Just retested everything with the newest nightly builts
(JBossTools-ALL-win32-3.0.1.Alpha1-N200904280907-H52.zip)...
A few things I want to share:
- The single-file publish seems to work now. If I modify an xhtml-file for example, I see
the file gets deleted and replaced by the modified...
But: I downloaded the sources as well and don't see any difference in
SingleFilePublisher...Does the publishing of those files happen somewhere else or are the
sources not equivalent to the built jboss-version?
Anyway, the persistence descriptor is not touched and therefore the persistence-unit does
not restart...(so this seems to work now)
- The full-publishing still does not work, but the server log shows some more entries:
Error
Mon May 04 09:35:45 CEST 2009
Attempt to delete
C:\jboss\jboss-4.2.2.GA\server\default\deploy\testapp-ear.ear\testapp.war failed
Error
Mon May 04 09:35:45 CEST 2009
Attempt to delete
C:\jboss\jboss-4.2.2.GA\server\default\deploy\testapp-ear.ear\testapp.war\WEB-INF failed
...and so on...
Only the jar-files in /WEB-INF/lib/* cannot be deleted
So why this happens seems clear... The JBoss AS is still running and the files cannot be
deleted as there are still some file-handles opened.
So I think those files should not be removed (or at least should not stop the
full-publishing to complete)...
Hope this helps a bit
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4156:
------------------------------------
Bernard:
You can see the singleFilePublisher diff over at:
http://fisheye.jboss.org/browse/JBossTools/trunk/as/plugins/org.jboss.ide...
There I made just a slight change to make sure the file isn't touched if the rename
failed.
I'll look into what I can do for JSTPublisher. Thanks for all your help.
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:54 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4156.
--------------------------------
Fix Version/s: (was: 3.0.2.GA)
Resolution: Done
I think I've figured it out. Not sure about windows, but for linux, this is the case,
and it makes sense if it applies to windows.
The application.xml file *is* coppied over new, but it's timestamp is not adjusted.
Here in linux that means the new file copy keeps the timestamp of the old file (?) which I
find a bit shocking but whatever.
Looking in my code, I copy all the files I can, logging errors, but do not stop copying
files even if there are errors. So it's not that a copy or delete error is blowing
everythign up... not directly.
Instead, it seems I'm returning without touching timestamps. I'll make a quick
patch and commit this to trunk.
Since I'm fairly confident this was the problem, I'm gonna resolve this issue and
let QA give it a whirl.
Let me know. =] (since I'm in China I'm not sure when the nightly builds run
exactly... so... you may have to wait a day or two)
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-4156:
-------------------------------
Fix Version/s: 3.0.2.GA
committed to branch also
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Ok, I'll check the NBs tomorrow and see if that did the trick...
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4156) Full publishing of a seam project does not restart the appliaction
[
https://jira.jboss.org/jira/browse/JBIDE-4156?page=com.atlassian.jira.plu...
]
Bernhard Hablesreiter commented on JBIDE-4156:
----------------------------------------------
Just retested with the latest NB and it seems to work now!
The application.xml is correctly touched after a full-publish and the single-file publish
also seems to work fine!
So I think that all related bugs have been fixed!
Thanks again!
Full publishing of a seam project does not restart the appliaction
------------------------------------------------------------------
Key: JBIDE-4156
URL: https://jira.jboss.org/jira/browse/JBIDE-4156
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA
Environment: JBoss 4.2.2, JDK1.5.0_15, Windows Vista, Eclipse 3.4.2 (lastes
Version, downloaded 2009-04-09), Seam 2.1.1
Reporter: Bernhard Hablesreiter
Assignee: Rob Stryker
Fix For: 3.1.0.M1, 3.0.2.GA
Attachments: testapp.zip
As described in the JBoss forums, the full-publish feature of JBoss Tools 3.0.0GA does
not work as expected.
A "full publish" only deploys the relevant files but does not restart the
application - i.e. it does not touch the application.xml file, which should trigger the
restart of the appiaction.
The console-output only shows that the persistence unit is reloaded, but the appliaction
does not restart.
The same reloading of the persistence unit happens when saving a simple Facelets-file -
which seems also weird.
I've installed a fresh eclipseEE 3.4.2, the JBoss Tools 3.3.0GA and a JBoss AS 4.2.2
and created a new workspace with a new seam project, so the setup should be correct. The
same problem appears when running on JBoss AS 4.2.3.
One of my colleagues is running a similar configuration on Ubuntu 8.10 without any
problems so this might be an OS-specific problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6193
days inactive
6222
days old
jbosstools-issues@lists.jboss.org
23 comments
3 participants
participants (3)
-
Bernhard Hablesreiter (JIRA) -
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)