July 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Scoping of war/jar file embedded in sar service archives

by alesj

Cause for reopening JBDEPLOY-59. I commited deployers/build/pom.xml to use the latest Classloading snapshot. The ManifestClassLoaderUnitTestCase is failing due to ordering issue. With the new Classloading code that tries to resolve ClassLoadingSpace, this piece causes child modules to declare its vfs roots before parent modules. org.jboss.classloading.spi.dependency.Domain: | // Skip the classloader space checking when it is import all | if (module.isImportAll() == false) | { | ClassLoadingSpace space = new ClassLoadingSpace(); | space.join(module); // starting here! | } | In the test top-level.jar is import-all == true, where top-levelsub.jar is import-all == false. 1) space.join(module) calls module.determinePackageNames 2) module.getCapabilities calls module.determineCapabilities 3) module.determineCapabilities in VFSDeploymentClassLoaderPolicyModule uses determineVFSRoots And since parent hasn't been yet examined, this code is never called | Set<VirtualFile> parentClassPath = parent.getAttachment(VFS_CLASS_PATH, Set.class); | if (parentClassPath != null) | { | if (log.isTraceEnabled()) | { | for (VirtualFile parentFile : parentClassPath) | { | if (classPath.contains(parentFile)) | log.trace(unit + " weeding duplicate entry " + parentFile + " from classpath already in parent " + parent); | } | } | classPath.removeAll(parentClassPath); | } | leaving the sub's classpath intact. Hence it loads class from it's own classloader. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165497#4165497 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165497

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Many dispatchers on the client side

by timfox

Currently each remoting connection on the client side has it's own packet dispatcher, whereas on the server side a single global dispatcher is used for all requests. I was wondering if there was any reason for having one per connection, rather than one global one on the client side? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165483#4165483 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165483

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - ManagedObjectAttachmentsImpl::transientManagedObjects not tr

by alesj

Looking at this | public class ManagedObjectAttachmentsImpl extends PredeterminedManagedObjectAttachmentsImpl implements ManagedObjectAttachments | { | /** The serialVersionUID */ | private static final long serialVersionUID = -195530143173768763L; | | /** The transient managed objects */ | private MutableAttachments transientManagedObjects = AttachmentsFactory.createMutableAttachments(); | | public MutableAttachments getTransientManagedObjects() | { | return transientManagedObjects; | } | | public void readExternal(ObjectInput in) throws IOException, ClassNotFoundException | { | super.readExternal(in); | transientManagedObjects = (MutableAttachments) in.readObject(); | } | | /** | * @serialData attachments | * @param out the output | * @throws IOException for any error | */ | public void writeExternal(ObjectOutput out) throws IOException | { | super.writeExternal(out); | out.writeObject(transientManagedObjects); | } | } | what's transient about it, except for the name? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165482#4165482 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165482

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Producer hangs after 20M sent

by timfox

Sounds like something to do with producer flow control. What's your producer window size set to? What happens if you disable producer flow control or change the window size? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165481#4165481 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165481

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Producer hangs after 20M sent

by ataylor

Ive come across what i think may be a bug in JBM 2. If you run the perf sender and set the message size to 64k, the producer stops sending after 32000 messages, if the message size is 32k it stops sending after 64000 messages, and so forth. So basically it looks like it stops working after 20M of messages. Can any of you guys reproduce this problem, if you can i'll raise a JIRA. NB pinging needs to be disabled to send lge messages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165478#4165478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165478

17 years, 8 months

1
0
0 / 0

[Design of Clustering on JBoss] - Java Concurrency in Practice annotations

by bstansberry＠jboss.com

FYI, I've added the net.jcip/jcip-annotations jar to the AS trunk thirdparty. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165461#4165461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165461

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by bstansberry＠jboss.com

Yes, I think it's worth trying. I'd thought there might have been a problem in JBC 1.4.x that would have made invalidation not work properly, which is why I said don't bother. But I just had a look at the JBC code and it's looks OK, so go for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165456#4165456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165456

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by prabhat.jha＠jboss.com

I dug further into code for your question regarding query caching. Though the flag is enabled in hibernate configuration for all modules, query cache is only enabled programatically (query.setCacheable(true)) for CMS. Following your previous response and as per http://wiki.jboss.org/auth/wiki/JBossCacheHibernate, does it mean that INVALIDATION_SYNC would be worth trying when CMS is not used? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165453#4165453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165453

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by bstansberry＠jboss.com

Yes, REPL_SYNC is needed if you use query caching. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165450#4165450 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165450

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - [WARNING] ...jboss-as-aspects:pom... is invalid.

by charles.crouch＠jboss.com

During the 'install' phase of building my project I'm getting the following warning when I have a dependency on jboss-as-profileservice:5.0.0-SNAPSHOT .... [WARNING] POM for 'org.jboss.jbossas:jboss-as-aspects:pom:5.0.0-SNAPSHOT:provided' is invalid. It will be ignored for artifa ct resolution. Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-aspects at Artifact [org.jboss.jbossas: jboss-as-aspects:pom:5.0.0-SNAPSHOT:provided] ... Anything we should be worried about? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165444#4165444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165444

17 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2008