[JBoss JIRA] Created: (JBAS-6562) Context entries don't work as explained in tomcat docs.
by Vicky Kak (JIRA)
Context entries don't work as explained in tomcat docs.
-------------------------------------------------------
Key: JBAS-6562
URL: https://jira.jboss.org/jira/browse/JBAS-6562
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Vicky Kak
Assignee: Vicky Kak
Fix For: JBossAS-5.1.0.Beta1, JBossAS-4.2.4.GA
The documentation about the context configuration in Tomcat does not work in JbossAS deployments.
I have just spend some time looking at the related code at
http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_4_2/tomcat/src/mai...
Here is the code snippet
****************************************************************
private String findConfig(URL warURL) throws IOException
{
String result = null;
// See if the warUrl is a dir or a file
File warFile = new File(warURL.getFile());
if (warURL.getProtocol().equals("file") && warFile.isDirectory() == true)
{
File webDD = new File(warFile, CONTEXT_CONFIG_FILE);
if (webDD.exists() == true) result = webDD.getAbsolutePath();
}
else
{
ZipFile zipFile = new ZipFile(warFile);
ZipEntry entry = zipFile.getEntry(CONTEXT_CONFIG_FILE);
if (entry != null)
{
InputStream zipIS = zipFile.getInputStream(entry);
byte[] buffer = new byte[512];
int bytes;
result = warFile.getAbsolutePath() + "-context.xml";
FileOutputStream fos = new FileOutputStream(result);
while ((bytes = zipIS.read(buffer)) > 0)
{
fos.write(buffer, 0, bytes);
}
zipIS.close();
fos.close();
}
zipFile.close();
}
return result;
}
****************************************************************
This code needs to be modified in such a way that it uses these configurations
**************************************************************************************
1. in the $CATALINA_HOME/conf/[enginename]/[hostname]/context.xml.default file: the Context element information will be loaded by all webapps of that host
2. in individual files (with a ".xml" extension) in the $CATALINA_HOME/conf/[enginename]/[hostname]/ directory. The name of the file (less the .xml) extension will be used as the context path. Multi-level context paths may be defined using #, e.g. context#path.xml. The default web application may be defined by using a file called ROOT.xml.
3. if the previous file was not found for this application, in an individual file at /META-INF/context.xml inside the application files
inside a Host element in the main conf/server.xml
**************************************************************************************
The point[3] is already rejected earlier by Scott, here is the related jira
https://jira.jboss.org/jira/browse/JBAS-2290
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBRULES-2246) Several random MVEL related errors while using drools.
by Rajesh Nair (JIRA)
Several random MVEL related errors while using drools.
------------------------------------------------------
Key: JBRULES-2246
URL: https://jira.jboss.org/jira/browse/JBRULES-2246
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.7
Environment: Unix
Reporter: Rajesh Nair
Assignee: Mark Proctor
We are getting several MVEL related exceptions while running a batch program that is multi-threaded. Sometimes the bean name gets corrupted and it complains about ClassNotFoundException. Sometimes, it complains that a specific property is not found. When we restart the batch program, the problem goes away. Is there a way to fix this? We are using JDK 1.5 and the mvel jar version is mvel-1.3.1-java1.4.jar. If this jar will not work with drools 4.0.7, please suggest the upgrade path. In the worst case, we can use Java dialect. However, all our rules are created via the BRMS. So, how do you force the BRMS to use Java dialect?
Thanks,
Rajesh
Here is a sample stacktrace.
rg.drools.RuntimeDroolsException: Exception executing predicate eval( (field1 + field2 + field3) <= 0 )
at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:216)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:137)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:318)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:162)
at org.drools.reteoo.Rete.assertObject(Rete.java:175)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:192)
at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:911)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:883)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:684)
at org.drools.reteoo.ReteooStatelessSession.executeWithResults(ReteooStatelessSession.java:198)
at walgreens.pbs.ruleengine.worker.RulesetExecutor.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:803)
Caused by: org.mvel.PropertyAccessException: unable to resolve property: field2 (where field2 is the name of the property)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.compileAccessor(ASMAccessorOptimizer.java:267)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.optimizeAccessor(ASMAccessorOptimizer.java:163)
at org.mvel.ASTNode.getReducedValueAccelerated(ASTNode.java:186)
at org.mvel.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:21)
at org.mvel.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:21)
at org.mvel.ExecutableAccessor.getValue(ExecutableAccessor.java:45)
at org.mvel.ast.Substatement.getReducedValueAccelerated(Substatement.java:24)
at org.mvel.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:21)
at org.mvel.MVELRuntime.execute(MVELRuntime.java:90)
at org.mvel.CompiledExpression.getValue(CompiledExpression.java:111)
at org.mvel.MVEL.executeExpression(MVEL.java:235)
at org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:45)
at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:209)
... 14 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.loadClass(ASMAccessorOptimizer.java:1003)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer._initializeAccessor(ASMAccessorOptimizer.java:206)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.compileAccessor(ASMAccessorOptimizer.java:264)
... 26 more
Caused by: java.lang.LinkageError: ASMAccessorImpl_19543133401249413540370
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:223)
at java.lang.ClassLoader.defineClass(ClassLoader.java:162)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Updated: (JBAS-7205) Redeployment of session doesn't acquire session state
by Shelly McGowan (JIRA)
[ https://jira.jboss.org/browse/JBAS-7205?page=com.atlassian.jira.plugin.sy... ]
Shelly McGowan updated JBAS-7205:
---------------------------------
Fix Version/s: TBD
(was: 6.0.0.Final)
> Redeployment of session doesn't acquire session state
> -----------------------------------------------------
>
> Key: JBAS-7205
> URL: https://jira.jboss.org/browse/JBAS-7205
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Bela Ban
> Assignee: Scott Marlow
> Fix For: TBD
>
> Attachments: web.war
>
>
> Here's the scenario:
> - Start instances A and B in a cluster, the webapp is session.war (*exploded* WAR)
> - Create a session, say its session-id is sessionId.A
> - Go to A and remove the WAR, e.g. cd ./deploy ; mv session.war session.war.bak
> - Refresh the session. It fails over to B: sessionId.B
> - Go back to A (/deploy dir) and mv session.war.bak session.war
> - Go to B and remove the session
> ==> The session will fail back to A, but the session's data is gone !
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBAS-7782) EJB3 over IIOP on JBOSS5.1.0 GA
by e t (JIRA)
EJB3 over IIOP on JBOSS5.1.0 GA
-------------------------------
Key: JBAS-7782
URL: https://jira.jboss.org/jira/browse/JBAS-7782
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers, EJB3
Affects Versions: JBossAS-5.1.0.GA
Environment: JBossAS 5.1.0 GA
JBoss-6.0.0.20100216-M2
Windows XP Professional
SUN jdk1.6.0_16
Reporter: e t
Assignee: Ales Justin
I encourter a problem at EJB3 over IIOP.
I deploy the EJB module on JBoss 5.1.0 GA,and run the JBoss server by "run.bat -c all". It is succeed to deploy and boot the JBoss server. But I found it is no any relate naming service under JBoss CorbaNaming.It seems that the deployer no bind the EJB3 Bussiness Remote Interface to the Corbanaming service.
My java code is under:
EJB3 Bussiness Remote:
package com.olm.ejb3;
public interface HW {
public String helloworld();
}
EJB3 Bean Implement:
package com.olm.ejb3;
@javax.ejb.Remote(HW.class)
@javax.ejb.Stateless(name="HWBean")
public class HWBean implements HW{
public String helloworld() {
return "hello,world";
}
}
Deployment Descriptor(jboss.xml):
<jboss>
<enterprise-beans>
<session>
<ejb-name>HWBean</ejb-name>
<configuration-name>Standard Stateless SessionBean</configuration-name>
<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>iiop</invoker-proxy-binding-name>
</invoker>
</invoker-bindings>
</session>
</enterprise-beans>
</jboss>
what can I do for the next?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBRULES-1820) Exception: Input stream is not explicitly closed.
by Kris Nuttycombe (JIRA)
Exception: Input stream is not explicitly closed.
-------------------------------------------------
Key: JBRULES-1820
URL: https://jira.jboss.org/jira/browse/JBRULES-1820
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 4.0.7
Environment: Java 6, Linux
Reporter: Kris Nuttycombe
Assignee: Mark Proctor
I am using the Drools PackageBuilder to create business rules from a file. While the rules appear to function correctly, when the JVM which runs the application shuts down, an exception is thrown due to the forced closing of an unclosed stream. It looks from the stack trace like the Drools code is opening a stream using ClassLoader.getResourceAsStream which is then left unclosed and is forced close at JVM shutdown.
On application server shutdown, I receive the following exception. This appears to be the result of an unclosed input stream for a system resource used by the Drools compiler.
[#|2008-10-23T09:55:09.527-0600|WARNING|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=22;_ThreadName=RMI TCP Connection(1197)-10.97.100.58;_RequestID=341c51d9-08de-4e67-9da1-c57375cb5f35;|Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.EJBClassLoader$SentinelInputStream.<init>(EJBClassLoader.java:1169)
at com.sun.enterprise.loader.EJBClassLoader$InternalJarURLConnection.getInputStream(EJBClassLoader.java:1262)
at java.net.URL.openStream(URL.java:1009)
at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1161)
at com.sun.enterprise.loader.EJBClassLoader.getResourceAsStream(EJBClassLoader.java:799)
at org.drools.rule.PackageCompilationData$PackageClassLoader.getResourceAsStream(PackageCompilationData.java:384)
at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.isPackage(EclipseJavaCompiler.java:280)
at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:222)
at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:204)
at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:97)
at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:43)
at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveUnresolvedType(BinaryTypeBinding.java:138)
at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superclass(BinaryTypeBinding.java:936)
at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.getExactMethod(BinaryTypeBinding.java:724)
at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.getExactMethod(BinaryTypeBinding.java:727)
at org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMethod(Scope.java:761)
at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:2002)
at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:384)
at org.eclipse.jdt.internal.compiler.ast.ReturnStatement.resolve(ReturnStatement.java:220)
at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:432)
at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:190)
at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:403)
at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1047)
at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1094)
at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:353)
at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:596)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:411)
at org.drools.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJavaCompiler.java:351)
at org.drools.commons.jci.compilers.AbstractJavaCompiler.compile(AbstractJavaCompiler.java:51)
at org.drools.rule.builder.dialect.java.JavaDialect.compileAll(JavaDialect.java:342)
at org.drools.compiler.DialectRegistry.compileAll(DialectRegistry.java:60)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:308)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:167)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBAS-6983) Error configuring property: sessionIdAlphabet for WarDeployer
by Manuel Aznar Perez (JIRA)
Error configuring property: sessionIdAlphabet for WarDeployer
-------------------------------------------------------------
Key: JBAS-6983
URL: https://jira.jboss.org/jira/browse/JBAS-6983
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.0.1.GA
Environment: JBoss 5.0.1.GA or JBoss 5.1.0.GA
Reporter: Manuel Aznar Perez
Assignee: Remy Maucherat
Priority: Minor
At "server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml" when i uncomment "<property name="sessionIdAlphabet">" and run JBoss. Launch exception:
2009-05-28 08:34:34,670 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Configured: name=WarDeployer state=Instantiated
java.lang.RuntimeException: Error configuring property: sessionIdAlphabet for WarDeployer
at org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:112)
at org.jboss.kernel.plugins.dependency.ConfigureAction.setAttributes(ConfigureAction.java:85)
at org.jboss.kernel.plugins.dependency.ConfigureAction.installActionInternal(ConfigureAction.java:44)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
That is because don't have "jboss-web-service.jar" in deployer.
This jar is in "deploy/jbossweb.sar".
This is fixed copy jar file to deployer directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months