[JBoss JIRA] (AS7-4695) Server does not start with sun jmx enabled
by Michael Voegele (JIRA)
Michael Voegele created AS7-4695:
------------------------------------
Summary: Server does not start with sun jmx enabled
Key: AS7-4695
URL: https://issues.jboss.org/browse/AS7-4695
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
Starting a server in domain mode configured as
{code:xml}
<servers>
<server name="server-1" group="server-group-1" auto-start="true">
<system-properties>
<property name="com.sun.management.jmxremote.port" value="13013"/>
<property name="com.sun.management.jmxremote.authenticate" value="false"/>
<property name="com.sun.management.jmxremote.ssl" value="false"/>
...
{code}
does not work.
{code:java}
[Server:server-1] WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
[Server:server-1] Exception in thread "main" java.lang.ExceptionInInitializerError
[Server:server-1] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:86)
[Server:server-1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[Server:server-1] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[Server:server-1] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[Server:server-1] at java.lang.reflect.Method.invoke(Method.java:597)
[Server:server-1] at org.jboss.modules.Module.run(Module.java:260)
[Server:server-1] at org.jboss.modules.Main.main(Main.java:291)
[Server:server-1] Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
[Server:server-1] at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
[Server:server-1] at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
[Server:server-1] ... 7 more
{code}
I've seen in https://issues.jboss.org/browse/AS7-1859 that this won't be supported. May I ask why? I think that this is standard java and it should work.
--
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
13 years, 12 months
[JBoss JIRA] (AS7-4694) JBAS014478: Could not find timeout method
by Franck Garcia (JIRA)
Franck Garcia created AS7-4694:
----------------------------------
Summary: JBAS014478: Could not find timeout method
Key: AS7-4694
URL: https://issues.jboss.org/browse/AS7-4694
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: ubuntu 11.04, x32, oracle jdk_1.6.0_27, AS 7.1.1.Final
Reporter: Franck Garcia
Assignee: jaikiran pai
I've added a timer service in one of my ejb of a specific module inside my ear application through the @Schedule annotation.
I then removed the method annotated with the Schedule annotation and redeploy.
The AS refuses to deploy my module (and my entire ear as a consequence) ended up with the following exception:
Caused by: java.lang.IllegalStateException: JBAS014478: Could not find timeout method: com.acme.AppLogger.processSend(javax.ejb.Timer)
at org.jboss.as.ejb3.timerservice.CalendarTimer.<init>(CalendarTimer.java:138)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:906)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:633)
at org.jboss.as.ejb3.timerservice.TimerServiceImpl.start(TimerServiceImpl.java:190)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
I add to get rid of the $JBOSS_DIR$standalone/data/timer-service-data folder to be able to properly redeploy.
--
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
13 years, 12 months
[JBoss JIRA] (JBRULES-3487) NullPointerException in org.jbpm.ruleflow.core.validation.RuleFlowProcessValidator
by James Nord (JIRA)
James Nord created JBRULES-3487:
-----------------------------------
Summary: NullPointerException in org.jbpm.ruleflow.core.validation.RuleFlowProcessValidator
Key: JBRULES-3487
URL: https://issues.jboss.org/browse/JBRULES-3487
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (flow)
Affects Versions: 5.4.0.CR1
Reporter: James Nord
Assignee: Mark Proctor
There is a coding issue in that leads to a NullPOinterException.
The Exception has been shown presumable due to an invalid rf file - but the code gives an unhelpful exception.
Insepction of the code reveals that if the first condition is true on line 193 then the code will blow up - which is presumable not what the coder has intended
{code:title=RuleFlowProcessValidator.java Line 190 onwars|borderStyle=solid}
if (split.getType() == Split.TYPE_XOR || split.getType() == Split.TYPE_OR ) {
for ( final Iterator<Connection> it = split.getDefaultOutgoingConnections().iterator(); it.hasNext(); ) {
final Connection connection = it.next();
if (split.getConstraint(connection) == null && !split.getConstraint(connection).isDefault() && (split.getConstraint(connection).getConstraint() == null || split.getConstraint(connection).getConstraint().trim().length() == 0)) {
errors.add(new ProcessValidationErrorImpl(process,
"Split node '" + node.getName() + "' [" + node.getId() + "] does not have a constraint for " + connection.toString() + "."));
}
}
}
{code}
"if (split.getConstraint(connection) == null && !split.getConstraint(connection).isDefault()"
if "split.gerConstraint(connection)" is null then "split.getConstraint(connection).isDefault()" will dereference null.
--
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
13 years, 12 months
[JBoss JIRA] (AS7-4688) Server shutdown may lead to NoClassDefFoundError
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-4688:
-----------------------------------
Summary: Server shutdown may lead to NoClassDefFoundError
Key: AS7-4688
URL: https://issues.jboss.org/browse/AS7-4688
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
{code}
09:42:16,497 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
09:42:16,514 INFO [org.apache.aries.jmx] Stopping JMX OSGi agent
09:42:16,516 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: jbosgi-jmx:1.1.0.Final
09:42:16,519 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.ops4j.pax.web.pax-web-jsp:1.1.2
09:42:16,521 INFO [org.apache.aries.jmx] Unregistering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@165f5a4 with name osgi.core:type=serviceState,version=1.5
09:42:16,519 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.apache.felix.eventadmin:1.2.14
09:42:16,531 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.apache.felix.eventadmin:1.2.14
09:42:16,533 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: jbosgi-jmx:1.1.0.Final
09:42:16,528 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.ops4j.pax.web.pax-web-jsp:1.1.2
09:42:16,532 INFO [org.apache.aries.jmx] Unregistering MBean with ObjectName [osgi.compendium:service=cm,version=1.3] for service with service.id [21]
09:42:16,534 INFO [org.apache.aries.jmx] Unregistering org.osgi.jmx.framework.BundleStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@165f5a4 with name osgi.core:type=bundleState,version=1.5
09:42:16,534 INFO [org.apache.aries.jmx] Unregistering org.osgi.jmx.framework.FrameworkMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@165f5a4 with name osgi.core:type=framework,version=1.5
09:42:16,535 INFO [org.apache.aries.jmx] Unregistering org.osgi.jmx.framework.PackageStateMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@165f5a4 with name osgi.core:type=packageState,version=1.5
09:42:16,535 INFO [org.apache.aries.jmx] Unregistering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.PluggableMBeanServerImpl@165f5a4 with name osgi.compendium:service=cm,version=1.3
09:42:16,542 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.apache.aries.jmx:0.3.0
09:42:16,543 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.apache.aries.jmx:0.3.0
09:42:16,544 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.ops4j.pax.web.pax-web-extender-war:1.1.2
09:42:16,549 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.ops4j.pax.web.pax-web-extender-war:1.1.2
09:42:16,554 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.apache.felix.log:1.0.0
09:42:16,560 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.apache.felix.log:1.0.0
09:42:16,555 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: jboss-osgi-logging:1.0.0
09:42:16,567 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: jboss-osgi-logging:1.0.0
09:42:16,568 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: jboss-as-osgi-configadmin:7.1.2.Final-SNAPSHOT
09:42:16,574 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.apache.felix.scr:1.6.0
09:42:16,575 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: jboss-as-osgi-configadmin:7.1.2.Final-SNAPSHOT
09:42:16,575 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.apache.felix.scr:1.6.0
09:42:16,613 INFO [org.jboss.osgi.framework] JBOSGI011003: Bundle stopped: org.apache.aries.blueprint:0.4.0
09:42:16,613 INFO [org.jboss.osgi.framework] JBOSGI011005: Bundle uninstalled: org.apache.aries.blueprint:0.4.0
09:42:16,624 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
09:42:16,628 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
09:42:16,646 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.aries.proxy:org.apache.aries.proxy:0.4 in 217ms
09:42:16,647 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.jboss.osgi.jmx:jbosgi-jmx:1.1.0.Final in 220ms
09:42:16,659 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.felix:org.apache.felix.scr:1.6.0 in 223ms
09:42:16,660 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.aries:org.apache.aries.util:0.4 in 225ms
09:42:16,648 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.aries.blueprint:org.apache.aries.blueprint:0.4 in 216ms
09:42:16,654 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.ops4j.pax.web:pax-web-jetty-bundle:1.1.2 in 219ms
09:42:16,661 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.felix:org.apache.felix.eventadmin:1.2.14 in 230ms
09:42:16,661 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.ops4j.pax.web:pax-web-jsp:1.1.2 in 237ms
09:42:16,650 ERROR [stderr] 2012-05-02 09:42:16.640:WARN:oejuc.AbstractLifeCycle:FAILED qtp830746789{8<=7<=7/254,0}#FAILED: java.lang.NoClassDefFoundError: org/eclipse/jetty/util/thread/QueuedThreadPool$1
09:42:16,662 ERROR [stderr] java.lang.NoClassDefFoundError: org/eclipse/jetty/util/thread/QueuedThreadPool$1
09:42:16,662 ERROR [stderr] at org.eclipse.jetty.util.thread.QueuedThreadPool.doStop(QueuedThreadPool.java:121)
09:42:16,662 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.ops4j.pax.web:pax-web-extender-war:1.1.2 in 233ms
09:42:16,662 ERROR [stderr] at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:84)
09:42:16,663 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment org.apache.aries.jmx:org.apache.aries.jmx:0.3 in 225ms
09:42:16,663 ERROR [stderr] at org.eclipse.jetty.util.component.AggregateLifeCycle.doStop(AggregateLifeCycle.java:59)
09:42:16,664 ERROR [stderr] at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:64)
09:42:16,664 ERROR [stderr] at org.eclipse.jetty.server.handler.HandlerWrapper.doStop(HandlerWrapper.java:102)
09:42:16,664 ERROR [stderr] at org.eclipse.jetty.server.Server.doStop(Server.java:322)
09:42:16,664 ERROR [stderr] at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:84)
09:42:16,664 ERROR [stderr] at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.stop(JettyServerImpl.java:117)
09:42:16,664 ERROR [stderr] at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Started.stop(ServerControllerImpl.java:253)
09:42:16,665 ERROR [stderr] at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.stop(ServerControllerImpl.java:73)
09:42:16,665 ERROR [stderr] at org.ops4j.pax.web.service.internal.Activator.stop(Activator.java:149)
09:42:16,665 ERROR [stderr] at org.ops4j.pax.web.service.jetty.internal.CompositeActivator.stop(CompositeActivator.java:52)
09:42:16,665 ERROR [stderr] at org.jboss.osgi.framework.internal.HostBundleState.stopInternal(HostBundleState.java:414)
09:42:16,665 ERROR [stderr] at org.jboss.osgi.framework.internal.BundleManagerPlugin.uninstallBundle(BundleManagerPlugin.java:413)
09:42:16,665 ERROR [stderr] at org.jboss.osgi.framework.internal.UserBundleInstalledService.stop(UserBundleInstalledService.java:92)
09:42:16,666 ERROR [stderr] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
09:42:16,666 ERROR [stderr] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
09:42:16,666 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
09:42:16,666 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
09:42:16,666 ERROR [stderr] at java.lang.Thread.run(Thread.java:662)
{code}
--
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
13 years, 12 months
[JBoss JIRA] Created: (JBAS-8366) Failure to deploy a war file with JBoss 5.0
by Sasha Matison (JIRA)
Failure to deploy a war file with JBoss 5.0
-------------------------------------------
Key: JBAS-8366
URL: https://jira.jboss.org/browse/JBAS-8366
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.0.0.GA
Environment: Windows 2003 R2 SP2, JBoss AS 5.0, JDK 1.6_16
Reporter: Sasha Matison
Assignee: Scott M Stark
Priority: Blocker
While deploying our war file with JBoss AS 5.0 we are getting the following error:
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
We are shipping the product with a version of Xerces-j 2.9.1. Removing this version from the product is not an option. Note that the war file used to work with JBoss 4.x.
This issue is blocking JBoss 5.0 testing. Please advise on the solution.
--
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
13 years, 12 months
[JBoss JIRA] (JBRULES-3363) Add support to inline constraints on multi-function accumulate
by Edson Tirelli (JIRA)
Edson Tirelli created JBRULES-3363:
--------------------------------------
Summary: Add support to inline constraints on multi-function accumulate
Key: JBRULES-3363
URL: https://issues.jboss.org/browse/JBRULES-3363
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.4.0.Beta1
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta2
FROM MARK:
===========
Edson,
While I don't want to change to acc/for keyword quite yet, until we are sure what drastic changes we want to make to syntax. I think we can evolve accumulate()
1) make the first ", " optionall [,;]. Where the documented new separate is ";"
2) functions are still "," separated
3) allow an optional second ";" after this boolean expression, an eval without the eval wrapper.
3. can be done now with a separate eval(....) after the accumulate. But I think good to encapsulate the intent of the guard within the accumulate itself, it's also another opportunity to remove the "eval" keyword for a common use case. For now we'll just rewrite the accumulate to place an eval() CE after the acc. It's a small win, which I think will make the DRL look nicer, especially for CEP use cases.
============
FROM EDSON:
============
Mark,
(1) and (2) are ok. Regarding (3), we can embed the expression in the accumulate node itself. No need for a separate node. And if we use ; as the separator, we don't need the eval() keyword.
--
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
13 years, 12 months
[JBoss JIRA] (JBRULES-3466) sum with no matching values results in NPE on reverse
by Chris Dolan (JIRA)
Chris Dolan created JBRULES-3466:
------------------------------------
Summary: sum with no matching values results in NPE on reverse
Key: JBRULES-3466
URL: https://issues.jboss.org/browse/JBRULES-3466
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.4.0.CR1
Environment: drools-planner 5.4.0-SNAPSHOT, snapshot downloaded on Apr 9, 2012
Reporter: Chris Dolan
Assignee: Geoffrey De Smet
I have a rule with this element in the when clause:
{noformat}
$beforePrediction : Number() from accumulate(
JobSlot(job != NULL_JOB, $j : job, $service == service, $ordinal > ordinal) and $p : Prediction(job == $j, service == $service),
sum($p.getMillisMid())
)
{noformat}
When I execute this I have cases where there are no matching Prediction instances, so the sum is zero. Later on retract, I get this:
{noformat}
Caused by: java.lang.NullPointerException: null
at org.drools.base.accumulators.SumAccumulateFunction.reverse(SumAccumulateFunction.java:83)
at org.drools.base.accumulators.JavaAccumulatorFunctionExecutor.reverse(JavaAccumulatorFunctionExecutor.java:130)
at org.drools.rule.Accumulate.reverse(Accumulate.java:208)
{noformat}
The relevant code is this:
{noformat}
public void accumulate(Serializable context,
Object value) {
SumData data = (SumData) context;
data.total += ((Number) value).doubleValue();
}
{noformat}
and this:
{noformat}
public void reverse(Object workingMemoryContext,
Object context,
Tuple leftTuple,
InternalFactHandle handle,
Declaration[] declarations,
Declaration[] innerDeclarations,
WorkingMemory workingMemory) throws Exception {
final Object value = ((JavaAccumulatorFunctionContext) context).reverseSupport.remove( Integer.valueOf( handle.getId() ) );
this.function.reverse( ((JavaAccumulatorFunctionContext) context).context,
value );
}
{noformat}
A breakpoint reveals that handle is a Prediction instance. Somehow that handle was not added to reverseSupport, apparently.
--
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
13 years, 12 months