[JBoss JIRA] (AS7-2023) Discovery and Broadcast configuration is broken for HornetQ
by Andy Taylor (Created) (JIRA)
Discovery and Broadcast configuration is broken for HornetQ
-----------------------------------------------------------
Key: AS7-2023
URL: https://issues.jboss.org/browse/AS7-2023
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.Alpha1
Reporter: Andy Taylor
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
this is because there is a transformation done from the String representation to an inet address and when its transformed back in DiscoveryGroupAdd:createDiscoveryGroupConfiguration(...) it uses the tostring() on the address so for instance 237.7.7.7 ends up as /237.7.7.7. so
final String groupAddress = socketBinding.getMulticastAddress().toString();
should actually be
final String groupAddress = socketBinding.getMulticastAddress().getHostAddress();
same for the bind address and one BroadcastGroupAdd
--
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
12 years, 6 months
[JBoss JIRA] Created: (AS7-1601) Cannot deploy war bundles in JBoss AS 7.0.0 nor 7.0.1
by Tommy Svensson (JIRA)
Cannot deploy war bundles in JBoss AS 7.0.0 nor 7.0.1
-----------------------------------------------------
Key: AS7-1601
URL: https://issues.jboss.org/browse/AS7-1601
Project: Application Server 7
Issue Type: Bug
Components: OSGi, Web
Affects Versions: 7.0.1.Final, 7.0.0.Final
Environment: Mac OS X 10.7 (Lion)
Reporter: Tommy Svensson
Assignee: Thomas Diesler
Impossible to deploy OSGi war bundle. The same war bundle deploys perfectly in eclipse Virgo server. I get the following when I try to deploy my war:
14:37:46,065 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) Starting deployment of "inputstream:aps-admin-web-1.0.0.war"
14:37:47,129 INFO [org.jboss.as.jpa] (MSC service thread 1-5) added javax.persistence.api dependency to inputstream:aps-admin-web-1.0.0.war
14:37:47,131 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."inputstream:aps-admin-web-1.0.0.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."inputstream:aps-admin-web-1.0.0.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "inputstream:aps-admin-web-1.0.0.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
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_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:72)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
14:37:47,134 INFO [org.jboss.as.server.controller] (pool-3-thread-1) Deployment of "inputstream:aps-admin-web-1.0.0.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"inputstream:aps-admin-web-1.0.0.war\""}}
14:37:47,143 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) Stopped deployment inputstream:aps-admin-web-1.0.0.war in 8ms
14:37:47,147 WARN [/] (Background Install /var/folders/3l/2n_xhr7s6ksc_bddrvl1hthm0000gn/T/install6377037636958039788.tmp) %bundles.pluginTitle: Cannot install or update bundle from /var/folders/3l/2n_xhr7s6ksc_bddrvl1hthm0000gn/T/install6377037636958039788.tmp: org.osgi.framework.BundleException: Cannot deploy bundle: [aps-admin-web:1.0.0,location=inputstream:aps-admin-web-1.0.0.war]
at org.jboss.as.osgi.service.BundleInstallProviderIntegration.installBundle(BundleInstallProviderIntegration.java:120)
at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundle(AbstractBundleContext.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundleInternal(AbstractBundleContext.java:189)
at org.jboss.osgi.framework.internal.AbstractBundleContext.installBundle(AbstractBundleContext.java:125)
at org.apache.felix.webconsole.internal.core.InstallHelper.doRun(InstallHelper.java:54) [InstallHelper.class:]
at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.doRun(BaseUpdateInstallHelper.java:89) [BaseUpdateInstallHelper.class:]
at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.run(BaseUpdateInstallHelper.java:121) [BaseUpdateInstallHelper.class:]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: java.lang.Exception: {"Failed services" => {"jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"inputstream:aps-admin-web-1.0.0.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"inputstream:aps-admin-web-1.0.0.war\""}}
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:99)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:88)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:70)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
at org.jboss.as.osgi.service.BundleInstallProviderIntegration.executeDeploymentPlan(BundleInstallProviderIntegration.java:144)
at org.jboss.as.osgi.service.BundleInstallProviderIntegration.installBundle(BundleInstallProviderIntegration.java:113)
... 7 more
The bundle manifest looks like this:
Manifest-Version: 1.0
Embed-Directory: lib
Bundle-ClassPath: WEB-INF/classes
Built-By: tommy
Tool: Bnd-1.43.0
Bundle-Name: APS Administration Web
Created-By: Apache Maven Bundle Plugin
Web-ContextPath: apsadminweb
Build-Jdk: 1.6.0_26
Bundle-Version: 1.0.0
Bnd-LastModified: 1313841491925
Bundle-ManifestVersion: 2
Bundle-Activator: osgi.aps.apsadminweb.APSAdminWebActivator
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0
Bundle-Description: APS Administration Web
Bundle-SymbolicName: aps-admin-web
Import-Package: org.osgi.framework;version="[1.5,2)",org.osgi.service.
log;version="[1.3,2)",org.osgi.util.tracker;version="[1.4,2)",se.bilt
more.osgi.aps.api.core.tools;version="[1.0,2)"
Embed-Dependency: *;scope=compile
All that is included in the war in addition to the activator is and index.jsp that looks like this:
----------------------------------
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<h1>Hello World!</h1>
</body>
</html>
----------------------------------
In other words, this is an extremely simple war bundle that I made for testing war bundle deploy. The activator does nothing yet. It has empty start(...) and stop(...) methods. Therefore I find the following line from the stack trace above interesting:
org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:72)
It is a simple war with a single jsp page, so why is it trying to do ejb3 depployment ? And also it is not the full server I'm running, only the web profile, which as far as I know should not contain ejb3.
All I have done in the configuration (standalone) is to change start level from 1 to 3, and change osgi from lazy to eager.
As I said above this war file deploys perfectly in the Virgo server and I can bring up http://localhost:8080/apsadminweb in the browser and get the "Hello World!". Thereby I feel that my simple war is correct.
As another test I tried to deploy one of the war bundles that came with the Virgo server and it resulted in exactly the same stack trace as above.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-3117) Compiling two functions fails
by Wolfgang Laun (JIRA)
Compiling two functions fails
------------------------------
Key: JBRULES-3117
URL: https://issues.jboss.org/browse/JBRULES-3117
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.1.Final
Compiling these two function together fails:
function boolean isOutOfRange( Object value, int lower ){
return true;
}
function boolean isNotContainedInt( Object object, int[] values ){
return true;
}
[ isNotContainedInt : unable to resolve type while building function ]
If the first one is removed, or its arguments are reduced, the remainder compiles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1582) Debug configuration in domain.sh is incorrect
by Brian Stansberry (JIRA)
Debug configuration in domain.sh is incorrect
---------------------------------------------
Key: AS7-1582
URL: https://issues.jboss.org/browse/AS7-1582
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.1.Final, 7.0.0.Final
Reporter: Brian Stansberry
Fix For: 7.1.0.CR1
The domain.conf file adds debug configuration to $JAVA_OPTS. That's incorrect, as it results in the same debug config being applied to the ProcessController and HostController processes, leading to port conflicts. A launch command something like this might work:
eval \"$JAVA\" $JAVA_OPTS \
\"-Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/process-controller/boot.log\" \
\"-Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties\" \
$PROCESS_CONTROLLER_DEBUG_OPTS \
-jar \"$JBOSS_HOME/jboss-modules.jar\" \
-mp \"$JBOSS_HOME/modules\" \
-logmodule "org.jboss.logmanager" \
org.jboss.as.process-controller \
-jboss-home \"$JBOSS_HOME\" \
-jvm \"$JAVA\" \
-- \
\"-Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/host-controller/boot.log\" \
\"-Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties\" \
$HOST_CONTROLLER_DEBUG_OPTS \
$JAVA_OPTS \
-- \
-default-jvm \"$JAVA\" \
"$@"
$PROCESS_CONTROLLER_DEBUG_OPTS and $HOST_CONTROLLER_DEBUG_OPTS would be new variables set in domain.conf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBRULES-3235) Fact Handle not found when using multiple entry points
by Edson Tirelli (Created) (JIRA)
Fact Handle not found when using multiple entry points
------------------------------------------------------
Key: JBRULES-3235
URL: https://issues.jboss.org/browse/JBRULES-3235
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.3.0.CR1
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.3.0.Final
Drools if failing to find the source entry point of a fact when multiple entry points are used with the java dialect. From Mark:
[16:16] mdproctor: go to DialectUtil fixBlockDescr
[16:17] mdproctor: we "fix" modofies here
[16:20] mdproctor: if ( declr == null || declr.isInternalFact() ) {
consequence.append( "org.drools.FactHandle " );
consequence.append( obj );
consequence.append( "__Handle2__ = drools.getFactHandle(" );
consequence.append( obj );
consequence.append( ");" );
}
[16:20] mdproctor: that is where an object is not already bound in a modify statement
[16:20] mdproctor: notice it calls drools.getFactHanle
[16:20] mdproctor: that then calls your method
[16:20] mdproctor: getFactHandleFromWM
[16:21] mdproctor: that for loop then neets to be
[16:21] mdproctor: for ( WorkingMemoryEntryPoint ep : workingMemory.getEntryPoints().values() ) {
handle = (FactHandle) ep.getFactHandle( object );
if ( handle != null ) {
if ( identityMap != null ) {
identityMap.put( object,
handle );
}
}
break;
}
--
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
12 years, 6 months
[JBoss JIRA] Created: (AS7-790) Subsystem "jms": attributes not writable
by Heiko Braun (JIRA)
Subsystem "jms": attributes not writable
----------------------------------------
Key: AS7-790
URL: https://issues.jboss.org/browse/AS7-790
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Attribute selector is not writeable"}}}
}
w/o modifications to existing queues/topics are not possible
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-3111) Regression: constraint comparing nested accessor to true fires when false
by Wolfgang Laun (JIRA)
Regression: constraint comparing nested accessor to true fires when false
---------------------------------------------------------------------------
Key: JBRULES-3111
URL: https://issues.jboss.org/browse/JBRULES-3111
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: FUTURE
The .drl file below produces
r3:one false
r2:one false
r1:one true
but only r1 is expected to fire.
Removing all "== true" is one way of showing the correct result.
declare Bool123
bool1 : boolean
bool2 : boolean
bool3 : boolean
end
declare Thing
name : String
bool123 : Bool123
end
rule kickOff
when
then
insert( new Thing( "one", new Bool123( true, false, false ) ) );
insert( new Thing( "two", new Bool123( false, false, false ) ) );
insert( new Thing( "three", new Bool123( false, false, false ) ) );
end
rule r1
when
$t: Thing( bool123.bool1 == true )
then
System.out.println( "r1:" + $t.getName() + " " + $t.getBool123().isBool1() );
end
rule r2
when
$t: Thing( bool123.bool2 == true )
then
System.out.println( "r2:" + $t.getName() + " " + $t.getBool123().isBool2() );
end
rule r3
when
$t: Thing( bool123.bool3 == true )
then
System.out.println( "r3:" + $t.getName() + " " + $t.getBool123().isBool3() );
end
~
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (AS7-1142) Exception when starting OSGi in AS7
by David Bosschaert (JIRA)
Exception when starting OSGi in AS7
------------------------------------
Key: AS7-1142
URL: https://issues.jboss.org/browse/AS7-1142
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Priority: Minor
When starting the OSGi Framework with Start Level 2 or higher, the following exception sometimes appears. It seems harmless though...
13:17:02,289 WARN [/] (CM Configuration Updater (ManagedService Update: pid=org.apache.felix.webconsole.internal.servlet.OsgiManager)) org.ops4j.pax.web.service.spi.model.ServletModel-2: unbindHttpService: Failed unregistering Servlet: java.lang.IllegalStateException: ServletModel{id=org.ops4j.pax.web.service.spi.model.ServletModel-2,name=org.ops4j.pax.web.service.spi.model.ServletModel-2,urlPatterns=[/system/console/*],alias=/system/console,servlet=org.apache.felix.webconsole.internal.servlet.OsgiManager@13dc8ea3,initParams={},context=ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext(a)75187984,contextParams={}}} was not found
at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.removeServlet(JettyServerImpl.java:230)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Started.removeServlet(ServerControllerImpl.java:271)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.removeServlet(ServerControllerImpl.java:112)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:205)
at org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:72)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:772) [OsgiManager.class:]
at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:660) [OsgiManager$HttpServiceTracker.class:]
at org.osgi.util.tracker.ServiceTracker$Tracked.untrack(ServiceTracker.java:1126) [ServiceTracker$Tracked.class:]
at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:347) [ServiceTracker.class:]
at org.apache.felix.webconsole.internal.servlet.OsgiManager.updateConfiguration(OsgiManager.java:826) [OsgiManager.class:]
at org.apache.felix.webconsole.internal.servlet.ConfigurationListener.updated(ConfigurationListener.java:66) [ConfigurationListener.class:]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-3073) Saliance is not working for 5.1.1 with fusion
by Richard Ambridge (JIRA)
Saliance is not working for 5.1.1 with fusion
---------------------------------------------
Key: JBRULES-3073
URL: https://issues.jboss.org/browse/JBRULES-3073
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Environment: Ubuntu
Reporter: Richard Ambridge
Assignee: Mark Proctor
Priority: Blocker
Attachments: DroolsRuleTest.java, Item.java, rule1.drl
Using drools with time based rules and saliance, the saliance is not used when firing the rules
This only happens when multiple objects update at the same time.
e.g. Rule 1 is
salience 1000
dialect "mvel"
when
$i : Item(val==10)
Item(val==11, this after [0s, 1m] $i)
Rule 2 is
salience 1000
dialect "mvel"
when
$i : Item(val==10)
not( Item(val==11, this after [0s,1m] $i))
Rule3 is
salience 100
when
$i : Item(val==11)
Then we insert 3 items with val==10
Rule2 is activated 3 times...
Then we insert an item with val==11
Note, with a val==10 and val==11 in the memory, Rule 1 will activate, and Rule 3 will activate
However, Rule1 should fire first.. as its saliance is high
For the first item it does, but then the Rule 3 fires before 2nd item does.
Audit log is attached, but summary is
Object inserted (1), Item: val==10
Activation created: Rule 2 (1)
Object inserted (2), Item: val==10
Activation created: Rule 2 (2)
Object inserted (3), Item: val==10
Activation created: Rule 2 (3)
Object inserted (4), Item: val==11
Activation created: Rule 1 (1)
Activation created: Rule 1 (2)
Activation created: Rule 1 (3)
Activation created: Rule 3 (4)
Activation cancelled: Rule 2 (1)
Activation cancelled: Rule 2 (2)
Activation cancelled: Rule 2 (3)
.. here we have 4 activations, 3 for Rule1 (saliance 1000), 1 for Rule3(saliance 100)
Activation executed Rule 1 (1)
Activation executed Rule 3 (4) //WRONG
Activation cancelled: Rule 1 (2)
Activation cancelled: Rule 1 (3)
Activation created: Rule 2 (2)
Activation created: Rule 2 (3)
Note, this works fine in Drools 5.0
In Drools 5.2.0 CR1 a null pointer is thrown (another issue will be logged for that)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-3064) dialect "mvel" flouts generic paramters
by Wolfgang Laun (JIRA)
dialect "mvel" flouts generic paramters
---------------------------------------
Key: JBRULES-3064
URL: https://issues.jboss.org/browse/JBRULES-3064
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.CR1
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.0
Given the rule
=============================================
rule x
dialect "mvel"
when
then
List<Integer> l = new ArrayList<Integer>();
end
=============================================
we get the error
=============================================
Unable to Analyse Expression List x = new ArrayList<Integer>();
[Error: Failed to compileShared: 1 compilation error(s):
- (1,23) could not resolve class: ArrayList<Integer>]
[Near : {... List x = new ArrayList<Integer>(); ....}]
^
[Line: 1, Column: 23]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months