[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 01:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 >Status: Pending Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) >Assigned to: Scott M Stark (starksm) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- Comment By: John Doe (jdoe7890) Date: 2003-02-04 07:03 Message: Logged In: YES user_id=704326 I am getting the same deployment problem on JBoss3.2 RC1. Can you send me the jboss-system.jar with the fix. Thanks for the help. -- Comment By: Moi (vincent_aumont) Date: 2003-01-28 10:45 Message: Logged In: YES user_id=627791 I had the same problem with 2.2.0RC, tried 3.2.0RC2 and it's fixed. -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 03:12 Message: Logged In: YES user_id=28931 It works with the new jboss-system.jar you sent. Which means that currently the JBoss3.2RC1 dist is broken with regard to redeployment of exploded EAR files. It'd probably be a good idea to do a RC2 fairly soon. Thanks for your help! -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 02:50 Message: Logged In: YES user_id=28931 Please send it!!! [EMAIL PROTECTED] Thanks! -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 02:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 02:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 02:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 04:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- Comment By: John Doe (jdoe7890) Date: 2003-02-04 10:03 Message: Logged In: YES user_id=704326 I am getting the same deployment problem on JBoss3.2 RC1. Can you send me the jboss-system.jar with the fix. Thanks for the help. -- Comment By: Moi (vincent_aumont) Date: 2003-01-28 13:45 Message: Logged In: YES user_id=627791 I had the same problem with 2.2.0RC, tried 3.2.0RC2 and it's fixed. -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 06:12 Message: Logged In: YES user_id=28931 It works with the new jboss-system.jar you sent. Which means that currently the JBoss3.2RC1 dist is broken with regard to redeployment of exploded EAR files. It'd probably be a good idea to do a RC2 fairly soon. Thanks for your help! -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 05:50 Message: Logged In: YES user_id=28931 Please send it!!! [EMAIL PROTECTED] Thanks! -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 05:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 05:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 05:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 01:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- Comment By: Moi (vincent_aumont) Date: 2003-01-28 10:45 Message: Logged In: YES user_id=627791 I had the same problem with 2.2.0RC, tried 3.2.0RC2 and it's fixed. -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 03:12 Message: Logged In: YES user_id=28931 It works with the new jboss-system.jar you sent. Which means that currently the JBoss3.2RC1 dist is broken with regard to redeployment of exploded EAR files. It'd probably be a good idea to do a RC2 fairly soon. Thanks for your help! -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 02:50 Message: Logged In: YES user_id=28931 Please send it!!! [EMAIL PROTECTED] Thanks! -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 02:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 02:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 02:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 10:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- >Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 12:12 Message: Logged In: YES user_id=28931 It works with the new jboss-system.jar you sent. Which means that currently the JBoss3.2RC1 dist is broken with regard to redeployment of exploded EAR files. It'd probably be a good idea to do a RC2 fairly soon. Thanks for your help! -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 11:50 Message: Logged In: YES user_id=28931 Please send it!!! [EMAIL PROTECTED] Thanks! -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 11:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 11:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 11:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 10:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- >Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 11:50 Message: Logged In: YES user_id=28931 Please send it!!! [EMAIL PROTECTED] Thanks! -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 11:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 11:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 11:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- >Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 12:49 Message: Logged In: YES user_id=543482 yes, I tried it on W2K. BTW, AFAIK, the protocol handlers are read from right to left (from the property), no? Ultimately, I can try to send you jboss-system.jar that should fix it :) alex -- Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 12:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 12:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 10:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- >Comment By: Rickard Öberg (rickardoberg) Date: 2003-01-28 11:42 Message: Logged In: YES user_id=28931 First of all, this is on W2K. Are you running on Linux? Anyway, I added the setting to properties-service.xml. Printing the property in a servlet indicates that it is set properly (JBoss is before Sun's stuff). -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 11:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 11:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- >Comment By: Alexey Loubyansky (loubyansky) Date: 2003-01-28 12:40 Message: Logged In: YES user_id=543482 I still think this is that bug with default protocol handlers. How did you make sure the JBoss' protocol handler is used for application.xml? Note, if the deploy directory gets in the classpath earlier than the custom URLStreamHandlerFactory is setup then, AFAIK, specifying java.protocol.handler.pkgs won't help. I coudn't reproduce it with jboss-3.2.0RC2. alex -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675984 ] Deploument descriptors are locked -> no redeploy possible
Bugs item #675984, was opened at 2003-01-28 10:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rickard Öberg (rickardoberg) Assigned to: Nobody/Anonymous (nobody) Summary: Deploument descriptors are locked -> no redeploy possible Initial Comment: I'm using 3.2RC1 /w Tomcat. I have an exploded EAR file. After deployment the application.xml file is somehow locked, which makes it impossible to "touch" it from Ant so that the timestamp is updated in order to get a redeploy. The consequence is that redeployment is impossible. I have made sure that the JBoss protocol handlers are being used, but that doesn't help. I have verified that it is indeed JBoss that is locking the file, because as soon as I quite JBoss I can run the Ant target and the timestamp of application.xml is updated. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=675984&group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
