[JBoss JIRA] Created: (JBMESSAGING-1848) java.lang.IllegalStateException: There is already a delivery set for auto ack
by philippe pinheiro (JIRA)
java.lang.IllegalStateException: There is already a delivery set for auto ack
-----------------------------------------------------------------------------
Key: JBMESSAGING-1848
URL: https://issues.jboss.org/browse/JBMESSAGING-1848
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.3.GA
Reporter: philippe pinheiro
If I run mutiple Threads (30) inside JBoss sharing a common QueueSession created in Session.AUTO_ACKNOWLEDGE mode
for sending and receiving messages from a Queue, after a while I get this exception :
java.lang.IllegalStateException: There is already a delivery set for auto ack 23964772 xa: false
2011-02-18 11:52:02,501 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.state.SessionState.setAutoAckInfo(SessionState.java:408)
2011-02-18 11:52:02,501 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:268)
2011-02-18 11:52:02,501 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handlePreDeliver_4634459.invoke(SessionAspect_z_handlePreDeliver_4634459.java)
2011-02-18 11:52:02,501 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,501 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
2011-02-18 11:52:02,502 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
2011-02-18 11:52:02,502 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,502 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java)
2011-02-18 11:52:02,502 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.container.ClientConsumer.receive(ClientConsumer.java:550)
2011-02-18 11:52:02,502 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.container.ConsumerAspect.handleReceive(ConsumerAspect.java:194)
2011-02-18 11:52:02,503 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect_z_handleReceive_4634459.invoke(ConsumerAspect_z_handleReceive_4634459.java)
2011-02-18 11:52:02,503 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,503 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
2011-02-18 11:52:02,503 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
2011-02-18 11:52:02,504 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,504 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.delegate.ClientConsumerDelegate.receive(ClientConsumerDelegate.java)
2011-02-18 11:52:02,504 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.jms.client.JBossMessageConsumer.receive(JBossMessageConsumer.java:81)
2011-02-18 11:52:02,504 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at integra.jms.reportfactory.ReportFactoryJMSSoapClient.getResult(ReportFactoryJMSSoapClient.java:80)
2011-02-18 11:52:02,504 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at integra.jms.reportfactory.ReportFactoryJMSRestClient.execute(ReportFactoryJMSRestClient.java:175)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at integra.jms.reportfactory.ReportFactoryJMSCommonClient.execute(ReportFactoryJMSCommonClient.java:22)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at integra.test.ClientSingleton.executeReport(ClientSingleton.java:40)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at integra.test.TestCallBean.test(TestCallBean.java:20)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at sun.reflect.GeneratedMethodAccessor293.invoke(Unknown Source)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
2011-02-18 11:52:02,505 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at java.lang.reflect.Method.invoke(Unknown Source)
2011-02-18 11:52:02,506 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
2011-02-18 11:52:02,506 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
2011-02-18 11:52:02,506 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
2011-02-18 11:52:02,506 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
2011-02-18 11:52:02,506 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at java.lang.reflect.Method.invoke(Unknown Source)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,507 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
2011-02-18 11:52:02,508 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_4634459.invoke(InvocationContextInterceptor_z_fillMethod_4634459.java)
2011-02-18 11:52:02,508 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,508 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
2011-02-18 11:52:02,508 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_4634459.invoke(InvocationContextInterceptor_z_setup_4634459.java)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,509 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
2011-02-18 11:52:02,510 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,510 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
2011-02-18 11:52:02,510 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,510 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
2011-02-18 11:52:02,510 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,511 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
2011-02-18 11:52:02,511 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
2011-02-18 11:52:02,511 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,511 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
2011-02-18 11:52:02,511 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
2011-02-18 11:52:02,512 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,513 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
2011-02-18 11:52:02,513 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,513 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
2011-02-18 11:52:02,513 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
2011-02-18 11:52:02,513 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:421)
2011-02-18 11:52:02,514 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53)
2011-02-18 11:52:02,514 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91)
2011-02-18 11:52:02,514 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
2011-02-18 11:52:02,514 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
2011-02-18 11:52:02,514 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
2011-02-18 11:52:02,515 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
2011-02-18 11:52:02,515 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
2011-02-18 11:52:02,515 ERROR [STDERR] (WorkerThread#24[10.20.0.75:50388]) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
It seems to be a problem of aspect in SessionAspect.handlePreDeliver and SessionAspect.handlePostDeliver
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (EJBTHREE-1429) SFSB replication soak testing
by Brian Stansberry (JIRA)
SFSB replication soak testing
-----------------------------
Key: EJBTHREE-1429
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1429
Project: EJB 3.0
Issue Type: Task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 5.0.0.CR2
Long running tests of SFSB replication under heavy load.
Should include:
1) Letting a significant percentage of sessions passivate and later activate.
2) Letting a significant percentage of sessions expire due to time out.
3) Invalidating remaining sessions after a while (i.e. don't use any sessions for the life of test; all get used and replaced after a while).
4) Perhaps, a low (say 1/1000) probability of failover.
--
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
13 years, 4 months
[JBoss JIRA] Created: (JBAS-8894) Resource adapter deployment fails when an authentication-mechanism-type is defined
by Shelly McGowan (JIRA)
Resource adapter deployment fails when an authentication-mechanism-type is defined
----------------------------------------------------------------------------------
Key: JBAS-8894
URL: https://issues.jboss.org/browse/JBAS-8894
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
The the authentication-mechanism element of the ra.xml is used to specify the authentication mechanism supported by the resource adapter. If the authentication-mechanism-type is defined the deployment fails to PARSE
<authentication-mechanism>
<authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
<credential-interface>javax.resource.security.PasswordCredential</credential-interface>
</authentication-mechanism>
19:10:19,387 ERROR [org.jboss.msc] (pool-2-thread-3) MSC-00001: Failed to start service jboss.deployment.unit.jbosstestadapter.rar.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.jbosstestadapter.rar.PARSE: Failed to process phase PARSE of deployment "jbosstestadapter.rar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112)
at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse service xml ["/content/jbosstestadapter.rar/META-INF/ra.xml"]
at org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:92)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
... 4 more
Caused by: java.lang.IllegalArgumentException: fullQualifiedName should be one of javax.resource.spi.security.PasswordCredential; org.ietf.jgss.GSSCredential;javax.resource.spi.security.GenericCredential
at org.jboss.jca.common.api.metadata.ra.CredentialInterfaceEnum.forName(CredentialInterfaceEnum.java:89)
at org.jboss.jca.common.metadata.ra.RaParser.parseAuthenticationMechanism(RaParser.java:1129)
at org.jboss.jca.common.metadata.ra.RaParser.parseResourceAdapter10(RaParser.java:631)
at org.jboss.jca.common.metadata.ra.RaParser.parseConnector10(RaParser.java:245)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:160)
at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:102)
at org.jboss.as.connector.deployers.processors.RaDeploymentParsingProcessor.deploy(RaDeploymentParsingProcessor.java:81)
The deployment does succeed if the authentication-mechanism element is empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JGRP-1294) XSD validation fails with AUTH protocol
by Manuel Dominguez Sarmiento (JIRA)
XSD validation fails with AUTH protocol
---------------------------------------
Key: JGRP-1294
URL: https://issues.jboss.org/browse/JGRP-1294
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12
Reporter: Manuel Dominguez Sarmiento
Assignee: Bela Ban
Priority: Minor
The config properties for the AUTH protocol depend on the actual auth_class being used. However this results in XSD validation failing, since the auth_class implementation properties are not defined.
We fixed our local XSD to define the props. required by MD5Token. I'm not sure how this should be handled generically, since end users might define their own auth_classes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBRULES-2904) KnowledgeAgent unsubscribes monitors, doesn't resubscribe them
by Laird Nelson (JIRA)
KnowledgeAgent unsubscribes monitors, doesn't resubscribe them
--------------------------------------------------------------
Key: JBRULES-2904
URL: https://issues.jboss.org/browse/JBRULES-2904
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: Laird Nelson
Assignee: Mark Proctor
A KnowledgeAgent set up to monitor a .drl file, and set to perform incremental builds, will correctly monitor that file for changes.
When a change to that file, however, results in a DRL syntax exception (or any other KnowledgeBuilder errors), the KnowledgeAgent no longer monitors the resource for changes.
This means that a typo in the file effectively stops the KnowledgeAgent from ever seeing that file again. Consequently, an error in the DRL file requires a restart to whatever server is using the KnowledgeAgent.
Esteban and I have found that the error is related to lines 337 and following of KnowledgeAgentImpl.java. Here is a snippet from one of his emails to me:
"The problem seems to be related to the lines you mentioned. When a resource is modified, all its knowledgeDefinition->resource are cleared and reconstructed later. I don't see any reason to unsubscribe the listener though. So the call to Set<KnowledgeDefinition> definitions = this.removeResourceMapping(resource, true); should be Set<KnowledgeDefinition> definitions = this.removeResourceMapping(resource, false);
"That means: remove all the mappings but don't unsubscribe me (the kagent) as a listener."
Further background can be found at http://drools-java-rules-engine.46999.n3.nabble.com/Drools-5-1-What-happe...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBAS-8879) webservices.xml creates a web context with the jar's name
by Ståle Pedersen (JIRA)
webservices.xml creates a web context with the jar's name
---------------------------------------------------------
Key: JBAS-8879
URL: https://issues.jboss.org/browse/JBAS-8879
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 6.0.0.Final
Reporter: Ståle Pedersen
Assignee: Richard Opalka
Fix For: 6.1.0
Deploying the SpecjEnterprise2010 benchmark on JBoss6-Final result in a deployment exception reporting that the war application is already installed. The .ear contains:
META-INF/
META-INF/MANIFEST.MF
META-INF/jboss-app.xml
specj-hornetq-jms.xml
lib/
META-INF/application.xml
jboss-mysql-ds.xml
lib/generated-ws-buyer.jar
mdb-service.xml
specj.jar
specj.war
supplier.war
The specj.jar contains a webservice.xml file and it seems to create a web context with the same name as the jar which causes the specj.war to fail to deploy. This worked on JBoss5.
Im not allowed to attach the benchmark, but ill attach the webservices.xml file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months