[JBoss JIRA] (JBRULES-3234) NPE while creating activations if a fact is modified by multiple prior consequences
by Jamie Shaw (Created) (JIRA)
NPE while creating activations if a fact is modified by multiple prior consequences
------------------------------------------------------------------------------------
Key: JBRULES-3234
URL: https://issues.jboss.org/browse/JBRULES-3234
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert), drools-core (flow)
Affects Versions: 5.3.0.CR1
Reporter: Jamie Shaw
Assignee: Mark Proctor
I receive an NPE when attempting to modify a fact in a rule consequence if multiple prior rules have modified the same fact.
It appears to involve the interaction between 3 rules, each of which is in a different agenda group. For background, this is a fraud detection application. Under certain conditions, we need to look up additional customer information. Some rules are run to determine whether the lookup is required and then another rule actually does the lookup. In this case:
Rule 021 says if the order is small, set the lookup flag on the customer fact to false
Rule 042B says if the order is from a 'bad' country, set the lookup flag on the customer fact to true
Rule 022 says if the lookup flag is true, do the lookup, set the results on the customer flag and set the lookup flag on the customer fact
If rule 021 fires alone, then 022 does not fire and all is well.
If rule 042B fires alone, then 022 fires and all is well.
If 021 fires to turn off the lookup AND 042B fires to turn on the lookup, then 022 gets and NPE.
As Edson suspected, the item is null and the 'rule' variable points to rule 021.
Each rule involved is in a different agenda group.
This works in 5.2.0.Final, but breaks in 5.3.0.CR1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (AS7-1189) When starting up more then one instance by accident can the error messages be better currently they are kinda long
by Jim Tyrrell (JIRA)
When starting up more then one instance by accident can the error messages be better currently they are kinda long
------------------------------------------------------------------------------------------------------------------
Key: AS7-1189
URL: https://issues.jboss.org/browse/AS7-1189
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jim Tyrrell
I do like the fact that address in use do not leave a running instance laying around, I would much rather see one error message rather then pages and pages. To our users this is very overwhelming, especially when they come from our competitors. Also how does this kind of error not have an error code associated with it.
How many other exceptions do not have error codes?
Jim-Tyrrells-MacBook-Pro-2:bin jimtyrrell$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1
JAVA: java
JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
=========================================================================
08:38:37,622 INFO [org.jboss.modules] JBoss Modules version 1.0.0.CR4
08:38:37,772 INFO [org.jboss.msc] JBoss MSC version 1.0.0.CR2
08:38:37,812 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" starting
08:38:38,328 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
08:38:38,333 INFO [org.jboss.as.logging] Removing bootstrap log handlers
08:38:38,343 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
08:38:38,413 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
08:38:38,420 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
08:38:38,425 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
08:38:38,436 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
08:38:38,442 INFO [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 3.2.0.Beta2
08:38:38,448 INFO [org.xnio] (MSC service thread 1-10) XNIO Version 3.0.0.Beta3
08:38:38,457 INFO [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.0.0.Beta3
08:38:38,606 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
08:38:38,616 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-10) Starting remote JMX connector
08:38:38,618 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
08:38:38,618 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC00001: Failed to start service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:98)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [:1.6.0_24]
at org.xnio.nio.NioXnio.createTcpServer(NioXnio.java:162)
at org.xnio.Xnio.createStreamServer(Xnio.java:230)
at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:162)
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:93)
... 5 more
08:38:38,623 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the URLStreamHandlerFactory
08:38:38,624 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the ContentHandlerFactory
08:38:38,625 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:89)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:47)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:37)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:126)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:99)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:86)
... 5 more
08:38:38,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
java.net.BindException: Address already in use
at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:106)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310) [:1.6.0_24]
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218) [:1.6.0_24]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393) [:1.6.0_24]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129) [:1.6.0_24]
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190) [:1.6.0_24]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) [:1.6.0_24]
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68) [:1.6.0_24]
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222) [:1.6.0_24]
at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:97)
... 5 more
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24]
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24]
at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24]
at org.jboss.as.network.ManagedServerSocketBinding.bind(ManagedServerSocketBinding.java:73)
at org.jboss.as.network.SocketBinding.createServerSocket(SocketBinding.java:149)
at org.jboss.as.jmx.JMXConnectorService$JMXServerSocketFactory.createServerSocket(JMXConnectorService.java:194)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649) [:1.6.0_24]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299) [:1.6.0_24]
... 13 more
08:38:38,634 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190)
at org.apache.catalina.connector.Connector.init(Connector.java:976)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
08:38:38,636 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.initialize: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.catalina.connector.Connector.init(Connector.java:978)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
08:38:38,638 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error starting endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:1020)
at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:218)
at org.apache.catalina.connector.Connector.start(Connector.java:1051)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
08:38:38,639 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.start: LifecycleException: service.getName(): "jboss.web"; Protocol handler start failed: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.catalina.connector.Connector.start(Connector.java:1058)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
08:38:38,675 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
08:38:38,700 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) Bound data source [java:jboss/datasources/ExampleDS]
08:38:38,920 INFO [org.jboss.as.deployment] (MSC service thread 1-10) Started FileSystemDeploymentService for directory /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1/standalone/deployments
08:38:39,130 INFO [org.jboss.as.controller] (Controller Boot Thread) Service status report
Services which failed to start:
service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
java.net.BindException: Address already in use
08:38:39,134 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.CR1 "White Rabbit" started (with errors) in 1668ms - Started 87 of 146 services (4 services failed or missing dependencies, 55 services are passive or on-demand)
^C08:39:03,929 INFO [org.jboss.as.logging] Restored bootstrap log handlers
08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
08:39:03,934 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" stopped in 4ms
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-4319) Admin console: Modcluster ProxyList field cannot be set back to empty.
by Simeon Pinder (JIRA)
Simeon Pinder created AS7-4319:
----------------------------------
Summary: Admin console: Modcluster ProxyList field cannot be set back to empty.
Key: AS7-4319
URL: https://issues.jboss.org/browse/AS7-4319
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Environment: Admin console standalone or domain mode.
Reporter: Simeon Pinder
Assignee: Heiko Braun
0)Start AS7 standalone with profile that supports HA to enable ModCluster
1)Log into admin console AS7.1.1.Final
2)Navigate to Profile > Web > Modcluster and select the 'Proxies' tab.
3)If empty(at default) then set ProxyList to 'some_value:8888' and save. Now edit the information again and attempt to set the field to "". You will be unable to save.
This means that if you have a modcluster configuration that is incorrect or not configured anymore that you cannot disable it via the console. On startup you will get nasty exception unless you manually clear.
UI field should not be required to be non-empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-4374) whoami operation failing in domain mode but still returning a response
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4374:
-------------------------------------
Summary: whoami operation failing in domain mode but still returning a response
Key: AS7-4374
URL: https://issues.jboss.org/browse/AS7-4374
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 7.1.2.Final
The whoami operation is both failing and returning a response in domain mode: -
[domain@192.168.1.158:9999 /] :whoami
{
"outcome" => "failed",
"result" => {"identity" => {
"username" => "mac",
"realm" => "ManagementRealm"
}},
"failure-description" => {"host-failure-descriptions" => [("mac" => "JBAS015249: No security context has been established.")]},
"rolled-back" => true
}
[domain@192.168.1.158:9999 /]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBRULES-2590) Maven build fails in Linux with LANG=fr_FR.utf8
by Jean-Marc Vanel (JIRA)
Maven build fails in Linux with LANG=fr_FR.utf8
------------------------------------------------
Key: JBRULES-2590
URL: https://jira.jboss.org/browse/JBRULES-2590
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: % uname -a
Linux jmv-desktop 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux
% java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Reporter: Jean-Marc Vanel
Assignee: Mark Proctor
With sources from Subversion, making a Maven build on drools-trunk gives 3 errors :
Tests in error:
testDate(org.drools.base.FieldFactoryTest)
testString(org.drools.base.mvel.MVELCalendarCoercionTest)
testString(org.drools.base.mvel.MVELDateCoercionTest)
Tests run: 578, Failures: 0, Errors: 3, Skipped: 1
[ERROR] BUILD FAILURE
However this runs fine:
LANG=en mvn install
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months