[JBoss JIRA] Created: (JBAS-4215) Need to externalize the web container class loader to use outside of the web container
by Scott M Stark (JIRA)
Need to externalize the web container class loader to use outside of the web container
--------------------------------------------------------------------------------------
Key: JBAS-4215
URL: http://jira.jboss.com/jira/browse/JBAS-4215
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Deployment services, Web (Tomcat) service
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
We need a WarClassLoadingDeployer that allows for the creation of the web container class loader during the DeploymentUnit processing based on the class loading metadata. In the absence of jboss UCL or osgi bundle metadata, this should create the standard tomcat war first class loader. Not having this at the DeploymentUnit level does not allow other deployers to interact with war deployments properly.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBAS-3883) JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF
by Amit Kasher (JIRA)
JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF
---------------------------------------------------------
Key: JBAS-3883
URL: http://jira.jboss.com/jira/browse/JBAS-3883
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading, Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.Beta1
Reporter: Amit Kasher
Assigned To: Scott M Stark
An EAR file that deploys well in JBoss4.0.5 fails to deploy in JBoss5.0Beta1 when initializing the web application (NoClassDefFound).
However, this ear does deploy well when taking the required jar files (the WAR dependencies) out of the EAR and placing them inside the .war/WEB-INF/lib folder, as well as removing the "Class-Path" entry in the WAR's MANIFEST.MF.
Documents stating, as far as I understand, the existence of the requirement that this should work are here:
http://java.sun.com/j2ee/verified/packaging.html
... as well as in the spec ... (http://jcp.org/en/jsr/detail?id=244) in section EE.8.2.1 (Bundled Libraries) starting in page 155.
It's related to Tomcat's classpath (or to the classpath augmentation JBoss performs, where there were probably recent changes to support resource injection into web clients, like servlets). This is why I indicated Tomcat as an additional affected component.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBAS-4306) Invalid invoker mbean names in standardjboss.xml
by Scott M Stark (JIRA)
Invalid invoker mbean names in standardjboss.xml
------------------------------------------------
Key: JBAS-4306
URL: http://jira.jboss.com/jira/browse/JBAS-4306
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
The following invoker-proxy-binding is useless in terms of defining the invoker-mbean such that it can be used as a ejb container dependency:
<invoker-proxy-binding>
<name>message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<CreateJBossMQDestination>false</CreateJBossMQDestination>
<!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
<MinimumSize>1</MinimumSize>
<MaximumSize>15</MaximumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
Either there should be an mbean representing the state of the default invoker, or the mdb invoker config specified in another way such that dependencies can be configured.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBAS-4491) Server startup failure with JDK 1.6
by Greg Zoller (JIRA)
Server startup failure with JDK 1.6
-----------------------------------
Key: JBAS-4491
URL: http://jira.jboss.com/jira/browse/JBAS-4491
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.0.Beta2
Environment: Windows
Reporter: Greg Zoller
An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup. Not sure the whys or wherefores but am pretty sure its not a good thing.
13:24:13,467 INFO [ServerImpl] Starting JBoss (Microcontainer)...
13:24:13,467 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
13:24:13,467 INFO [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2
13:24:13,467 INFO [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/
13:24:13,467 INFO [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/
13:24:13,467 INFO [ServerImpl] Patch URL: null
13:24:13,467 INFO [ServerImpl] Server Name: default
13:24:13,467 INFO [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default
13:24:13,467 INFO [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/
13:24:13,467 INFO [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data
13:24:13,467 INFO [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp
13:24:13,467 INFO [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/
13:24:13,467 INFO [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/
13:24:13,467 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
13:24:13,499 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
13:24:14,831 INFO [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default
13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:522)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
... 35 more
13:24:16,258 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
13:24:16,258 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
13:24:16,258 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
13:24:16,305 INFO [JMXKernel] Legacy JMX core initialized
Failed to boot JBoss:
java.lang.RuntimeException: Exception during Bootstrap
at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:522)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
VFSBootstrapScanner
-> DeploymentFilter{Configured:**ERROR**}
VFSDeployerScanner
-> DeploymentFilter{Configured:**ERROR**}
VFSDeploymentScanner
-> DeploymentFilter{Configured:**ERROR**}
*** CONTEXTS IN ERROR: Name -> Error
DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
... 5 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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBPORTAL-1801) CMS content shows incorrect 'Created' and 'Modified' timestamps
by Martin Putz (JIRA)
CMS content shows incorrect 'Created' and 'Modified' timestamps
---------------------------------------------------------------
Key: JBPORTAL-1801
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1801
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Reporter: Martin Putz
Assigned To: Sohil Shah
A given file (index.html) in CMS is displayed like:
index.html Created=T1, Modified=T1
- index.html - Version 1.0, Created=T1, Modified=T1
If this file is updated, a new version (2.0) is created and after that the display looks like
index.html Created=T1, Modified=T1
- index.html - Version 1.0, Created=T1, Modified=T1
- index.html - Version 2.0, Created=T2, Modified=T2
One would expect to see the Modified=T2 date of the latest Version 2.0 on the top level entry of this content:
index.html Created=T1, Modified=*T2*
- index.html - Version 1.0, Created=T1, Modified=T1
- index.html - Version 2.0, Created=T2, Modified=T2
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBRULES-1329) RuleBase.removeRule() prevents other rules from being applied
by James Sparrow (JIRA)
RuleBase.removeRule() prevents other rules from being applied
-------------------------------------------------------------
Key: JBRULES-1329
URL: http://jira.jboss.com/jira/browse/JBRULES-1329
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.3
Environment: JDK 1.6.0
Reporter: James Sparrow
After adding a package containing two rules and then removing one of the rules, the remaining rule is no longer activated when a matching fact is asserted. Following is a unit test displaying this behavior, along with its .drl file.
import java.io.InputStreamReader;
import java.io.Reader;
import java.util.ArrayList;
import java.util.List;
import java.util.Properties;
import junit.framework.TestCase;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.StatelessSession;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.compiler.PackageBuilderConfiguration;
import org.drools.event.AfterActivationFiredEvent;
import org.drools.event.DefaultAgendaEventListener;
import org.drools.rule.Package;
import org.drools.rule.Rule;
public class DroolsRemoveRuleTest extends TestCase
{
/**
* Create a new RuleBase from a package containing two rules, "Hello" and
* "Goodbye". First verify both rules are applied as expected. Then remove
* the "Hello" rule and verify the "Hello" rule is no longer applied, but
* the "Goodbye" rule is applied. In Drools 4.0.3, the removal of the
* "Hello" rule causes the "Goodbye" rule to no longer be applied.
*/
public void testRemoveRule() throws Exception
{
Reader removeRuleSource = new InputStreamReader(getClass().getResourceAsStream("testRemoveRule.drl"));
Properties props = new Properties();
props.setProperty("drools.dialect.java.compiler", "JANINO");
PackageBuilderConfiguration cfg = new PackageBuilderConfiguration(props);
PackageBuilder packageBuilder = new PackageBuilder(cfg);
packageBuilder.addPackageFromDrl(removeRuleSource);
assertFalse(packageBuilder.hasErrors());
Package pkg = packageBuilder.getPackage();
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage(pkg);
Message hello = new Message();
hello.setName("Chuck");
hello.setType(Type.HELLO);
Message goodbye = new Message();
goodbye.setName("Charles");
goodbye.setType(Type.GOODBYE);
StatelessSession session = ruleBase.newStatelessSession();
FiredRulesListener listener = new FiredRulesListener();
session.addEventListener(listener);
session.execute(hello);
assertEquals(1, listener.getFiredRules().size());
assertEquals("Hello", listener.getFiredRules().get(0).getName());
session = ruleBase.newStatelessSession();
listener = new FiredRulesListener();
session.addEventListener(listener);
session.execute(goodbye);
assertEquals(1, listener.getFiredRules().size());
assertEquals("Goodbye", listener.getFiredRules().get(0).getName());
ruleBase.removeRule(pkg.getName(), "Hello");
session = ruleBase.newStatelessSession();
listener = new FiredRulesListener();
session.addEventListener(listener);
session.execute(hello);
assertEquals(0, listener.getFiredRules().size());
session = ruleBase.newStatelessSession();
listener = new FiredRulesListener();
session.addEventListener(listener);
session.execute(goodbye);
// The following assertion currently fails
assertEquals(1, listener.getFiredRules().size());
assertEquals("Goodbye", listener.getFiredRules().get(0).getName());
}
public static class FiredRulesListener extends DefaultAgendaEventListener
{
List<Rule> firedRules = new ArrayList<Rule>();
public List<Rule> getFiredRules()
{
return this.firedRules;
}
@Override
public void afterActivationFired(AfterActivationFiredEvent event, WorkingMemory workingMemory)
{
Rule rule = event.getActivation().getRule();
this.firedRules.add(rule);
}
}
public static enum Type
{
HELLO, GOODBYE
};
public static class Message
{
private Type type = null;
private String name = null;
public Type getType()
{
return this.type;
}
public void setType(Type type)
{
this.type = type;
}
public String getName()
{
return this.name;
}
public void setName(String name)
{
this.name = name;
}
}
}
package test
import DroolsRemoveRuleTest.Message
import DroolsRemoveRuleTest.Type
rule "Hello"
dialect "java"
when
Message( type == Type.HELLO, name : name )
then
System.out.println("Hello " + name);
end
rule "Goodbye"
dialect "java"
when
Message( type == Type.GOODBYE, name : name )
then
System.out.println("Goodbye " + name);
end
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months