[JBoss JIRA] Created: (JBMESSAGING-1891) Null point exception while committing a transaction
by Tom Ross (JIRA)
Null point exception while committing a transaction
---------------------------------------------------
Key: JBMESSAGING-1891
URL: https://issues.jboss.org/browse/JBMESSAGING-1891
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.8.SP1
Environment: JBoss EAP 5.1.1
Reporter: Tom Ross
Assignee: Yong Hao Gao
The following exception gets throw when committing a transaction:
12:02:53,098 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.commitexception] [com.arjuna.ats.internal.jta.resources.arjunacore.commitexception] XAResourceRecord.topLevelCommit caught: java.lang.NullPointerException
java.lang.NullPointerException
at org.jboss.jms.tx.ResourceManager.commit(ResourceManager.java:375)
at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:255)
at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.commit(MessagingXAResourceWrapper.java:126)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelCommit(XAResourceRecord.java:568)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doCommit(BasicAction.java:3155)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doCommit(BasicAction.java:3070)
at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Commit(BasicAction.java:2131)
at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.replayPhase2(RecoverAtomicAction.java:85)
at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecoveryModule.java:181)
at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:294)
at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:128)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:799)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412)
--
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-3201) Sliding windows - Rule is being fired event when LHS is false
by eyal rahamim (JIRA)
Sliding windows - Rule is being fired event when LHS is false
-------------------------------------------------------------
Key: JBRULES-3201
URL: https://issues.jboss.org/browse/JBRULES-3201
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.3.0.Beta1
Environment: Linux
Reporter: eyal rahamim
Assignee: Mark Proctor
I have a rule that accumulate fact into sliding window. When the count get to a certain threshold the rule should be activated. After the window time is over, I expect that the rule will not fired anymore. The counter of the fact is report as 0, but still the rule is being executed.
drl :
package com.sample;
import com.sample.WindowLength.FactTest;
declare FactTest
@role( event )
end
rule "A500 : test"
when
// count devices per tag id
$counter : Number( intValue >= 2 ) from accumulate (
$d : FactTest() over window:time(1m), count($d))
then
System.out.println("A500: Rule is fired, count = " + $counter + " *********");
end
scenario:
ksession.insert(new FactTest());
ksession.fireAllRules();
ksession.insert(new FactTest());
ksession.fireAllRules();
ksession.insert(new FactTest());
ksession.fireAllRules();
SessionPseudoClock clock = ksession.getSessionClock();
clock.advanceTime(1, TimeUnit.MINUTES );
ksession.fireAllRules();
Result:
A500: Rule is fired, count = 2 *********
A500: Rule is fired, count = 3 *********
A500: Rule is fired, count = 0 *********
--
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: (JBMESSAGING-1462) Message expiration is not correctly managed
by Ivan (JIRA)
Message expiration is not correctly managed
-------------------------------------------
Key: JBMESSAGING-1462
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1462
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.1.GA
Environment: JBAS 5.0GA, JBM 1.4.1GA, persistence on Oracle 10i
Reporter: Ivan
Assignee: Tim Fox
1) A topic is created
2) A durable subscriber is created fro the topic
3) A message is sent on the topic
4) The durable subscriber pulls the message from the topic ( receive() ) but don't ack
5) The durable subscriber is closed, subscriber session.unsuscribe(name) is called but an exception is thrown and then the subsciber session is closed.
As result of this a message, expired, with DELIVERY_COUNT = 1 will remain on the database forever.
--
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, 4 months
[JBoss JIRA] Created: (AS7-1046) AS7 gives NPE when jboss-web.xml is missing from WAR
by Nathan Kopp (JIRA)
AS7 gives NPE when jboss-web.xml is missing from WAR
----------------------------------------------------
Key: AS7-1046
URL: https://issues.jboss.org/browse/AS7-1046
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: Open To Community
Environment: Windows XP, JDK 1.6
Reporter: Nathan Kopp
Attachments: jaxws-test.war
I'm trying to deploy a simple WAR (nearly empty, with a single JAX-WS web service) using a fairly recent snapshot of JBoss AS7. If I do not include jboss-web.xml in the WEB-INF folder, I get the following NPE when deploying to standalone\deployment
12:17:25,356 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."jaxws-test.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-test.war".INSTALL: Failed to process phase INSTALL of deployment "jaxws-test.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_10]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_10]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_10]
Caused by: java.lang.NullPointerException
at org.jboss.as.webservices.util.WebMetaDataHelper.getServlets(WebMetaDataHelper.java:130)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createServlets(WebMetaDataCreator.java:173)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createWebAppDescriptor(WebMetaDataCreator.java:109)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.create(WebMetaDataCreator.java:93)
at org.jboss.as.webservices.tomcat.WebMetaDataCreatingDeploymentAspect.start(WebMetaDataCreatingDeploymentAspect.java:48)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:78)
at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:42)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 4 more
When I add a very simple jboss-web.xml file (containing only the context-root tag), the deployment succeeds.
Attached is the WAR file.
--
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: (AS7-1216) NonexistentConversationException when attempting to restore a long-running conversation on AS 7 CR1 and not beta3
by Drew Stockdreher (JIRA)
NonexistentConversationException when attempting to restore a long-running conversation on AS 7 CR1 and not beta3
-----------------------------------------------------------------------------------------------------------------
Key: AS7-1216
URL: https://issues.jboss.org/browse/AS7-1216
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.0.0.CR1
Environment: Windows XP 32 bit, JBoss AS 7 CR1 and Firefox 5
Reporter: Drew Stockdreher
A simple web application which starts a long-running conversation via an
<f:event type="preRenderView" listener="#{bean.startConvo}"/> tag.
Selecting from a selectOneMenuList makes an ajax request which was working on the beta3 release of AS 7 is no longer working with the following stacktrace. This does however still work in IE 7 and Chrome 12 on both beta3 and CR1 releases.
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) org.jboss.weld.context.NonexistentConversationException: WELD-000321 No conversation found to restore for id 1
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:108)
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:84)
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111)
10:36:11,275 ERROR [stderr] (http--127.0.0.1-8080-1) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
10:36:11,291 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
10:36:11,306 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
10:36:11,322 ERROR [stderr] (http--127.0.0.1-8080-1) at java.lang.Thread.run(Thread.java:662)
--
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] Commented: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on AS7-1702:
------------------------------------
hmmm.. yea, didn't think of that. Probably need to open up for a remoteAddress option or similar in configuration to override the autodiscover.
> Accept <any-address/> in Jboss AS7 configuration
> ------------------------------------------------
>
> Key: AS7-1702
> URL: https://issues.jboss.org/browse/AS7-1702
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.0.1.Final
> Environment: JBoss AS 7.0.1.Final
> Reporter: Alexandre Gattiker
>
> ERROR ArquillianServiceDeployer - Cannot deploy arquillian service
> java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asList(ModelValue.java:128)
> at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096)
> at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185)
> at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177)
> at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148)
> at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90)
> at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98)
> at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58)
> After changing the JBoss AS 7 configuration from:
> <interface name="public">
> <inet-address value="127.0.0.1"/>
> </interface>
> to:
> <interface name="public">
> <any-address/>
> </interface>
> Presumed cause:
> in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar:
> return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString();
--
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: (AS7-1392) Description in scripts to secure the api wrong
by Heiko Rupp (JIRA)
Description in scripts to secure the api wrong
----------------------------------------------
Key: AS7-1392
URL: https://issues.jboss.org/browse/AS7-1392
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
Script says to execute
snert:~/downloads/jboss-as-web-7.0.0.Final hrupp$ bin/jboss-admin.sh -c --file=scripts/secure-standalone-mgmt.cli
File /Users/hrupp/Downloads/jboss-as-web-7.0.0.Final/scripts/secure-standalone-mgmt.cli doesn't exist.
which fails.
Also the description in the file fails to mention that the server must be started for this (or alternatively to start the server, but as it a cli script, this is probably not expected).
--
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: (AS7-1462) JVM version should be added to the list of jvm attributes exposed to management interface
by Simeon Pinder (JIRA)
JVM version should be added to the list of jvm attributes exposed to management interface
-----------------------------------------------------------------------------------------
Key: AS7-1462
URL: https://issues.jboss.org/browse/AS7-1462
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Environment: CLI management interface.
Reporter: Simeon Pinder
Assignee: Brian Stansberry
"jvm" => {"default" => {
"agent-lib" => undefined,
"agent-path" => undefined,
"env-classpath-ignored" => undefined,
"environment-variables" => undefined,
"heap-size" => "64m",
"java-agent" => undefined,
"java-home" => undefined,
"jvm-options" => undefined,
"max-heap-size" => "512m",
"max-permgen-size" => undefined,
"permgen-size" => undefined,
"stack-size" => undefined,
"type" => undefined
}}
JVM version should be added to the list of jvm attributes exposed to management interface. Most of the elements are focused on the runtime settings for the JVM, but the specific JVM version is also very important for pruposes of patching, upgrades and for describing a platform upon which many other components depend.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months