[JBoss-dev] jboss-3.2-testsuite build.79 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050225005054Lbuild.79 BUILD COMPLETE - build.79Date of build: 02/25/2005 00:50:54Time to build: 73 minutes 55 secondsLast changed: 02/24/2005 07:02:40Last log entry: moved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules Unit Tests: (1936) Total Errors and Failures: (28)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestQueueMessageOrderorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestRequestReplyQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryQueueDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryTopicDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueSendorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueBrowseorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationTopicPublishorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestErrorsTopicSubscribeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestCreateQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestMessageListenerorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestApplicationServerStufforg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicsorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalBounceorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorChangeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorNullOrEmptyorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveExpiredorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendListenOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (3)1.1.2.3modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javamoved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules1.1.2.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaJBAS-1500 session.invalidate does not gets replicated1.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1511 http session produce WARN session null message
[JBoss-dev] [Design of JBoss Admin Console] - Update Data and Minor DataSource Module Suggestions
Can you describe in brief goals for 1.0 and 1.1 alpha versions - data source and jms administration? Currently I see that there is only view functionality available, no update. When it is planned to be available - maybe this depends on the DeploymentService? What do you think about those two minor suggestions about datasources: 1) If user wants to create new datasource similar to existing one then copying/cloning DS data will be useful. Maybe sample presets for some DBs will be helpful too. 2) Connection URL - currently input text length is small (for DefaultDS on my installation) so maybe title attribute, onmouseover or some other event is needed to display the full text. This is in case there will be separate read-only and write-enabled modes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867866#3867866 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867866 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: nullpointerexception
The problem wasn't eviction policies, but xml-apis.jar. I am doing my project with hibernate , myeclipse, jboss and jbossCache. The problem was that myeclipse included J2EE jars (with his xml-apis.jar), which caused the problem. So when I removed that jar and included the same from jboss, everything was working. Hope that it will help someone :-) majecek View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867864#3867864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867864 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1522) HttpNamingContextFactory fails due to system property read when under a security manager
HttpNamingContextFactory fails due to system property read when under a security manager Key: JBAS-1522 URL: http://jira.jboss.com/jira/browse/JBAS-1522 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Scott M Stark Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final Running under a security manager with the org.jboss.naming.HttpNamingContextFactory can result in the following failure due to the property access not being in a privileged block. The failure should also be ignored since its an optional override setting. java.lang.ExceptionInInitializerError at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:106) at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:65) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) at javax.naming.InitialContext.init(InitialContext.java:219) at javax.naming.InitialContext.(InitialContext.java:195) at com.nineci.applet.HelloBeanApplet.start(HelloBeanApplet.java:31) at sun.applet.AppletPanel.run(AppletPanel.java:377) at java.lang.Thread.run(Thread.java:534) Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission org.jboss.security.httpInvoker.sslSocketFactoryBuilder read) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269) at java.security.AccessController.checkPermission(AccessController.java:401) at java.lang.SecurityManager.checkPermission(SecurityManager.java:524) at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1276) at java.lang.System.getProperty(System.java:573) at org.jboss.invocation.http.interfaces.Util.(Util.java:76) ... 9 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[
http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315789 ]
John Emerson commented on JBIDE-116:
I'm trying to debug this myself. I'm building the ide in eclipse according to
http://www.jboss.org/wiki/Wiki.jsp?page=JBossIDEBuild
However I get one compile error in
org.jboss.ide.eclipse.packaging.ui.ConfigurationViewer.java
In the following getPackagingData in DataChoiceDialog is not defined:
private void doAddStandardArchive()
{
Collection choices =
PackagingCorePlugin.getDefault().getStandardConfigurations().getConfigurations();
DataChoiceDialog dialog = new DataChoiceDialog(AbstractPlugin.getShell(),
choices);
if (dialog.open() == IDialogConstants.OK_ID)
{
PackagingData data = dialog.getPackagingData();
if (data != null)
{
PackagingArchive archive = (PackagingArchive) data.cloneData();
archive.setProject(this.project);
this.configurations.add(archive);
this.refresh();
}
}
}
What do I do?
> Conflict between JBoss-IDE plugin and Rational ClearCase SCM
>
>
> Key: JBIDE-116
> URL: http://jira.jboss.com/jira/browse/JBIDE-116
> Project: JBoss IDE
> Type: Bug
> Reporter: SourceForge User
> Assignee: Marshall Culpepper
>
>
> SourceForge Submitter: ericeberry .
> I have been getting this exception when trying to Run
> XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1.
> !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004
> 09:07:29.742
> !MESSAGE An internal error occurred during: "XDoclet
> Generation".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to
> beginRule: R/, does not match outer scope rule:
> P/bnc1.5
> at org.eclipse.core.internal.runtime.Assert.isLegal
> (Assert.java:58)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush
> (ThreadJob.java:106)
> at org.eclipse.core.internal.jobs.ThreadJob.push
> (ThreadJob.java:200)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin
> (ImplicitJobs.java:80)
> at org.eclipse.core.internal.jobs.JobManager.beginRule
> (JobManager.java:170)
> at
> org.eclipse.core.internal.resources.WorkManager.checkIn
> (WorkManager.java:95)
> at
> org.eclipse.core.internal.resources.Workspace.prepareOp
> eration(Workspace.java:1628)
> at
> org.eclipse.core.internal.resources.Resource.refreshLocal
> (Resource.java:1224)
> at
> org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct
> ion$1.run(XDocletRunAction.java:191)
> at org.eclipse.core.internal.jobs.Worker.run
> (Worker.java:66)
> It turns out there is a conflict between the JBoss-IDE
> plugin and the Rational ClearCase SCM Adapter 6.0.24
> plugin. Becuase this plugin is "always on", we can't turn
> the plugin off. We have to disable the plugin to turn it
> off. I disabled the plugin and I was able to run xdoclet
> every time. As soon as I re-enabled the plugin. Run
> XDoclet stopped working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-212) portlet resource bundle was not loaded correctly
portlet resource bundle was not loaded correctly Key: JBPORTAL-212 URL: http://jira.jboss.com/jira/browse/JBPORTAL-212 Project: JBoss Portal Type: Bug Components: Portal Core Versions: 2.0 Beta 1, 2.0 Beta 2, 2.0 Final Reporter: Julien Viet Assigned to: Julien Viet Fix For: 2.0 Beta 1, 2.0 Beta 2, 2.0 Final the loading of resource bundle was not executed correctly and bundle not at the root were not loaded at all -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-212) portlet resource bundle was not loaded correctly
[ http://jira.jboss.com/jira/browse/JBPORTAL-212?page=history ] Julien Viet resolved JBPORTAL-212: -- Resolution: Done > portlet resource bundle was not loaded correctly > > > Key: JBPORTAL-212 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-212 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 Beta 1, 2.0 Beta 2, 2.0 Final > Reporter: Julien Viet > Assignee: Julien Viet > Fix For: 2.0 Beta 1, 2.0 Beta 2, 2.0 Final > > Original Estimate: 5 hours > Remaining: 5 hours > > the loading of resource bundle was not executed correctly and bundle not at > the root were not loaded at all -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1520) patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData
[ http://jira.jboss.com/jira/browse/JBAS-1520?page=history ] Marcin Mieszek updated JBAS-1520: - Description: This is the first time I submit anything here.. so please be patient to me :) Module jboss-head failed to compile as in 1.7.6.1 version of org.jboss.metadata.ClusterConfigMetaData constant: public final static String DEFAULT_PARTITION = "DefaultPartition"; was replaced with default partition logic in org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: public static String getDefaultPartitionName() However, there are still references to DEFAULT_PARTITION in files: 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at line 54: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: protected String partitionName = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected String partitionName = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); Below are build errors: D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\framework\server\ClusterPartition.java:54: cannot find symbol symbol : variable DEFAULT_PARTITION location: class org.jboss.metadata.ClusterConfigMetaData protected String partitionName = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^ D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\hasessionstate\server\HASessionStateImpl.java:54: cannot find symbol symbol : variable DEFAULT_PARTITION location: class org.jboss.metadata.ClusterConfigMetaData protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^ I hope it may be useful and the format of my message is readable and this is the right place to post this piece of information. Best regards, Marcin Mieszek was: This is the first time I submit anything here.. so please be patient to me :) Module jboss-head failed to compile as in 1.7.6.1 version of org.jboss.metadata.ClusterConfigMetaData constant: public final static String DEFAULT_PARTITION = "DefaultPartition"; was replaced with default partition logic in org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: public static String getDefaultPartitionName() However, there are still references to DEFAULT_PARTITION in files: 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at line 54: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: protected String partitionName = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected String partitionName = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); I hope it may be useful and the format of my message is readable. Best regards, Marcin Mieszek > patched references to missing field DEFAULT_PARTITION in > org.jboss.metadata.ClusterConfigMetaData > - > > Key: JBAS-1520 > URL: http://jira.jboss.com/jira/browse/JBAS-1520 > Project: JBoss Application Server > Type: Patch > Components: Clustering > Reporter: Marcin Mieszek > Priority: Blocker > > > This is the first time I submit anything here.. so please be patient to me :) > Module jboss-head failed to compile as in 1.7.6.1 version of > org.jboss.metadata.ClusterConfigMetaData constant: > public final static String DEFAULT_PARTITION = "DefaultPartition"; > was replaced with default partition logic in > org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: > public static String getDefaultPartitionName() > However, there are still references to DEFAULT_PARTITION in files: > 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1520) patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData
patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData - Key: JBAS-1520 URL: http://jira.jboss.com/jira/browse/JBAS-1520 Project: JBoss Application Server Type: Patch Components: Clustering Reporter: Marcin Mieszek Priority: Blocker This is the first time I submit anything here.. so please be patient to me :) Module jboss-head failed to compile as in 1.7.6.1 version of org.jboss.metadata.ClusterConfigMetaData constant: public final static String DEFAULT_PARTITION = "DefaultPartition"; was replaced with default partition logic in org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: public static String getDefaultPartitionName() However, there are still references to DEFAULT_PARTITION in files: 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at line 54: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected final String DEFAULT_PARTITION_JNDI_NAME = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: protected String partitionName = org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; ^^ I suggest changing to: protected String partitionName = org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); I hope it may be useful and the format of my message is readable. Best regards, Marcin Mieszek -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1519) CMR deletion problems with 2 CMR's and one is batch-cascade-delete
[ http://jira.jboss.com/jira/browse/JBAS-1519?page=history ] Ian updated JBAS-1519: -- Attachment: CMPBug.zip This is a zipfile of an Eclipse project that implements the beans, plus Java source to run tests. > CMR deletion problems with 2 CMR's and one is batch-cascade-delete > -- > > Key: JBAS-1519 > URL: http://jira.jboss.com/jira/browse/JBAS-1519 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Windows XP, Java 1.4.2_06 > Reporter: Ian > Attachments: CMPBug.zip > > > When you have 3 beans (A, B, and C). A has a 1-1 mandatory relationship with > B, with B having a non-nullable foreign key in A. A has a 1-many relationship > with C, and C is marked for cascade-delete. The problem occurs when you > populate A (which means B must be populated), and C is populated with > references to A. Then you delete A. > From the trace, you can see that the batch-cascade-delete work is deferred on > relationship C. Then it attempts to set the foreign key field of B to null in > A - which is not allowed, and a database constraint is activated. > If you remove the relationship from A to C, everything is fine. If you don't > populate C, everything is fine. > I have included two portions of traces from the log files. > This portion of the log file occurs when C is populated (deleting A): > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.A] RESET PERSISTENCE > CONTEXT: id=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] load data: entity=A > pk=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] No preload data found: > entity=A pk=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.A] Default eager-load > for entity: readahead=null > 2005-02-25 09:53:10,772 DEBUG > [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.A] Executing SQL: > SELECT fk_B FROM A_TABLE WHERE (pk_A=?) > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.A#pkA] param: > i=1, type=INTEGER, value=1 > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.A#fkB] result: > i=1, type=java.lang.Integer, value=1000 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.A.c] Read ahead > cahce load: cmrField=c pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] load data: entity=A > pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] No preload data found: > entity=A pk=[.1.] > 2005-02-25 09:53:10,782 DEBUG > [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.A] load relation SQL: > SELECT pk_C FROM C_TABLE WHERE (fk_A=?) > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkA] param: > i=1, type=INTEGER, value=1 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkC] result: > i=1, type=java.lang.Integer, value=1 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add preload data: entity=C > pk=[.1.] field=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkC] result: > i=1, type=java.lang.Integer, value=2 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add preload data: entity=C > pk=[.2.] field=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add finder results: > entity=C results=[[.1.], [.2.]] readahead=[JDBCReadAheadMetaData : > strategy=on-load, pageSize=1000, eagerLoadGroup=*, left-join[]] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.C] RESET PERSISTENCE > CONTEXT: id=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] load data: entity=C > pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Preloading data: entity=C > pk=[.1.] cmrField=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.C] Scheduled for > batch-cascade-delete: [.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.C] RESET PERSISTENCE > CONTEXT: id=[.2.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] load data: entity=C > pk=[.2.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Preloading data: entity=C > pk=[.2.] cmrField=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.C] Scheduled for > batch-ca
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-82) Misused Error Messages in EntityToHibernateXml
Misused Error Messages in EntityToHibernateXml -- Key: EJBTHREE-82 URL: http://jira.jboss.com/jira/browse/EJBTHREE-82 Project: EJB 3.0 Type: Bug Reporter: Adriano Bonat Priority: Trivial The RuntimeException "failed to get ManyToMany" is used in other methods (handle*Relationship*) than handleManyToMany. This code could be view in: http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-ejb3/src/main/org/jboss/ejb3/entity/EntityToHibernateXml.java?view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-29) TypeInfo in ValueMetaData
TypeInfo in ValueMetaData
-
Key: JBMICROCONT-29
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-29
Project: JBoss MicroContainer
Type: Task
Components: MetaData
Versions: JBossMC_1_0_0M1
Reporter: Adrian Brock
Assigned to: Adrian Brock
Need to produce a clean api for the ValueMetaData
to retrieve TypeInfo/Class information.
e.g. StringValueMetaData might want to override a specific type
to a concrete implementation when using the PropertyEditors:
hypothetical example (specifying a concrete implementation for a property
that defines an interface)
public void setSomething(Map map) {}
Similar issue with collections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-25) Configurator tidyup
[
http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=comments#action_12315786 ]
Adrian Brock commented on JBMICROCONT-25:
-
Also need to make sure BeanInfo api is only looking at public
non static methods. I know this is not currently the case,
see the FIXME in Configurator:
public static MethodJoinpoint findMethod(boolean trace, BeanInfo info,
String name, List parameters, boolean isStatic, boolean isPublic) throws
Throwable
{
String[] paramTypes = getParameterTypes(trace, parameters);
MethodInfo minfo = findMethodInfo(info.getClassInfo(), name, paramTypes);
// FIXME isStatic, isPublic);
JoinpointFactory jpf = info.getJoinpointFactory();
return jpf.getMethodJoinpoint(minfo);
}
> Configurator tidyup
> ---
>
> Key: JBMICROCONT-25
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25
> Project: JBoss MicroContainer
> Type: Task
> Components: Configurator
> Reporter: Adrian Brock
> Priority: Minor
>
>
> The Configurator api is largely being replaced by the JoinPointFactory api.
> There is still a usecase for some of the Configurator api as a convenience
> mechanism
> on top of the JoinPointFactory.
> This needs cleaning up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBMICROCONT-28) BeanMetaData should implement ValueMetaData
[ http://jira.jboss.com/jira/browse/JBMICROCONT-28?page=history ] Adrian Brock reassigned JBMICROCONT-28: --- Assign To: Adrian Brock > BeanMetaData should implement ValueMetaData > --- > > Key: JBMICROCONT-28 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-28 > Project: JBoss MicroContainer > Type: Task > Components: MetaData > Reporter: Adrian Brock > Assignee: Adrian Brock > > > BeanMetaData should implement ValueMetaData > where the value is the bean constructed. > This allows direct configuration like: > > > > etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-28) BeanMetaData should implement ValueMetaData
BeanMetaData should implement ValueMetaData --- Key: JBMICROCONT-28 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-28 Project: JBoss MicroContainer Type: Task Components: MetaData Reporter: Adrian Brock BeanMetaData should implement ValueMetaData where the value is the bean constructed. This allows direct configuration like: etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-27) Need to add a notion of classloader to the Constructor/Bean/DeploymentMetaData/BeanMetaData
Need to add a notion of classloader to the Constructor/Bean/DeploymentMetaData/BeanMetaData --- Key: JBMICROCONT-27 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-27 Project: JBoss MicroContainer Type: Task Components: MetaData Versions: JBossMC_1_0_0M1 Reporter: Adrian Brock Need to add classloader configuration to Constructor/Bean/Deployment MetaData. This is just an additional ValueMetaData that can be either a classloader object, a dependendency reference to a classloader beanmetadata or a direct bean construct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-22) Implement Build for jaxrpc
[ http://jira.jboss.com/jira/browse/JBBUILD-22?page=comments#action_12315785 ] Ryan Campbell commented on JBBUILD-22: -- I have implemented this build with the following caveats: 1. A compilation of any source now includes copying **/*.properties to the output! - the alternative (and real solution) to this is to extract those property files to a subdir under resources, but I don't want to alter the source just for the new build. 2. build.resources no longer requires src/resources to exist. jaxrpc has resources, but they aren't located in src/resources. 3. The old build required xerces to be in the root classpath of javac. This might be an issue when we port the build to 3.2 which needs to be compiled with jdk1.3? > Implement Build for jaxrpc > -- > > Key: JBBUILD-22 > URL: http://jira.jboss.com/jira/browse/JBBUILD-22 > Project: JBoss Build System > Type: Sub-task > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Fix For: Q105 > > > Build axis-ws4ee.jar in the jaxrpc module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-17) execant is broken on windows
[ http://jira.jboss.com/jira/browse/JBBUILD-17?page=comments#action_12315780 ] Ryan Campbell commented on JBBUILD-17: -- This needs to be fixed in tools/etc/jbossbuild/tasks.xml in jboss-head. > execant is broken on windows > > > Key: JBBUILD-17 > URL: http://jira.jboss.com/jira/browse/JBBUILD-17 > Project: JBoss Build System > Type: Bug > Reporter: Ryan Campbell > Fix For: Q105 > > > When I tried to execute synchronize, I received an IOException: CreateProcess > ant -f jbossbuild.xml synchronize.after error=2 > From what I can tell, error=2 is file not found. I think this is because of > the way execant is implemented using the exec task. > executable="ant" > > > > > For windows it should be: > executable="cmd" > > > > > So to fix this, we just need to do some conditional processing using the os > family information like in testsuite/imports/server-config.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Problem with demo
You are using windows runShellDemo.bat arent You ? In fact there is a bug in it. The line : set CLASSPATH=%CACHE_LIB%/commons-logging.jar;%CACHE_LIB%/bsh-1.3.0.jar;%CACHE_LIB%/bsh-commands-1.3.0.jar;%CACHE_LIB%/jboss-aop.jar;%CACHE_LIB%/jboss-j2ee.jar;%CACHE_LIB%/jgroups.jar;%CACHE_LIB%/jboss-cache.jar;%CACHE_LIB%/jboss-jmx.jar;%CACHE_LIB%/trove.jar;%CACHE_LIB%/javassist.jar;%CACHE_LIB%/jboss-minimal.jar;%CACHE_LIB%/jboss-common.jar;%CACHE_LIB%/jboss-system.jar;%CACHE_LIB%/log4j.jar;%CACHE_LIB%/concurrent.jar;%CACHE_LIB%/je.jar;%CACHE_LIB/jboss-remoting.jar shuld be changed to set CLASSPATH=%CACHE_LIB%/commons-logging.jar;%CACHE_LIB%/bsh-1.3.0.jar;%CACHE_LIB%/bsh-commands-1.3.0.jar;%CACHE_LIB%/jboss-aop.jar;%CACHE_LIB%/jboss-j2ee.jar;%CACHE_LIB%/jgroups.jar;%CACHE_LIB%/jboss-cache.jar;%CACHE_LIB%/jboss-jmx.jar;%CACHE_LIB%/trove.jar;%CACHE_LIB%/javassist.jar;%CACHE_LIB%/jboss-minimal.jar;%CACHE_LIB%/jboss-common.jar;%CACHE_LIB%/jboss-system.jar;%CACHE_LIB%/log4j.jar;%CACHE_LIB%/concurrent.jar;%CACHE_LIB%/je.jar;%CACHE_LIB%/jboss-remoting.jar As you can see, the first line does not provide the correct path for the jboss-remoting.jar, CASHE_LIB is not evaluated as required : %CACHE_LIB/jboss-remoting.jar Hope it will be helpful. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867829#3867829 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867829 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1501) ClusterConfigMetaData should check for the new partition name system property
[ http://jira.jboss.com/jira/browse/JBAS-1501?page=history ] Adrian Brock closed JBAS-1501: -- Resolution: Done Fix Version: JBossAS-4.0.2RC1 This has been done. All hardwiring of "DefaultPartition" has been replaced with a new ServerConfigUtil.getDefaultPartition() static method that first looks at the System property jboss.partition.name before using "DefaultPartition" > ClusterConfigMetaData should check for the new partition name system property > - > > Key: JBAS-1501 > URL: http://jira.jboss.com/jira/browse/JBAS-1501 > Project: JBoss Application Server > Type: Feature Request > Components: EJBs > Versions: JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assignee: Adrian Brock > Priority: Minor > Fix For: JBossAS-4.0.2RC1 > > > org.jboss.metadata.ClusterConfigMetaData > should check for the new system property jboss.partition.name > before using DefaultPartition. > Need to also check the codebase for other such hardwiring that > cannot (has not already) be fixed by MBean attribute configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design the new POJO MicroContainer] - Re: Boston meeting notes: Two phase join point factory const
Does the getInstanceAdapter get called if there are annotation overrides? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867822#3867822 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867822 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050224151345 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 02/24/2005 15:13:45Time to build: 16 minutes 22 secondsLast changed: 02/24/2005 14:52:05Last log entry: [JBAS-1501] - Add defaults for using jboss.partition.name in ejb cluster configuration Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (115)1.88.2.5modifiedejortserver/src/etc/conf/default/standardjboss.xml[JBAS-1501] - Add defaults for using jboss.partition.name in ejb cluster configuration1.12.2.4modifiedejortremoting/.classpathFix the elipse build (again).Please be more careful when porting between different releases!1.12.2.3modifiedtelrodremoting/.classpathJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.8.2modifiedtelrodremoting/build.batJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.8.2modifiedtelrodremoting/build.shJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.17.2.2modifiedtelrodremoting/build.xmlJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.1.2.2modifiedtelrodremoting/tests/build.shJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.5.2.2modifiedtelrodremoting/tests/build.xmlJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/detection/SimpleDetectorClient.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/detection/SimpleDetectorServer.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/simple/SimpleClient.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/simple/SimpleServer.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/callback/CallbackClient.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/samples/callback/CallbackServer.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.3.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/socket/InvokerServerTest.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.3.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/socket/InvokerTestCase.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.4.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/socket/InvokerClientTest.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/rmi/RMIInvokerServerTest.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.3.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/rmi/RMIInvokerTestCase.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/rmi/RMIInvokerClientTest.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.1.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/mock/MockClientInvoker.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.4.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/mock/MockServerInvocationHandler.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/mock/MockServerInvoker.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.1.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/mock/MockTest.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.3.6.1modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/http/HTTPInvokerTestServer.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/local/LocalInvocationTestCase.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.1.6.1modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/http/ComplexObject.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.2modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/http/HTTPInvokerClientTestCase.javaJBREM-37 - backport of jboss remoting 1.0.1 final to 4.0 branch.1.2.2.1modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/http/HTTPInvokerTestCase.javaJBREM-37 -
[JBoss-dev] jboss-head build.832 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050224141318Lbuild.832 BUILD COMPLETE - build.832Date of build: 02/24/2005 14:13:18Time to build: 24 minutes 58 secondsLast changed: 02/24/2005 12:39:08Last log entry: get rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (23)1.3deletedpatriot1burkeaspects/src/main/org/jboss/aspects/ioc/DependencyInjectorContainer.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.2deletedpatriot1burkeaspects/src/main/org/jboss/aspects/ioc/Factory.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.2deletedpatriot1burkeaspects/src/main/org/jboss/aspects/ioc/Identifier.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.5deletedpatriot1burkeaspects/src/main/org/jboss/aspects/ioc/IocInterceptor.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.5deletedpatriot1burkeaspects/src/main/org/jboss/aspects/ioc/IocPointcut.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.3deletedpatriot1burkeaspects/src/test/test/ioc/IocTest.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.2deletedpatriot1burkeaspects/src/test/test/ioc/POJO.javaget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.2deletedpatriot1burkeaspects/src/test/test/ioc/META-INF/jboss-aop.xmlget rid of AOP/IOC stuff. It needs to be rewritten and is inhibiting 2.0 refactoring1.7modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/initial/unit/RemoteUnitTestCase.javadisassociate imported TX from thread when leaving1.4modifiedpatriot1burkeaspects/src/main/org/jboss/aspects/tx/TxPropagationInterceptor.javadisassociate imported TX from thread when leaving1.2deletedccrouchadmin-console/tmp_libs/easymock-1.1.jarJBADMCON-64 delete now since struts test case and easymock jars are in thirdparty folder1.2deletedccrouchadmin-console/tmp_libs/easymockclassextension.jarJBADMCON-64 delete now since struts test case and easymock jars are in thirdparty folder1.2deletedccrouchadmin-console/tmp_libs/strutstest-2.1.3.jarJBADMCON-64 delete now since struts test case and easymock jars are in thirdparty folder1.14modifiedccrouchadmin-console/build.xmlupdated to remove warning during build1.8modifiedanddadmin-console/README.txtminor path changes1.14modifiedrecampbelljbossas/jbossbuild.xmlJBBBUILD-21 - added system module1.1addedrecampbellsystem/jbossbuild.xmlJBBUILD-21 - initial checkin, correctly builds jboss-system.jar1.9modifiedejortcontainer/src/main/org/jboss/reflect/plugins/introspection/IntrospectionTypeInfoFactory.javaJavadoc tidyup1.8modifiedejortcontainer/src/main/org/jboss/reflect/plugins/introspection/IntrospectionTypeInfoFactory.javaPerformance improvement (mainly for tests).Use a static delegate for the reflected type info factoryto avoid the same information getting recalculated over and overagain when new TypeInfoFactorys are instantiatedin the same classloader.1.1addedejortcontainer/src/main/org/jboss/reflect/plugins/introspection/IntrospectionTypeInfoFactoryImpl.javaPerformance improvement (mainly for tests).Use a static delegate for the reflected type info factoryto avoid the same information getting recalculated over and overagain when new TypeInfoFactorys are instantiatedin the same classloader.1.226modifiedbelabancache/src/main/org/jboss/cache/TreeCache.javaadded trace stmt when node is not found in _put()1.13modifiedccrouchadmin-console/build.xmlJBADMCON-64 reference struts test case and easymock jars in thirdparty folder1.15modifiedbelabancache/src/main/org/jboss/cache/loader/FileCacheLoader.javaapplied Tom Bakken's patch for memleak in FileCacheLoader (http://jira.jboss.com/jira/browse/JBCACHE-96)
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-714) Automatically include everything in jboss/lib to classpath
[ http://jira.jboss.com/jira/browse/JBAS-714?page=history ] Scott M Stark closed JBAS-714: -- > Automatically include everything in jboss/lib to classpath > -- > > Key: JBAS-714 > URL: http://jira.jboss.com/jira/browse/JBAS-714 > Project: JBoss Application Server > Type: Feature Request > Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assignee: Scott M Stark > Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1 > > > SourceForge Submitter: rmcauble . > This is a convenience to as not to have to explictly list > out each jar in jboss/lib. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-275) 2 identical named mdbs cannot deploy
[ http://jira.jboss.com/jira/browse/JBAS-275?page=history ] Scott M Stark closed JBAS-275: -- > 2 identical named mdbs cannot deploy > > > Key: JBAS-275 > URL: http://jira.jboss.com/jira/browse/JBAS-275 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assignee: Scott M Stark > Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1 > > > SourceForge Submitter: charris . > Two MDBs, both with the same ejb-name but *in different > ejb-jars*, both produce MBeans with ObjectName > jboss.j2ee:jndiName=local/MyMDBEJBName,service=EJB > meaning that the second MDB will not deploy properly > since the MBeanServer returns > InstanceAlreadyExistsException. The ObjectNames are > formed with the prefix "/local" to produce a dummy jndi > name, but need to be more unique than this to avoid the > clash. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-98) New constructor GenericInterceptorFactory(Class, Element)
New constructor GenericInterceptorFactory(Class, Element) - Key: JBAOP-98 URL: http://jira.jboss.com/jira/browse/JBAOP-98 Project: JBoss AOP Type: Bug Reporter: Kabir Khan Fix For: 2.0, 1.1.1 Wanted by Rajiv Kadayam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-98) New constructor GenericInterceptorFactory(Class, Element)
[ http://jira.jboss.com/jira/browse/JBAOP-98?page=history ] Kabir Khan closed JBAOP-98: --- Resolution: Done > New constructor GenericInterceptorFactory(Class, Element) > - > > Key: JBAOP-98 > URL: http://jira.jboss.com/jira/browse/JBAOP-98 > Project: JBoss AOP > Type: Bug > Reporter: Kabir Khan > Fix For: 2.0, 1.1.1 > > > Wanted by Rajiv Kadayam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12315775 ] David Dossot commented on JBCACHE-98: - I have tried using a more recent jboss-cache.jar but it resulted in class cast exceptions. Maybe I did it wrong but it seemed not an option. > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-96) TxPropagationInterceptor doesn't disassociate thread
[ http://jira.jboss.com/jira/browse/JBAOP-96?page=history ] Bill Burke closed JBAOP-96: --- Resolution: Done > TxPropagationInterceptor doesn't disassociate thread > > > Key: JBAOP-96 > URL: http://jira.jboss.com/jira/browse/JBAOP-96 > Project: JBoss AOP > Type: Bug > Components: Aspect Library > Versions: 1.1 > Reporter: Bill Burke > Fix For: 1.1.1 > > > The TxPropagationInterceptor needs to suspend the TX (dissassociate it from > the thread) if the tx was imported. Otherwise, the thread is never > disassociated from the transaction and the transaction is leaked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAOP-71) java.lang.StackOverflowError in execution of INTRODUCED interface methods
[ http://jira.jboss.com/jira/browse/JBAOP-71?page=history ] Bill Burke updated JBAOP-71: Fix Version: (was: 1.1.1) Not sure if I'm going to accept this yet...The thing is, if you're just introducing an interface with no mixin, then an interceptor should handle the implementation. > java.lang.StackOverflowError in execution of INTRODUCED interface methods > - > > Key: JBAOP-71 > URL: http://jira.jboss.com/jira/browse/JBAOP-71 > Project: JBoss AOP > Type: Bug > Versions: 1.1 > Environment: Windows XP, JBoss-AOP v1.1 Standalone > Reporter: Paul Extance > Assignee: Bill Burke > Priority: Critical > > > When an Interface is INTRODUCED into a class, the ClassAdvisor sets the > 'unadvisedMethod' and the 'advisedMethod' fields on a MethodInfo instance to > the same value (provided there was no implementation for an Interface's > method on the original class). > The introduced method invokes the invokeNext() method on an attached > interceptor-stack and finally invokes the 'unadvisedMethod', which is itself. > This results in an infinite loop, which raises java.lang.StackOverflowError > There was no such problem in 'jboss-aop_1.0.0-FINAL', since the > 'unadvisedMethod' would be set to null, if there was no implementation for an > Interface's method on the original class. > Since then, the following change to the ClassAdvisor sets an erroneous value > to the 'unadvisedMethod' field on the MethodInfo instance > http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-aop/src/main/org/jboss/aop/ClassAdvisor.java?r1=1.95&r2=1.96 > To fix the problem, remove 'if (umethod == null) umethod = amethod;' in the > initializeMethodChain() method of ClassAdvisor. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1516) Tomcat5: StandardContext getConfigBase tries to create a directory
[
http://jira.jboss.com/jira/browse/JBAS-1516?page=comments#action_12315773 ]
Remy Maucherat commented on JBAS-1516:
--
This is now fixed in Tomcat upstream. Thanks for the report.
> Tomcat5: StandardContext getConfigBase tries to create a directory
> --
>
> Key: JBAS-1516
> URL: http://jira.jboss.com/jira/browse/JBAS-1516
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1
> Environment: JBoss 4.0.1sp1, Solaris8
> Reporter: Roland R?z
> Assignee: Remy Maucherat
> Priority: Critical
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> Hello,
> Just to explain you the circumstances why this request has arised.
> I try to secure JBoss with a java security policy. The policy should prevent
> somebody from writing in the JBoss installation directory.
> For this reason I set a File permission that allows only reading on the
> JBoss installation directory.
> It looks like this
> grant {
> permission java.io.FilePermission "${jboss.home.dir}/-", "read";
> ...
> };
> Now when I start JBoss and deploy a War file I receive the following
> AccessPermissionException
> Caused by: java.security.AccessControlException: access denied
> (java.io.FilePermission
> /opt/jboss/4.0.1/server/myserver/conf/jboss.web/localhost write)
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
> at java.security.AccessController.checkPermission(AccessController.java:401)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.File.mkdir(File.java:1097)
> at java.io.File.mkdirs(File.java:1122)
> at
> org.apache.catalina.core.StandardContext.getConfigBase(StandardContext.java:4858)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4071)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121)
> at
> org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:805)
> at org.a
> pache.catalina.core.StandardHost.addChild(StandardHost.java:595)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> ... 152 more
> The method that creates the Exception looks like this
> private File org.apache.catalina.core.StandardContext#getConfigBase()
> {
> File configBase = new File(System.getProperty("catalina.base"),
> "conf");
> if(!configBase.exists())
> return null;
> Container container = this;
> Container host = null;
> Container engine = null;
> for(; container != null; container = container.getParent())
> {
> if(container instanceof Host)
> host = container;
> if(container instanceof Engine)
> engine = container;
> }
> if(engine != null)
> configBase = new File(configBase, engine.getName());
> if(host != null)
> configBase = new File(configBase, host.getName());
> configBase.mkdirs(); // here it crashes
> return configBase;
> }
> JBoss sets the saveConfig Flag of the StandardContext to false.
> (see TomcatDeployer#performDeployInternal)
> configBase.mkdirs() should only be invoked if the saveConfig Flag is set to
> true.
> Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12315772 ] Ben Wang commented on JBCACHE-98: - I am thinking about not backporting. Instead, we should be able to replace just jboss-cache.jar from release 1.2.1 as a patch to 4.0.0 and 4.0.1. Of, course, QA may need to test this one out. > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBBUILD-21) Implement build for system module
[ http://jira.jboss.com/jira/browse/JBBUILD-21?page=history ] Ryan Campbell reassigned JBBUILD-21: Assign To: Ryan Campbell > Implement build for system module > - > > Key: JBBUILD-21 > URL: http://jira.jboss.com/jira/browse/JBBUILD-21 > Project: JBoss Build System > Type: Sub-task > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Priority: Critical > Fix For: Q105 > > > Implement the build for this module. > Completion of this module requires implementation of sourcejar as log4j.jar > and getopt.jar need to be unpacked and their contents shuffled about. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (JBAS-1516) Tomcat5: StandardContext getConfigBase tries to create a directory
[ http://jira.jboss.com/jira/browse/JBAS-1516?page=history ]
Scott M Stark moved JBWEB-13 to JBAS-1516:
--
Project: JBoss Application Server (was: JBoss Web)
Key: JBAS-1516 (was: JBWEB-13)
Component: Web (Tomcat) service
(was: Tomcat)
Version: JBossAS-4.0.1 SP1
JBossAS-4.0.1 Final
JBossAS-3.2.7 Final
(was: JBossWeb-4.0.1)
Fix Version: JBossAS-4.0.2 Final
JBossAS-5.0 Alpha
JBossAS-3.2.8 Final
Security Level: Public
> Tomcat5: StandardContext getConfigBase tries to create a directory
> --
>
> Key: JBAS-1516
> URL: http://jira.jboss.com/jira/browse/JBAS-1516
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1
> Environment: JBoss 4.0.1sp1, Solaris8
> Reporter: Roland R?z
> Assignee: Remy Maucherat
> Priority: Minor
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> Hello,
> Just to explain you the circumstances why this request has arised.
> I try to secure JBoss with a java security policy. The policy should prevent
> somebody from writing in the JBoss installation directory.
> For this reason I set a File permission that allows only reading on the
> JBoss installation directory.
> It looks like this
> grant {
> permission java.io.FilePermission "${jboss.home.dir}/-", "read";
> ...
> };
> Now when I start JBoss and deploy a War file I receive the following
> AccessPermissionException
> Caused by: java.security.AccessControlException: access denied
> (java.io.FilePermission
> /opt/jboss/4.0.1/server/myserver/conf/jboss.web/localhost write)
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
> at java.security.AccessController.checkPermission(AccessController.java:401)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.File.mkdir(File.java:1097)
> at java.io.File.mkdirs(File.java:1122)
> at
> org.apache.catalina.core.StandardContext.getConfigBase(StandardContext.java:4858)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4071)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121)
> at
> org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:805)
> at org.a
> pache.catalina.core.StandardHost.addChild(StandardHost.java:595)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> ... 152 more
> The method that creates the Exception looks like this
> private File org.apache.catalina.core.StandardContext#getConfigBase()
> {
> File configBase = new File(System.getProperty("catalina.base"),
> "conf");
> if(!configBase.exists())
> return null;
> Container container = this;
> Container host = null;
> Container engine = null;
> for(; container != null; container = container.getParent())
> {
> if(container instanceof Host)
> host = container;
> if(container instanceof Engine)
> engine = container;
> }
> if(engine != null)
> configBase = new File(configBase, engine.getName());
> if(host != null)
> configBase = new File(configBase, host.getName());
> configBase.mkdirs(); // here it crashes
> return configBase;
> }
> JBoss sets the saveConfig Flag of the StandardContext to false.
> (see TomcatDeployer#performDeployInternal)
> configBase.mkdirs() should only be invoked if the saveConfig Flag is set to
> true.
> Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Rea
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-75) make event propagation configurable
[ http://jira.jboss.com/jira/browse/JBPM-75?page=history ] Tom Baeyens updated JBPM-75: Priority: Major (was: Optional) Original Estimate: 14400 Remaining Estimate: 14400 Fix Version: 3.0 alpha 3 most of the event propagation is done. the configuration option that should be added is that graph elements should be able to block propagation of events they fire. > make event propagation configurable > --- > > Key: JBPM-75 > URL: http://jira.jboss.com/jira/browse/JBPM-75 > Project: JBoss jBPM > Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: 3.0 alpha 3 > > Original Estimate: 4 hours > Remaining: 4 hours > > event propagation might become a bottleneck in high-throughput deployments. > the easiest way to solve this is by introducing a configuration property that > overrides the default behaviour of event propagation. the current default is > that event propagation is active. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-58) persistence
[ http://jira.jboss.com/jira/browse/JBPM-58?page=history ] Tom Baeyens updated JBPM-58: Original Estimate: 432000 Remaining Estimate: 432000 > persistence > --- > > Key: JBPM-58 > URL: http://jira.jboss.com/jira/browse/JBPM-58 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: 3.0 alpha 2 > > Original Estimate: 3 weeks > Remaining: 3 weeks > > 1) how to delete process instances and process definitions : cascading > deletes ? > 2) long or Long for id's. is there a preference. i have experienced some > problems with the null-value not being interpreted as i had hoped in case of > long but that might be my ignorance. > 3) query tokens and/or process instances based on process variables. how to > query the > 4) Variable persistence: is the serializable type of hibernate better then my > ServializableValue (using commons base64 encoding) > 5) what is the most portable way to store the variable types float and double > ? > 6) does a private default constructor blocks some optimizations. (i want to > get rid of most of the default constructors in the javadocs and making them > private seems the easiest way) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-45) undo undoable actions in case of exceptions
[ http://jira.jboss.com/jira/browse/JBPM-45?page=history ] Tom Baeyens updated JBPM-45: Description: suppose a client calls token.signal() and the engine starts calculating the next state. during this calculation, a few undoable action handlers are executed. then an actionhandler throws an exception. then we want a configurable option to specify that the executed actions have to be undone. in jbpm2, this feature was not yet available. was: suppose a client calls token.signal() and the engine starts calculating the next state. during this calculation, a few undoable action handlers are executed. then an actionhandler throws an exception. then we want a configurable option to specify that the executed actions have to be undone. in jbpm2, this feature was not yet available. Environment: Priority: Minor (was: Major) > undo undoable actions in case of exceptions > --- > > Key: JBPM-45 > URL: http://jira.jboss.com/jira/browse/JBPM-45 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Minor > > > suppose a client calls token.signal() and the engine starts calculating the > next state. during this calculation, a few undoable action handlers are > executed. then an actionhandler throws an exception. then we want a > configurable option to specify that the executed actions have to be undone. > in jbpm2, this feature was not yet available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPM-59) refactor relations
[ http://jira.jboss.com/jira/browse/JBPM-59?page=history ] Tom Baeyens resolved JBPM-59: - Resolution: Done > refactor relations > -- > > Key: JBPM-59 > URL: http://jira.jboss.com/jira/browse/JBPM-59 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > > make all relation-managers private. redirect use of relation managers to > target object if necessary. > change CollectionMgr to ListMgr. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-68) finish pluggability for par parsers
[ http://jira.jboss.com/jira/browse/JBPM-68?page=history ] Tom Baeyens updated JBPM-68: Fix Version: 3.0 alpha 2 > finish pluggability for par parsers > --- > > Key: JBPM-68 > URL: http://jira.jboss.com/jira/browse/JBPM-68 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: 3.0 alpha 2 > > Time Spent: 1 day >Remaining: 1 hour > > when users want to extend jbpm with their custom modules, we should also > support pluggability of the module parsers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-46) scheduler
[ http://jira.jboss.com/jira/browse/JBPM-46?page=history ] Tom Baeyens updated JBPM-46: Original Estimate: 86400 Remaining Estimate: 86400 Fix Version: 3.0 alpha 3 (was: 3.0 alpha 2) > scheduler > - > > Key: JBPM-46 > URL: http://jira.jboss.com/jira/browse/JBPM-46 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > Fix For: 3.0 alpha 3 > > Original Estimate: 3 days > Remaining: 3 days > > implement the scheduler functionality + a simple servlet that acts as a > cron-task to check for due jobs on regular intervals. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-29) xml serialization and parsing of process definitions
[ http://jira.jboss.com/jira/browse/JBPM-29?page=history ] Tom Baeyens updated JBPM-29: Description: sub tasks/features: * xml serialization of process definitions * xml parsing of process definitions * w3c schema for the process definition (xsd) * optional validation against xsd less important: * dtd schema * dtd validation * allow for schema selection in xml serialization : none, xsd, dtd was: sub tasks/features: * xml serialization of process definitions * xml parsing of process definitions * w3c schema for the process definition (xsd) * optional validation against xsd less important: * dtd schema * dtd validation * allow for schema selection in xml serialization : none, xsd, dtd Environment: Original Estimate: 86400 (was: 144000) Remaining Estimate: 86400 (was: 144000) Fix Version: 3.0 alpha 2 most of the parsing is done. lots of the xml writing still needs to be done. the xml-schema is documented. we're looking for volunteers to write the w3c schema and/or the dtd > xml serialization and parsing of process definitions > > > Key: JBPM-29 > URL: http://jira.jboss.com/jira/browse/JBPM-29 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: 3.0 alpha 2 > > Original Estimate: 3 days > Remaining: 3 days > > sub tasks/features: > * xml serialization of process definitions > * xml parsing of process definitions > * w3c schema for the process definition (xsd) > * optional validation against xsd > less important: > * dtd schema > * dtd validation > * allow for schema selection in xml serialization : none, xsd, dtd -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Image galery module dev
Hi lepe. Managing static content can be achieved in two ways : The Apacha way, if you use it in front of tomcat. That's pure http.conf hack, so this forum is not the right place to discuss it, contact me. The tomcat way. You can create an additional static context in Tomcat, not linked with nukes (see my previous reply http://jboss.org/index.html?module=bb&op=viewtopic&t=57461) The former is far more powerfull, the later far more simple. see http://enfanceetcroissance.com see http://gitesprovence.fr.to View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867789#3867789 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867789 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-79) Compensation Handling
Compensation Handling - Key: JBPM-79 URL: http://jira.jboss.com/jira/browse/JBPM-79 Project: JBoss jBPM Type: Sub-task Reporter: Juan Cantu Assigned to: Juan Cantu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-53) Rewrite of ENC for Web, EJB 2.1, and EJB 3.0
[ http://jira.jboss.com/jira/browse/JBAS-53?page=history ] Scott M Stark updated JBAS-53: -- Fix Version: (was: JBossAS-4.0.2 Final) > Rewrite of ENC for Web, EJB 2.1, and EJB 3.0 > > > Key: JBAS-53 > URL: http://jira.jboss.com/jira/browse/JBAS-53 > Project: JBoss Application Server > Type: Feature Request > Components: Naming > Versions: JBossAS-4.0.2 Final > Reporter: Bill Burke > Assignee: Bill Burke > > Original Estimate: 1 day > Remaining: 1 day > > Make the ENC be threadlocal based rather than classloader based as > classloader based can give incorrect behavior. This task will be dependent > on a JBoss 4.0 point release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1293) AOP HTTP session replication under Tomcat 5
[ http://jira.jboss.com/jira/browse/JBAS-1293?page=history ] Scott M Stark updated JBAS-1293: Fix Version: (was: JBossAS-4.0.2 Final) > AOP HTTP session replication under Tomcat 5 > --- > > Key: JBAS-1293 > URL: http://jira.jboss.com/jira/browse/JBAS-1293 > Project: JBoss Application Server > Type: Feature Request > Components: Clustering > Versions: JBossAS-4.0.1 Final > Reporter: Bela Ban > Assignee: Ben Wang > Fix For: JBossAS-5.0 Alpha > > Original Estimate: 10 weeks > Remaining: 10 weeks > > Use TreeCacheAop to do field level http session replication. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1286) EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException
[ http://jira.jboss.com/jira/browse/JBAS-1286?page=comments#action_12315767 ] Frank Merenda commented on JBAS-1286: - Thanks Adrian! I appreciate the help. I will have a look at this after JBoss world. -Frank > EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException > - > > Key: JBAS-1286 > URL: http://jira.jboss.com/jira/browse/JBAS-1286 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1RC1 > Environment: Linux, 2.6.9 kernel. jdk build 1.5.0-b64. JBoss 4.0.1RC1. EJB > Preview 2. > Reporter: Frank Merenda > Priority: Minor > > > If I have a EJB 3 SLSB deployed in an .ear file, and I create a separate .war > file (not in the ear file) to access that SLSB it works fine upon server > startup. If I touch the .ear file everything still works fine. If I touch the > .war file, I get a ClassCastException: > java.lang.ClassCastException: $Proxy76 > at > org.jboss.jbossnetwork.pushportal.business.ApplicationFacade.login(ApplicationFacade.java:23) > at > I am referencing the SLSB from the war file with the following code: > InitialContext ctx = new InitialContext(); > Login login = (Login) ctx.lookup(LoginRemote.class.getName()); > It is blowing up on the second line. > This is repeatable 100% of the time. If I restart the app server it works > correctly again. If I just re-touch both the .ear and the .war I will still > get the CCE. > I was not sure if this goes into the EJB3 or the JBoss AS project. There were > other ClassCastExceptions in the AS project, so I put it in here. > I've attached the .war and .ear file. You can deploy them in JBoss 4.0.1RC2 > with EJB3 set up. (update if no attachment, email me at [EMAIL PROTECTED] and > I will send them. I don't see an attach on the bug request). I will try to > add it after I file the bug. > Steps to repeat: > 1) deploy war and ear files. > 2) go to http://localhost:8080/jbosspush/login.html > 3) type in any 4 letters for the username and password. You are sent to the > main page. > 4) touch jboss-4.0.1RC1/server/all/deploy/jbosspush.war. Wait for hot deploy. > 5) go to http://localhost:8080/jbosspush/login.html > 6) type in any 4 letters for the username and password. You are sent to > placeholder error page. Trace is in the log. > 7) restart jboss server > 8) repeat steps 1-3. Everything works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBADMCON-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Dimitris Andreadis closed JBADMCON-91: -- Resolution: Rejected It is possible to *not* include the isSameRM-override-value entry by simply not including the key in the properties map. Look for example the "use-java-context" property in the xa-datasource template. No value is passed and nothing gets produced in the testsuite. I also verified that explicitly with isSameRM. > 'isSameRMValue' always gets set to true or false > -- > > Key: JBADMCON-91 > URL: http://jira.jboss.com/jira/browse/JBADMCON-91 > Project: JBoss Admin Console > Type: Bug > Components: DataSource > Versions: 1.0 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 4 hours > Remaining: 4 hours > > The 'isSameRMValue' property for an XA DataSource is always being set to > either true or false, there is no way to leave it unspecified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-78) Fault and Termination Handling
Fault and Termination Handling -- Key: JBPM-78 URL: http://jira.jboss.com/jira/browse/JBPM-78 Project: JBoss jBPM Type: Sub-task Reporter: Juan Cantu Assigned to: Juan Cantu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1286) EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException
[ http://jira.jboss.com/jira/browse/JBAS-1286?page=history ] Adrian Brock reassigned JBAS-1286: -- Assign To: (was: Adrian Brock) > EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException > - > > Key: JBAS-1286 > URL: http://jira.jboss.com/jira/browse/JBAS-1286 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1RC1 > Environment: Linux, 2.6.9 kernel. jdk build 1.5.0-b64. JBoss 4.0.1RC1. EJB > Preview 2. > Reporter: Frank Merenda > Priority: Minor > > > If I have a EJB 3 SLSB deployed in an .ear file, and I create a separate .war > file (not in the ear file) to access that SLSB it works fine upon server > startup. If I touch the .ear file everything still works fine. If I touch the > .war file, I get a ClassCastException: > java.lang.ClassCastException: $Proxy76 > at > org.jboss.jbossnetwork.pushportal.business.ApplicationFacade.login(ApplicationFacade.java:23) > at > I am referencing the SLSB from the war file with the following code: > InitialContext ctx = new InitialContext(); > Login login = (Login) ctx.lookup(LoginRemote.class.getName()); > It is blowing up on the second line. > This is repeatable 100% of the time. If I restart the app server it works > correctly again. If I just re-touch both the .ear and the .war I will still > get the CCE. > I was not sure if this goes into the EJB3 or the JBoss AS project. There were > other ClassCastExceptions in the AS project, so I put it in here. > I've attached the .war and .ear file. You can deploy them in JBoss 4.0.1RC2 > with EJB3 set up. (update if no attachment, email me at [EMAIL PROTECTED] and > I will send them. I don't see an attach on the bug request). I will try to > add it after I file the bug. > Steps to repeat: > 1) deploy war and ear files. > 2) go to http://localhost:8080/jbosspush/login.html > 3) type in any 4 letters for the username and password. You are sent to the > main page. > 4) touch jboss-4.0.1RC1/server/all/deploy/jbosspush.war. Wait for hot deploy. > 5) go to http://localhost:8080/jbosspush/login.html > 6) type in any 4 letters for the username and password. You are sent to > placeholder error page. Trace is in the log. > 7) restart jboss server > 8) repeat steps 1-3. Everything works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-93) Memory problem at repeated remote PUT
[ http://jira.jboss.com/jira/browse/JBCACHE-93?page=comments#action_12315763 ] Bela Ban commented on JBCACHE-93: - Doesn't compile, you have some HM specific classes. Please modify your code and resubmit it. Thanks, > Memory problem at repeated remote PUT > - > > Key: JBCACHE-93 > URL: http://jira.jboss.com/jira/browse/JBCACHE-93 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Environment: * Windows cluster with two W2K servers, 2 JVMs per server > * JDK 1.4.2_05 > * Application server is Oracle 9.0.3 AS > * one database server (Oracle) > Reporter: Henrik Nyberg > Assignee: Bela Ban > Fix For: 1.2.1 > Attachments: JBCACHE-93.zip, SimpleCacheTest.java, SimpleCacheTest.java > > > JBossCache does not properly garbage collect objects that are replicated > through the network and that replaces an already existing object in the local > cache. The existing local cache object that is being replaced by the remote > PUT is not garbage collected. > We have four caches in our setup, A, B, C, D. We describe the status for > cache A after the first iteration using an object sA1. We PUT that object > after every iteration into A using the same key ksA. > Iteration 1: > A updates status -> A(ksA,sA1) replicated to => B(ksA, sA1), C(ksA, sA1), > D(ksA, sA1) > Iteration 2: > A updates status -> A(ksA,sA2) replicated to => B(ksA, sA2), C(ksA, sA2), > D(ksA, sA2) > After iteration 2 the local object A(ksA,sA1) is probably correctly gc:ed, > since if we run this test in local mode the cache works reliably. The remote > objects B(ksA, sA1), C(ksA, sA1), D(ksA, sA1) however seem not to be > correctly gc:ed since the cache constantly eats memory when running in > replicated mode. > If we turn off the status replication, i.e. the repeated PUT of the status > object A(ksA, saN), the cache works like a charm. The only difference between > the two test cases is the PUT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: How do I include the News module in my index page?
Hi, you should consider this : http://www.jboss.org/index.html?module=bb&op=viewtopic&t=53733 For examples see http://enfanceetcroissance.com see http://gitesprovence.fr.to View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867784#3867784 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867784 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-64) Scope (13)
[ http://jira.jboss.com/jira/browse/JBPM-64?page=history ] Juan Cantu updated JBPM-64: --- Description: Implement fault, compensation and event handling as specified in ws-bpel 2.0 Environment: Version: 3.0 DR 1 Component: BPEL > Scope (13) > -- > > Key: JBPM-64 > URL: http://jira.jboss.com/jira/browse/JBPM-64 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: 3.0 DR 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > > > Implement fault, compensation and event handling as specified in ws-bpel 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.831 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050224092858Lbuild.831 BUILD COMPLETE - build.831Date of build: 02/24/2005 09:28:58Time to build: 47 minutes 24 secondsLast changed: 02/24/2005 09:10:24Last log entry: replaced children HashMap with ConcurrentReaderHashMap Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.70modifiedbelabancache/src/main/org/jboss/cache/Node.javareplaced children HashMap with ConcurrentReaderHashMap1.17modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/eviction/LRUPolicyUnitTestCase.javano message
[JBoss-dev] [Design of JBoss Portal] - Portal Build
I've downloaded the modules jboss-portal and jboss-portal-thirdparty. When I've runned build.bat from jboss-portal/build directory the following error ocurred: file:C:/Projetos/workspace/jboss-portal-2.0/format/build.xml:113: Could not create task or type of type: jflex. what i've done wrong? what else do I have to do to build portal? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867778#3867778 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867778 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-94) Incorrect synchronization between threads (CreateIfNotExistsInterceptor and LockInterceptor)
[ http://jira.jboss.com/jira/browse/JBCACHE-94?page=history ] Bela Ban resolved JBCACHE-94: - Resolution: Done Involved changing synchronization of put() and evict()/remove() methods in CreateIfNotExistsInterceptor > Incorrect synchronization between threads (CreateIfNotExistsInterceptor and > LockInterceptor) > > > Key: JBCACHE-94 > URL: http://jira.jboss.com/jira/browse/JBCACHE-94 > Project: JBoss Cache > Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Blocker > Fix For: 1.2.1 > > > Example (assumes RPE-READ (R/W lock) semantics): > - TX1 does a put(/a/b/c) > - TX1 acquires lock1 in CreateIfNotExistsInterceptor > - TX1 creates /a/b (RL) and /a/b/c (WL), locking those nodes > - TX2 does a put(/a/b/c/d), waits on CINE-Int > - TX1 releases lock1 > - TX2 acquires lock1 and blocks on lock acquisition for /a/b/c (WL-ed by TX1) > - TX1 does a remove(/a/b/c, key) > - TX1 blocks on lock1 (held by TX2) > - TX2 times out, rolls back changes and releases lock1 > - TX1 acquires lock1, makes the change, commits TX and releases all locks > SOLUTION: we need to fine-grained synchronization in > CreateIfNotExistsInterceptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Portlet title always null
I tried to use a newer version of the portlet integration library and now it works like a charm:-) Thx View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867766#3867766 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867766 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.398 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050224083728Lbuild.398 BUILD COMPLETE - build.398Date of build: 02/24/2005 08:37:28Time to build: 19 minutes 23 secondsLast changed: 02/24/2005 08:08:27Last log entry: typo Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.40.2.14modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javatypo
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: Problem with XML editor on migration to 3.1M5
Yes Eclipse seem to have either added som xerces code or changed how classes are loadedthe short version: JBossIDE does not work with 3.1M5a. We are trying to adjust for their changes and hope to release a version that works with the latest version soonbut cant promise anything yet ,) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867763#3867763 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867763 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-901) setting unpackWars as false didn't work
[ http://jira.jboss.com/jira/browse/JBAS-901?page=comments#action_12315758 ] Remy Maucherat commented on JBAS-901: - AFAIK, leaving wars packed only works when the Tomcat classloader is used (useJBossWebLoader set to false). > setting unpackWars as false didn't work > --- > > Key: JBAS-901 > URL: http://jira.jboss.com/jira/browse/JBAS-901 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assignee: Remy Maucherat > > > SourceForge Submitter: shyamvs . > using jboss 323 release version jdk 1.4.2_03 linux RH > 8.0 2.4.18-14 > When I set the unpackWars flag as false then i get a > ClassNotFoundException. When is set true I am not > getting this exception. > 10:43:37:929]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: Test > Print=unpack wars==false| > [10:43:38:345]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:38,282 INFO [EmbeddedTomcatService] deploy, > ctxPath=/servervm-test, > warUrl=file:/advent1/reg/WebNMS5_Test_ant1.6/build/servervm-test.war > | > [10:43:39:281]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,266 INFO [Engine] > SingleSignOnContextConfig[/servervm-test]: Added > certificates -> request attribute Valve > | > [10:43:39:384]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,299 WARN [EmbeddedTomcatService] Unable to > invoke setDelegate on class > loader:[EMAIL PROTECTED] > | > [10:43:39:385]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,299 INFO [Engine] > StandardManager[/servervm-test]: Seeding random number > generator class java.security.SecureRandom > | > [10:43:39:385]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,300 INFO [Engine] > StandardManager[/servervm-test]: Seeding of random > number generator has been completed > | > [10:43:39:385]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,301 INFO [Engine] > StandardWrapper[/servervm-test:default]: Loading > container servlet default > | > [10:43:39:386]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,301 INFO [Engine] > StandardWrapper[/servervm-test:invoker]: Loading > container servlet invoker > | > [10:43:39:489]|[03-01-2004]|[SYSOUT]|[INFO]|[13]|: > 10:43:39,388 INFO [MainDeployer] Deployed package: > file:/advent1/reg/WebNMS5_Test_ant1.6/build/servervm-test.war > | > [10:43:39:837]|[03-01-2004]|[SYSOUT]|[INFO]|[14]|: > 10:43:39,748 INFO [Engine] > StandardWrapper[/servervm-test:JUnitEETestServlet]: > Marking servlet JUnitEETestServlet as unavailable > | > [10:43:39:838]|[03-01-2004]|[SYSOUT]|[INFO]|[14]|: > 10:43:39,751 ERROR [Engine] > StandardWrapperValve[JUnitEETestServlet]: Allocate > exception for servlet JUnitEETestServlet > javax.servlet.ServletException: Wrapper cannot find > servlet class org.junitee.servlet.JUnitEEServlet or a > class it depends on > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:891) > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) > at > org.jboss.web.tomcat.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:220) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) > at > org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) > at > org.jboss.web.tomcat.tc4.statistics.ContainerStatsValve.invoke(ContainerStatsValve.java:76) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) > at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) > at > org.a
[JBoss-dev] jboss-4.0 build.397 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050224075035Lbuild.397 BUILD COMPLETE - build.397Date of build: 02/24/2005 07:50:35Time to build: 18 minutes 59 secondsLast changed: 02/24/2005 07:31:03Last log entry: Prevent NPE in addDocument when element NS URI is null Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.1.1.1.4.5modifiedtdieslerjaxrpc/src/main/org/apache/axis/message/SOAPBodyAxisImpl.javaPrevent NPE in addDocument when element NS URI is null1.3.2.1modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javamoved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - java.lang.LinkageError: loader constraints violated when lin
Hello, I have an application that deploys fine when doens't have the jboss-app.xml file in the ear. I need to isolate the ear and I can't modify the jboss configuration. When I put this file (jboss-app.xml) in the ear, I get the error: 12:52:10,571 INFO [TomcatDeployer] deploy, ctxPath=/integratorweb, warUrl=file:/C:/java/jboss-3.2.5_teste/server/default/tmp/deploy/tmp15210workflow.ear-contents/integrator.war/ 12:52:11,946 ERROR [Engine] StandardContext[/integratorweb]StandardWrapper.Throwable java.lang.LinkageError: loader constraints violated when linking org/xml/sax/ErrorHandler class at com.cpqd.util.presentation.menu.MenuLoader.init(MenuLoader.java:60) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1019) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3991) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4335) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:109) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5412) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:109) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:286) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:70) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:306) at org.jboss.web.WebModule.startModule(WebModule.java:62) at org.jboss.web.WebModule.startService(WebModule.java:40) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837) at $Proxy17.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:367) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy31.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebC
[JBoss-dev] [Design of JBoss Portal] - Re: JBossPortal and AOP
sounds like you should use SSO instead. how is logon performed on your other application ? does it use servlet container authentication ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867751#3867751 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867751 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.830 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050224064017Lbuild.830 BUILD COMPLETE - build.830Date of build: 02/24/2005 06:40:17Time to build: 17 minutes 20 secondsLast changed: 02/24/2005 06:28:26Last log entry: added one more map entry representation Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (43)1.2modifiedloubyanskytestsuite/src/resources/xml/newmetadata.xmladded one more map entry representation1.11modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javaupdated new metadata testcase1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/Immutable.javaimprovements in java value binding1.17modifiedloubyanskycommon/src/main/org/jboss/xml/binding/MappingObjectModelFactory.javaimprovements in java value binding1.9modifiedloubyanskycommon/src/main/org/jboss/xml/binding/MetadataDrivenObjectModelFactory.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/ArrayValue.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/ClassBinding.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/CollectionItemBinding.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/CollectionValue.javaimprovements in java value binding1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/CursorImpl.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/FieldBinding.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaFieldValue.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValue.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValueBinding.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValueFactory.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValueFactoryImpl.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapEntryBinding.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapEntryValue.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapKeyBinding.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapValue.javaimprovements in java value binding1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapValueBinding.javaimprovements in java value binding1.3modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/ObjectModelFactoryImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlAttribute.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlAttributeImpl.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlComplexType.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlComplexTypeImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDataContent.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDataContentImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocument.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentFactory.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentFactoryImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlElement.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlElementImpl.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlNamespace.javaimprovements in java value binding1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlNamespaceImpl.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlSimpleType.javaimprovements in java value binding1.2deletedloubyanskycommon/src/main/org/jboss/xml/bind
[JBoss-dev] [Design of JBoss Portal] - Re: shared state between HttpSession and PortletSession
no they don't share it, they only have the jessionid in common. that enables to have the same session wether you access the webapp by request dispatch from the portal or directly for the browser. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867735#3867735 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867735 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBossXB] - Re: MappingObjectModel and Polymorphism
Another iteration of the API is committed and the testcase is updated. Maps are now supported if there is a wrapping element bound to map. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867734#3867734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867734 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of the JBoss Web Container] - Where is SecurityAssociationValve configured?
I tried to figure out how the container-managed security is handled when the tomcat is running inside the jboss. 1. I found the source code for SecurityAssociationValve. However, I did not see any where this valve is configured in the server.xml and it is clearly used in JBossSecurityMgrRealm | Principal caller = (Principal) SecurityAssociationValve.userPrincipal.get(); | if (caller == null && username == null && credentials == null) | return null; Can anyone tell me where this caller data in the SecurityAssociationValve is set? 2. The tomcat has some internal value such as the security check valve? Is this valve called before my custom valve such as FormAuthValve? Where is the valve sequence is specified? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867729#3867729 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867729 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.829 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050224055244Lbuild.829 BUILD COMPLETE - build.829Date of build: 02/24/2005 05:52:44Time to build: 15 minutes 59 secondsLast changed: 02/24/2005 05:23:10Last log entry: no message Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (10)1.8modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/local/TxDeadlockUnitTestCase.javano message1.34modifiedbelabancache/src/main/org/jboss/cache/lock/IdentityLock.javaexposed UpgradeException (not rethrown as TimeoutException, or LockingException)1.69modifiedbelabancache/src/main/org/jboss/cache/Node.javaexposed UpgradeException (not rethrown as TimeoutException, or LockingException)1.13modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/generic/IdentityLockUnitTestCase.javaadded handling for InterruptedException1.12modifiedbelabancache/src/main/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javaimplemented fine-grained synchronization between put() and remove()/evict() methods1.43modifiedbelabancache/src/main/org/jboss/cache/aop/TreeCacheAop.javaadded handling of InterruptedException1.68modifiedbelabancache/src/main/org/jboss/cache/Node.javaadded InterruptedException to signature1.33modifiedbelabancache/src/main/org/jboss/cache/lock/IdentityLock.javaadded InterruptedException to signature1.19modifiedbelabancache/src/main/org/jboss/cache/interceptors/LockInterceptor.javaadded InterruptedException to signature1.7modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/local/TxDeadlockUnitTestCase.javano message
[JBoss-dev] [Nukes Development] - Nukes, struts and EJBÂs
I implementing an application MVC, where I use: -NUKES - View -STRUTS - Controller -BEANÂs - Model My problem is, can I use a block already definitely (loginBlock.java) as View, and struts as controller? Can I do it? My intention is to create a portal of access to users using blocks Nukes but with another model MVC different from Nukes Thank you in advance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867727#3867727 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867727 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050224042836 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 02/24/2005 04:28:36Time to build: 22 minutes 26 secondsLast changed: 02/24/2005 04:17:13Last log entry: implemented fine-grained synchronization between put() and remove()/evict() methods Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (6)1.12modifiedbelabancache/src/main/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javaimplemented fine-grained synchronization between put() and remove()/evict() methods1.43modifiedbelabancache/src/main/org/jboss/cache/aop/TreeCacheAop.javaadded handling of InterruptedException1.68modifiedbelabancache/src/main/org/jboss/cache/Node.javaadded InterruptedException to signature1.33modifiedbelabancache/src/main/org/jboss/cache/lock/IdentityLock.javaadded InterruptedException to signature1.19modifiedbelabancache/src/main/org/jboss/cache/interceptors/LockInterceptor.javaadded InterruptedException to signature1.7modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/local/TxDeadlockUnitTestCase.javano message
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-97) ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer waiting to upgrade lock
ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer waiting to upgrade lock - Key: JBCACHE-97 URL: http://jira.jboss.com/jira/browse/JBCACHE-97 Project: JBoss Cache Type: Bug Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.1 TxDeadlockUnitTestCase has 2 methods that show the following stack traces: testMoreThanOneUpgrader: Upgrader#0: get(/a/b/c) Upgrader#1: get(/a/b/c) main: locks: /a (read owners=[:2, :1]) /b (read owners=[:2, :1]) /c (read owners=[:2, :1]) Upgrader#0: put(/a/b/c) Upgrader#1: put(/a/b/c) Upgrader#1: org.jboss.cache.lock.LockingException: acquireWriteLock(): lock upgrade failed for /a/b/c (caller=:2); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock) Upgrader#0: org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [:2] Write lock owner: null (caller=:1) org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [:2] Write lock owner: null (caller=:1) at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:155) at org.jboss.cache.Node.acquireWriteLock(Node.java:448) at org.jboss.cache.Node.acquire(Node.java:417) at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:199) at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:144) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.CreateIfNotExistsInterceptor.invoke(CreateIfNotExistsInterceptor.java:145) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:2998) at org.jboss.cache.TreeCache.put(TreeCache.java:1657) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$MyUpgrader._run(TxDeadlockUnitTestCase.java:346) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) and testConcurrentUpgrade(): MyThread#1: get(/a/b/c) MyThread#2: get(/a/b/c) MyThread#2: done, locks: /a (read owners=[:2]) /b (read owners=[:2]) /c (read owners=[:2]) MyThread#1: done, locks: /a (read owners=[:2, :1]) /b (read owners=[:2, :1]) /c (read owners=[:2, :1]) MyThread#2: put(/a/b/c) MyThread#1: put(/a/b/c) MyThread#1: org.jboss.cache.lock.LockingException: acquireWriteLock(): lock upgrade failed for /a/b/c (caller=:1); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock) MyThread#2: org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [:1] Write lock owner: null (caller=:2) org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [:1] Write lock owner: null (caller=:2) at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:155) at org.jboss.cache.Node.acquireWriteLock(Node.java:448) at org.jboss.cache.Node.acquire(Node.java:417) at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:199) at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:144) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.CreateIfNotExistsInterceptor.invoke(CreateIfNotExistsInterceptor.java:145) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:2998) at org.jboss.cache.TreeCache.put(TreeCache.java:1657) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$MyThread._run(TxDeadlockUnitTestCase.java:317) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/s
[JBoss-dev] [JBoss JIRA] Created: (JBWEB-13) Tomcat5: StandardContext getConfigBase tries to create a directory
Tomcat5: StandardContext getConfigBase tries to create a directory
--
Key: JBWEB-13
URL: http://jira.jboss.com/jira/browse/JBWEB-13
Project: JBoss Web
Type: Bug
Components: Tomcat
Versions: JBossWeb-4.0.1
Environment: JBoss 4.0.1sp1, Solaris8
Reporter: Roland R?z
Assigned to: Remy Maucherat
Priority: Minor
Hello,
Just to explain you the circumstances why this request has arised.
I try to secure JBoss with a java security policy. The policy should prevent
somebody from writing in the JBoss installation directory.
For this reason I set a File permission that allows only reading on the
JBoss installation directory.
It looks like this
grant {
permission java.io.FilePermission "${jboss.home.dir}/-", "read";
...
};
Now when I start JBoss and deploy a War file I receive the following
AccessPermissionException
Caused by: java.security.AccessControlException: access denied
(java.io.FilePermission
/opt/jboss/4.0.1/server/myserver/conf/jboss.web/localhost write)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
at java.io.File.mkdir(File.java:1097)
at java.io.File.mkdirs(File.java:1122)
at
org.apache.catalina.core.StandardContext.getConfigBase(StandardContext.java:4858)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4071)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121)
at
org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:805)
at org.a
pache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
... 152 more
The method that creates the Exception looks like this
private File org.apache.catalina.core.StandardContext#getConfigBase()
{
File configBase = new File(System.getProperty("catalina.base"), "conf");
if(!configBase.exists())
return null;
Container container = this;
Container host = null;
Container engine = null;
for(; container != null; container = container.getParent())
{
if(container instanceof Host)
host = container;
if(container instanceof Engine)
engine = container;
}
if(engine != null)
configBase = new File(configBase, engine.getName());
if(host != null)
configBase = new File(configBase, host.getName());
configBase.mkdirs(); // here it crashes
return configBase;
}
JBoss sets the saveConfig Flag of the StandardContext to false.
(see TomcatDeployer#performDeployInternal)
configBase.mkdirs() should only be invoked if the saveConfig Flag is set to
true.
Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1515) Update the AOP binaries and remove the aop modules
Update the AOP binaries and remove the aop modules -- Key: JBAS-1515 URL: http://jira.jboss.com/jira/browse/JBAS-1515 Project: JBoss Application Server Type: Task Components: Build System Versions: JBossAS-4.0.2RC1 Reporter: Scott M Stark Fix For: JBossAS-4.0.2 Final The aop deployer seems to no longer be built from the aspects module source. The current 4.0 branch binaries do not include the recent security changes and needs to be updated. If binaries are being used as the integration mechanism, there is no reason to be including obsolete source modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
