March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-911) Kie Navigator does not recognize running EAP server

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-911?page=com.atlassian.jira.plugin... ] Tomas David closed DROOLS-911. ------------------------------ Verified with 6.4.0.CR2. > Kie Navigator does not recognize running EAP server > --------------------------------------------------- > > Key: DROOLS-911 > URL: https://issues.jboss.org/browse/DROOLS-911 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.3.0.CR2 > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Labels: qe-recommend-fix-before-ga, reported-by-qe > Fix For: 6.4.0.CR2 > > > Kie Navigator does not recognize running EAP server. Server should be listed in Kie Navigator view but there is only default link ("No servers available. Click this link to create a new server...") to the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6434) System property 'org.jboss.as.security.jacc-module' not always used

by Winfried Wasser (JIRA)

Winfried Wasser created WFLY-6434: ------------------------------------- Summary: System property 'org.jboss.as.security.jacc-module' not always used Key: WFLY-6434 URL: https://issues.jboss.org/browse/WFLY-6434 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 10.0.0.Final Reporter: Winfried Wasser Assignee: Darran Lofthouse Priority: Blocker Attachments: security.patch JaccService of security subsystem does not use the system property 'org.jboss.as.security.jacc-module' for class loader. Due to this "not using", the custom JACC module is not used. This property was introduced by WFLY-5340 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6152) EJB timer scheduler log an Exception for an already canceled timer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6152?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6152: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1305960|https://bugzilla.redhat.com/show_bug.cgi?id=1305960] from MODIFIED to POST > EJB timer scheduler log an Exception for an already canceled timer > ------------------------------------------------------------------ > > Key: WFLY-6152 > URL: https://issues.jboss.org/browse/WFLY-6152 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Labels: timer, timers, timerservice > > If a timer is canceled inside of the @timeout method the scheduler will log an ERROR if the timer duration is longer than the intervall and an overlapping execution should be fired. > This is due to internal validatons. > This will not happen if the timer is canceled by an external process, here the scheduler is removed. > The log message is like this: > ERROR [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0164: Exception running timer task for timer [id=0bd9870b-568b-42f5-9bda-e1525c3500aa timedObjectId=ejb30-timer.ejb30-timer.SimpleTimerBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@53ba1a7f initialExpiration=Tue Feb 09 17:19:32 CET 2016 intervalDuration(in milli sec)=5000 nextExpiration=Tue Feb 09 17:19:37 CET 2016 timerState=CANCELED info=SimpleTimerInfo description=A timer started every 5 seconds] on EJB ejb30-timer.ejb30-timer.SimpleTimerBean: javax.ejb.NoSuchObjectLocalException: WFLYEJB0331: Timer was canceled > at org.jboss.as.ejb3.timerservice.TimerImpl.assertTimerState(TimerImpl.java:459) > at org.jboss.as.ejb3.timerservice.TimerImpl.isPersistent(TimerImpl.java:215) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.shouldRun(TimerServiceImpl.java:1117) > at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:124) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1221) > at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2645) SFSB containing injected DataSource fails to passivate/serialize

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2645?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2645: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 901300|https://bugzilla.redhat.com/show_bug.cgi?id=901300] from MODIFIED to POST > SFSB containing injected DataSource fails to passivate/serialize > ---------------------------------------------------------------- > > Key: WFLY-2645 > URL: https://issues.jboss.org/browse/WFLY-2645 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Stefano Maestri > Priority: Critical > > See JBPAPP6-1762 for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4260) Schema validation errors against jboss-service_7_0.xsd

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4260?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4260: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1183165|https://bugzilla.redhat.com/show_bug.cgi?id=1183165] from MODIFIED to POST > Schema validation errors against jboss-service_7_0.xsd > ------------------------------------------------------- > > Key: WFLY-4260 > URL: https://issues.jboss.org/browse/WFLY-4260 > Project: WildFly > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Tomas Hofman > > When you import a quickstart containing a jboss-service.xml file, you get the following XML: > cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. > The quickstart source is located here: > https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x/hello... > I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: > * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml > * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml > * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml > * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > There seems to be an error in the schema: > http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd > The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4533) Port jboss-as-messaging_1_5.xsd from EAP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4533?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4533: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1212941|https://bugzilla.redhat.com/show_bug.cgi?id=1212941] from MODIFIED to POST > Port jboss-as-messaging_1_5.xsd from EAP > ---------------------------------------- > > Key: WFLY-4533 > URL: https://issues.jboss.org/browse/WFLY-4533 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 9.0.0.CR1 > > > Unfortunately an incompatible change has been introduced in jboss-as-messaging_1_4.xsd within EAP, this Jira issue is to minimise the impact. > EAP should have a new jboss-as-messaging_1_5.xsd added and the changes to the 1.4 schema reverted. The parser will be updated to support 1.5 and will remain quietly accepting the new element. > In WildFly we need to forward port this new 1.5 schema and also update the 1.4 parser to quietly accept the new element. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1121: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1265740|https://bugzilla.redhat.com/show_bug.cgi?id=1265740] from MODIFIED to POST > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Optional > Fix For: 3.0.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-591) revertReloadRequired() throws a NPE is reloadRequired has not been called

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-591?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-591: ------------------------------------------------ Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1294591|https://bugzilla.redhat.com/show_bug.cgi?id=1294591] from MODIFIED to POST > revertReloadRequired() throws a NPE is reloadRequired has not been called > ------------------------------------------------------------------------- > > Key: WFCORE-591 > URL: https://issues.jboss.org/browse/WFCORE-591 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 1.0.0.Beta1 > > > If an operation step handler calls org.jboss.as.controller.OperationContext#revertReloadRequired() when org.jboss.as.controller.OperationContext#reloadRequired() has not been called, it throws a NPE: > {noformat} > java.lang.NullPointerException > at org.jboss.as.controller.ControlledProcessState.revertReloadRequired(ControlledProcessState.java:181) > at org.jboss.as.controller.AbstractOperationContext.revertReloadRequired(AbstractOperationContext.java:1037) > at org.jboss.as.controller.test.RevertReloadRequiredTestCase$TestResourceAddHandler.rollbackRuntime(RevertReloadRequiredTestCase.java:98) > at org.jboss.as.controller.AbstractAddStepHandler$1$1.handleRollback(AbstractAddStepHandler.java:133) > at org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1419) > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1385) > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1367) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1323) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1283) > at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1172) > at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:929) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:877) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1182) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:205) > {noformat} > The NPE is caused by this.activeStep.restartStamp field which is set only when reloadRequired() (or restartRequired()) is called. > My OSH may call reloadRequired() or not depending on some runtime state and I could add some logic to make sure I call > I can fix my handle to check that I call context.revertReloadRequired() only I had previously called reloadRequired () first. > However, in order to make the OperationContext more robust, I think that the revertReloadRequired() method should instead be a no-op if there is no reload required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6163) Remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6163: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1311733|https://bugzilla.redhat.com/show_bug.cgi?id=1311733] from MODIFIED to POST > Remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-6163 > URL: https://issues.jboss.org/browse/WFLY-6163 > Project: WildFly > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 10.1.0.Final > > > We can remove org.apache.santuario.xmlsec dependency from org.jboss.as.webservices.server.integration module as Santuario is not needed directly from JBossWS (it's directly used by WSS4J and CXF though). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3483) Improve the ability to use MS Windows keystore for the web servers ssl connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3483?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3483: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1108310|https://bugzilla.redhat.com/show_bug.cgi?id=1108310] from MODIFIED to POST > Improve the ability to use MS Windows keystore for the web servers ssl connector > -------------------------------------------------------------------------------- > > Key: WFLY-3483 > URL: https://issues.jboss.org/browse/WFLY-3483 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.1.0.Final > > > It is possible to configure the web ssl connector to use the Windows certificate keystore (access provided by the SunMSCAPI provider). However, the JSSESocketFactory checks for a keystore file. This check should likely be skipped when the connector is configured to use the Windows keystore. > Here is what the configuration looks like: > {noformat} > <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"> > <ssl name="https" > key-alias="jbossweb" > keystore-type="Windows-MY" > protocol="TLSv1" > </connector> > {noformat} > This results in an error like this: > 13:54:01,821 ERROR [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003043: Error initializing endpoint: java.io.FileNotFoundException: C:\Users\imauser\.keystore (The system cannot find the file specified) > You can work around this issue by creating this keystore (C:\Users\imauser\.keystore). > More info on using the Windows keystores can be found here: > http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProvide... > http://www.oracle.com/technetwork/articles/javase/security-137537.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2016