[JBoss JIRA] (DROOLS-1) Rules getting executed even when the condition specifed is not satisfied
by Gladson Soans (JIRA)
Gladson Soans created DROOLS-1:
----------------------------------
Summary: Rules getting executed even when the condition specifed is not satisfied
Key: DROOLS-1
URL: https://issues.jboss.org/browse/DROOLS-1
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: SOLARIS
Reporter: Gladson Soans
Assignee: Mark Proctor
Hi,
Below is the rules:
rule "RelStatusUpdateCalcCheck"
salience 55
no-loop true
when
$evt : UpdateRateStatusReq(statusID == RateStatusEnum.READY.getValue() || == RateStatusEnum.HOLIDAY_ROLL_FORWARD.getValue() || == RateStatusEnum.ROLL_FORWARD.getValue()) from entry-point RequestStream
$rr : ReliableRate(rateId == $evt.getRateID())
$dr : DerivedRate(holidayFlag == false, grfLock == false, $lr : listInputRateId, $lr.contains($evt.getRateID()))
then
cepService.relStatusUpdateCalcCheck($evt, $rr, $dr);
end
The last condition states that if 'holidayflag' is false and other conditions are satisfied as well then only execute the the java method. But the method gets executed even when the holidayflag is true. Only when I restart my app server the method doesnt get executed when holidayflag is true. Why is this so?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6171) Confusing error message when an invalid element is added to host.xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6171?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6171:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
(was: 7.2.0.CR1)
> Confusing error message when an invalid element is added to host.xml
> --------------------------------------------------------------------
>
> Key: AS7-6171
> URL: https://issues.jboss.org/browse/AS7-6171
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> I deliberately added an element <bogus/> to host.xml as part of testing something. I got this not very useful error message:
> [Host Controller] 20:25:50,435 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:163) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:399) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
> [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[4,5]
> [Host Controller] Message: JBAS014725: Missing required element(s): MANAGEMENT
> [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequiredElement(ParseUtils.java:154) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readHostElement_1_1(HostXml.java:392) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:129) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:104) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Host Controller] ... 4 more
> The parser should detect the invalid element and fail with the unexpected element message.
> Look for the same problem elsewhere as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6171) Confusing error message when an invalid element is added to host.xml
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6171:
-------------------------------------
Summary: Confusing error message when an invalid element is added to host.xml
Key: AS7-6171
URL: https://issues.jboss.org/browse/AS7-6171
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: 7.2.0.CR1
I deliberately added an element <bogus/> to host.xml as part of testing something. I got this not very useful error message:
[Host Controller] 20:25:50,435 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
[Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:163) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:399) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[4,5]
[Host Controller] Message: JBAS014725: Missing required element(s): MANAGEMENT
[Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequiredElement(ParseUtils.java:154) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readHostElement_1_1(HostXml.java:392) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:129) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:104) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
[Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Host Controller] ... 4 more
The parser should detect the invalid element and fail with the unexpected element message.
Look for the same problem elsewhere as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-1581) tomcatAuthentication attribute on the AJP connector
by Usman Saleem (JIRA)
[ https://issues.jboss.org/browse/AS7-1581?page=com.atlassian.jira.plugin.s... ]
Usman Saleem commented on AS7-1581:
-----------------------------------
Hi Jean,
You modified http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_0_17_FINAL/java/o... with following change:
{noformat}
protected boolean tomcatAuthentication =
Boolean.valueOf(System.getProperty("org.apache.coyote.ajp.AprProcessor.TOMCATAUTHENTICATION", "true")).booleanValue();
{noformat}
However, AjpAprProtocol.java modified this value as follows:
{noformat}
/**
* Should authentication be done in the native webserver layer,
* or in the Servlet container ?
*/
protected boolean tomcatAuthentication = true;
...
// -------------------------------------- AjpConnectionHandler Inner Class
protected static class AjpConnectionHandler implements Handler {
...
protected AjpAprProcessor createProcessor() {
AjpAprProcessor processor = new AjpAprProcessor(proto.packetSize, proto.endpoint);
processor.setAdapter(proto.adapter);
processor.setTomcatAuthentication(proto.tomcatAuthentication); // <--- This will override the system property settings.
processor.setRequiredSecret(proto.requiredSecret);
register(processor);
return processor;
}
{noformat}
Hence, the change should also be made in AjpAprProtocol.java as:
{noformat}
protected boolean tomcatAuthentication =
Boolean.valueOf(System.getProperty("org.apache.coyote.ajp.AprProcessor.TOMCATAUTHENTICATION", "true")).booleanValue();
{noformat}
Thanks,
Usman
> tomcatAuthentication attribute on the AJP connector
> ---------------------------------------------------
>
> Key: AS7-1581
> URL: https://issues.jboss.org/browse/AS7-1581
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Web
> Affects Versions: 7.0.0.Final
> Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension
> Reporter: Brett Prucha
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 7.2.0.CR1
>
>
> In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6170) Host controller attempts to write logging configuration
by James Perkins (JIRA)
James Perkins created AS7-6170:
----------------------------------
Summary: Host controller attempts to write logging configuration
Key: AS7-6170
URL: https://issues.jboss.org/browse/AS7-6170
Project: Application Server 7
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Fix For: 7.2.0.Alpha1
Due to the switch to using a {{ResultHandler}} when the host controller completes logging steps and attempt is made to write the {{logging.properties}} file. The following error is logged:
{code}
[Host Controller] 12:00:59,110 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) JBAS014781: Step handler org.jboss.as.logging.LoggerOperations$LoggerAddOperationStepHandler@5ac12e for operation set-root-logger at address [
[Host Controller] ("profile" => "full-ha"),
[Host Controller] ("subsystem" => "logging"),
[Host Controller] ("root-logger" => "ROOT")
[Host Controller] ] failed handling operation rollback -- JBAS014847: Could not find a path called 'logging.properties'
{code}
The commit and write of the logging configuration should only happen in the {{RUNTIME}} stage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6104) jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6104?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6104:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6104
> URL: https://issues.jboss.org/browse/AS7-6104
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Professional SP1
> Reporter: Raymond Naseef
> Assignee: Brian Stansberry
> Labels: jboss-as7, modules, postgresql
> Fix For: 7.2.0.Alpha1
>
>
> NullPointerException during jboss-cli remove with command:
> jboss-cli --connect command="/subsystem=datasources/jdbc-driver=bop:remove"
> Console and log below.
> This happens when standalone.xml has XML entry for driver that does not exist (see "Steps to Reproduce"). I have also seen this happen in a case where the driver does exist; not sure how the latter happened, or how important that is.
> MS-DOS Console:
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: null",
> "rolled-back" => true
> }
> Server Log:
> 23:17:42,627 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) JBAS014612: Operation ("remove") failed - address: ([
> ("subsystem" => "datasources"),
> ("jdbc-driver" => "postgresql-driver")
> ]): java.lang.NullPointerException
> at org.jboss.as.controller.OperationContextImpl.doRemove(OperationContextImpl.java:298) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.OperationContextImpl.removeService(OperationContextImpl.java:293) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.connector.subsystems.datasources.JdbcDriverRemove.performRuntime(JdbcDriverRemove.java:66)
> at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-4990) Cannot embed Jersey 1.13-b01 with error: UnsupportedOperationException: JBAS011859: Naming context is read-only
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-4990?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas reopened AS7-4990:
---------------------------------
Assignee: Stuart Douglas (was: John Bailey)
I'm not sure why I rejected this, it looks this I totally mis-read what you were trying to do. This looks like a weld problem
> Cannot embed Jersey 1.13-b01 with error: UnsupportedOperationException: JBAS011859: Naming context is read-only
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4990
> URL: https://issues.jboss.org/browse/AS7-4990
> Project: Application Server 7
> Issue Type: Bug
> Components: Naming
> Affects Versions: 7.1.1.Final
> Environment: JBoss AS 7.1.1.Final (removing the jaxrs subsystem)
> java version "1.6.0_31"
> Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
> Linux annafi.dev 3.0.0-21-generic #35-Ubuntu SMP Fri May 25 17:57:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Hendy Irawan
> Assignee: Stuart Douglas
>
> {code}
> 03:47:22,356 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"thread-inmem-jerseywar.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"thread-inmem-jerseywar.war\".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:116)
> at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:338)
> at org.jboss.as.naming.InitialContext.createSubcontext(InitialContext.java:229)
> at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:346)
> at javax.naming.InitialContext.createSubcontext(InitialContext.java:483)
> at com.sun.jersey.server.impl.cdi.CDIExtension$1.stepInto(CDIExtension.java:280)
> at com.sun.jersey.server.impl.cdi.CDIExtension.diveIntoJNDIContext(CDIExtension.java:267)
> at com.sun.jersey.server.impl.cdi.CDIExtension.createJerseyConfigJNDIContext(CDIExtension.java:273)
> at com.sun.jersey.server.impl.cdi.CDIExtension.initialize(CDIExtension.java:192)
> at com.sun.jersey.server.impl.cdi.CDIExtension.beforeBeanDiscovery(CDIExtension.java:297)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:241)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:229)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "}}}}
> {code}
> Sample project to reproduce:
> https://github.com/ceefour/odata-sandbox/tarball/jboss-jndi-readonly-jersey
> in folder: thread-inmem-jerseywar
> The JBoss AS 7.1.1 configuration is in: thread-inmem-jerseywar/jboss/standalone-no-jaxrs.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6169) CLI does not work on windows
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6169?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6169:
----------------------------------
Priority: Blocker (was: Critical)
> CLI does not work on windows
> ----------------------------
>
> Key: AS7-6169
> URL: https://issues.jboss.org/browse/AS7-6169
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, Windows 8, Windows Server 2008r2
> Reporter: Tomaz Cerar
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: cli, windows
>
> Typing in CLI crashes with error below after any character is entered
> {noformat}
> [standalone@localhost:9999 /] ajava.lang.ArithmeticException: / by zero
> at org.jboss.aesh.console.Console.writeChar(Console.java:752)
> at org.jboss.aesh.console.Console.writeChars(Console.java:735)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:432)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1167)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6169) CLI does not work on windows
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6169?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6169:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> CLI does not work on windows
> ----------------------------
>
> Key: AS7-6169
> URL: https://issues.jboss.org/browse/AS7-6169
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, Windows 8, Windows Server 2008r2
> Reporter: Tomaz Cerar
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: cli, windows
> Fix For: 7.2.0.Alpha1
>
>
> Typing in CLI crashes with error below after any character is entered
> {noformat}
> [standalone@localhost:9999 /] ajava.lang.ArithmeticException: / by zero
> at org.jboss.aesh.console.Console.writeChar(Console.java:752)
> at org.jboss.aesh.console.Console.writeChars(Console.java:735)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:432)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1167)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-5722) Backward compatibility issue with JMS clients
by Andrig Miller (JIRA)
[ https://issues.jboss.org/browse/AS7-5722?page=com.atlassian.jira.plugin.s... ]
Andrig Miller commented on AS7-5722:
------------------------------------
Just so this is recorded here, we also have a commitment to support older versions of clients. So, not only do all EAP 6 clients have to work with newer versions of EAP 6, the EAP 5.1.2 client has to work against an EAP 6 server. I believe we committed to support across two major versions above the client version. So, an EAP 5.1.2 and above client (where HornetQ first became supported), has to work with any EAP 6.x server, and any EAP 7.x server in the future too.
> Backward compatibility issue with JMS clients
> ---------------------------------------------
>
> Key: AS7-5722
> URL: https://issues.jboss.org/browse/AS7-5722
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Critical
> Fix For: 7.2.0.Alpha1
>
>
> When standalone jms client is trying to connect with "old" jboss-client.jar from AS 7.1.2.Final (HornetQ 2.2.16.Final) to AS 7.2.0.Alpha1 (HornetQ 2.3.0.Beta1) then ClassNotFoundException it thrown:
> Console log of jms client:
> {code}
> [jbossqa@station4 as7-with-hq-replicated]$ java -cp /home/jbossqa/hornetq_eap6_testsuite/as7-with-hq-replicated/client-1.0-SNAPSHOT.jar:/home/jbossqa/hornetq_eap6_testsuite/server1/jboss-eap-6.0/bin/client/jboss-client.jar org.jboss.jms.client.TestProducer 192.168.40.1 jms/queue/testQueue0 10
> remote://192.168.40.1:4447
> Oct 10, 2012 11:44:41 AM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.6.GA-redhat-1
> Oct 10, 2012 11:44:41 AM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.6.GA-redhat-1
> Oct 10, 2012 11:44:41 AM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.SP1-redhat-1
> Oct 10, 2012 11:44:42 AM org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver handleEnd
> ERROR: Channel end notification received, closing channel Channel ID f6fa08e1 (outbound) of Remoting connection 2a0ab444 to /192.168.40.1:4447
> org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: org.hornetq.api.core.BroadcastEndpointFactoryConfiguration]
> at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49)
> at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104)
> at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:78)
> at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:227)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:119)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:223)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
> at javax.naming.InitialContext.lookup(InitialContext.java:409)
> at org.jboss.jms.client.TestProducer.startClient(TestProducer.java:47)
> at org.jboss.jms.client.TestProducer.main(TestProducer.java:28)
> Caused by: java.io.IOException: java.lang.ClassNotFoundException: org.hornetq.api.core.BroadcastEndpointFactoryConfiguration
> at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:159)
> at org.jboss.naming.remote.protocol.v1.BaseProtocolCommand.readResult(BaseProtocolCommand.java:60)
> at org.jboss.naming.remote.protocol.v1.Protocol$1.handleClientMessage(Protocol.java:149)
> at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver$1.run(RemoteNamingStoreV1.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.ClassNotFoundException: org.hornetq.api.core.BroadcastEndpointFactoryConfiguration
> at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:135)
> at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:116)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:871)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:903)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:903)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1205)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.river.RiverUnmarshaller.readFields(RiverUnmarshaller.java:1678)
> at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1594)
> at org.jboss.marshalling.river.RiverUnmarshaller.doInitSerializable(RiverUnmarshaller.java:1558)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1236)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37)
> at org.jboss.naming.remote.protocol.v1.Protocol$1$3.read(Protocol.java:156)
> ... 6 more
> Oct 10, 2012 11:44:42 AM org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver handleEnd
> ERROR: Channel end notification received, closing channel Channel ID dac0f594 (outbound) of Remoting connection 16e1eea8 to /192.168.40.1:4447
> {code}
> How to reproduce:
> 1) Download reproducer.zip from QA Lab and unzip reproducer.zip: {code}scp -r messaging-18.jbm.lab.bos.redhat.com:/home/mnovak/reproducer-backward-compatibility .{code}
> 2) Start AS7 server:{code}cd jboss-as-7.2.0.Alpha1-SNAPSHOT/bin;sh standalone.sh -c standalone-full-ha.xml -b localhost{code}
> 3) Start jms producer:{code}java -cp $PWD/client-1.0-SNAPSHOT.jar:$PWD/jboss-old-hq226-client.jar org.jboss.jms.client.TestProducer localhost jms/queue/testQueue0 10{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months