[JBoss JIRA] (WFCORE-49) Limit deployment scanner to a list of deployments
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-49?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet reassigned WFCORE-49:
---------------------------------------
Assignee: ehsavoie Hugonnet
> Limit deployment scanner to a list of deployments
> -------------------------------------------------
>
> Key: WFCORE-49
> URL: https://issues.jboss.org/browse/WFCORE-49
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Deployment Scanner, Domain Management
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
> Priority: Minor
>
> The basic scenario here is there's a file /some/path/to/foo.war that users want deployed via a scanner, but /some/path/to includes other files that can't be moved and that should not be scanned. There's no way to limit the scanner to foo.war and related marker files.
> Allowing configuration of an explicit white list of (non-marker) files to consider, and/or a black list of ones to ignore, would allow this use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-5242) Inconsistent format for IPv6 addresses in server log
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5242?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-5242:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1258298|https://bugzilla.redhat.com/show_bug.cgi?id=1258298] from POST to MODIFIED
> Inconsistent format for IPv6 addresses in server log
> ----------------------------------------------------
>
> Key: WFLY-5242
> URL: https://issues.jboss.org/browse/WFLY-5242
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Beta2
> Reporter: Lyle Wang
> Assignee: Chao Wang
> Priority: Minor
> Fix For: 10.0.0.CR1
>
>
> Description of problem:
> When IPv6 is used, square brackets for IPv6 addresses are missed in some of log entries. Specifically, the address format from Undertow logs is different from those "WFLYSRV" logs.
> How reproducible:
> Always
> Steps to Reproduce:
> 1. Config IPv6 (example: https://docs.jboss.org/author/display/WFLY10/Interfaces+and+ports)
> 2. Start WildFly and check the log
> Actual results:
> ----------------------------------------
> 2015-08-31 12:51:47,812 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /0:0:0:0:0:0:0:1:8080
> ......
> 2015-08-31 12:51:48,431 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9993/management
> 2015-08-31 12:51:48,432 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9993
> ----------------------------------------
> In Undertow logs it's like "/0:0:0:0:0:0:0:1:8080" but in WildFly server logs "http://[::1]:9993/management"
> Expected results:
> Consistent format should be used for IPv6 address across different components and the address is enclosed in square brackets [ ].
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-5478) allow custom scoped persistence unit name hint in persistence unit definition
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5478?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-5478:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1262401|https://bugzilla.redhat.com/show_bug.cgi?id=1262401] from POST to MODIFIED
> allow custom scoped persistence unit name hint in persistence unit definition
> -----------------------------------------------------------------------------
>
> Key: WFLY-5478
> URL: https://issues.jboss.org/browse/WFLY-5478
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Final, 9.0.0.Final, 10.0.0.CR2
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 10.0.0.CR3
>
>
> Consider allowing applications to override the scoped persistence unit name, so instead of using names like "test2.ear/w2.war#warPUnit_PU", the application can specify a unique (across all deployments on the app server) name.
> The idea is that application deployments can include a persistence unit hint "jboss.as.jpa.scopedname" that specifies the unique scoped persistence unit name that will be used for several internal settings (e.g. hibernate.cache.region_prefix will be set to the scopedname value unless the application specifies a different hibernate.cache.region_prefix value).
> The WildFly management console does not yet work with applications that specify the jboss.as.jpa.scopedname. Once this change is merged to WildFly, a management console change should be requested.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (AS7-4441) JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4441?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4441:
----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1262401|https://bugzilla.redhat.com/show_bug.cgi?id=1262401] from POST to MODIFIED
> JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss
> -----------------------------------------------------------------------------
>
> Key: AS7-4441
> URL: https://issues.jboss.org/browse/AS7-4441
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX, JPA / Hibernate, Server
> Affects Versions: 7.1.1.Final
> Environment: Windows Vista 64 bit, JDK 1.6.0_18
> Reporter: Osten Forshed
> Assignee: Scott Marlow
> Priority: Minor
> Fix For: 7.1.2.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> If a web app is deployed (standalone) with a persistence.xml containing:
> <property name="hibernate.cache.region_prefix" value=""/>
> Then it is not possible to connect to the MBean Server with JConsole using instructions here:
> https://community.jboss.org/wiki/UsingJconsoleToConnectToJMXOnAS7
> Following stack trace is written to JBoss log:
> 12:27:03,406 WARN [org.jboss.remotingjmx.protocol.v1.ServerProxy] (pool-5-thread-16) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.queryNames(ModelControllerMBeanHelper.java:136)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.queryNames(ModelControllerMBeanServerPlugin.java:124)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:280)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$QueryNamesHandler.handle(ServerProxy.java:1197)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_18]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_18]
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_18]
> If property is removed from persistence.xml it is possible to connect using JConsole and browse the MBeans.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6528) Server is unable to invoke @Timeout method after 10 methods are called on Asynchronous bean on IBM JDK
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-6528?page=com.atlassian.jira.plugin.... ]
Stuart Douglas moved JBEAP-4228 to WFLY-6528:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6528 (was: JBEAP-4228)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Target Release: (was: 7.backlog.GA)
> Server is unable to invoke @Timeout method after 10 methods are called on Asynchronous bean on IBM JDK
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6528
> URL: https://issues.jboss.org/browse/WFLY-6528
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
>
> *Description of problem:*
> Server is unable to invoke @Timeout method after 10 methods are called on Asynchronous bean
> Test:
> {code:java}
> for (int i = 0; i < 10; i++) {
> AsyncBean bean = lookup(AsyncBean.class);
> bean.asyncMethod();
> }
> InitialContext iniCtx = new InitialContext();
> TimeoutBean bean = (TimeoutBean) iniCtx.lookup("java:module/" + TimeoutBean.class.getSimpleName());
> bean.createTimer();
> {code}
> Asynchronous bean:
> {code:java}
> @Stateless
> @Asynchronous
> @LocalBean
> public class AsyncBean{
> public void asyncMethod() {
> System.out.println("asynch bean execution");
> }
> }
> {code}
> Timeout bean:
> {code:java}
> @Stateless
> public class TimeoutBean {
> @Resource
> private TimerService timerService;
> public void createTimer() {
> timerService.createTimer(100, null);
> }
> @Timeout
> private void timeout(Timer timer) {
> System.out.println("in timeout method");
> }
> }
> {code}
> *How reproducible:*
> Always on IBM JDK
> *Steps to Reproduce: (use attached reproducer)*
> # get fresh EAP
> # mvn test -Djboss.home=$\{EAP_HOME\}
> *Actual results:*
> {noformat}
> 12:26:57,462 ERROR [org.jboss.as.ejb3] (EJB default - 9) WFLYEJB0164: Exception running timer task for timer [id=03aa7a93-ee6f-483e-bf6b-caff56a13fc0 timedObjectId=test.test.TimeoutBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@f1cd0789 initialExpiration=Mon Apr 11 12:26:57 CEST 2016 intervalDuration(in milli sec)=0 nextExpiration=null timerState=IN_TIMEOUT info=null] on EJB test.test.TimeoutBean: java.lang.RuntimeException: javax.xml.stream.FactoryConfigurationError: Provider __redirected.__XMLOutputFactory not found
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:614)
> at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:148)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1214)
> at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: javax.xml.stream.FactoryConfigurationError: Provider __redirected.__XMLOutputFactory not found
> at javax.xml.stream.XMLOutputFactory.newFactory(Unknown Source)
> at javax.xml.stream.XMLOutputFactory.newInstance(Unknown Source)
> at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.writeFile(FileTimerPersistence.java:497)
> at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.persistTimer(FileTimerPersistence.java:225)
> at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.persistTimer(FileTimerPersistence.java:193)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:609)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: __redirected.__XMLOutputFactory
> at java.lang.Class.forNameImpl(Native Method)
> at java.lang.Class.forName(Class.java:273)
> at javax.xml.stream.FactoryFinder.newInstance(Unknown Source)
> at javax.xml.stream.FactoryFinder.find(Unknown Source)
> at javax.xml.stream.FactoryFinder.find(Unknown Source)
> ... 13 more
> {noformat}
> *Expected results:*
> No exception on output
> *Additional info:*
> Number of EJB call depends on max-threads attribute of EJB3 subsystem. It can be configured by this CLI command:
> {noformat}
> /subsystem=ejb3/thread-pool=default:write-attribute(name=max-threads,value=10)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1129) osgi bundle have wrong metadata info
by Hiep Lq (JIRA)
Hiep Lq created DROOLS-1129:
-------------------------------
Summary: osgi bundle have wrong metadata info
Key: DROOLS-1129
URL: https://issues.jboss.org/browse/DROOLS-1129
Project: Drools
Issue Type: Bug
Components: integration
Affects Versions: 6.4.0.Final
Reporter: Hiep Lq
Assignee: Mario Fusco
1. bundle reteoo have wrong Bundle-SymbolicName.
now is Bundle-SymbolicName: org.drools.core
it should is Bundle-SymbolicName: org.drools.reteoo
2. base in standard of P2 repository. almost source bundle have wrong value at Bundle-SymbolicName and Eclipse-SourceBundle
example:drools-compiler-6.4.0.Final-sources
current value of: Bundle-SymbolicName = drools-compiler.source
should be:Bundle-SymbolicName = org.drools.compiler.source
current value of: Eclipse-SourceBundle=drools-compiler
should be:Eclipse-SourceBundle=org.drools.compiler
or we can keep source bundle, and change at binary bundle
example change Bundle-SymbolicName of org.drools.compiler to drools-compiler
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6527) Cannot lookup RemoteConnectionFactory using https-remoting
by George Turner (JIRA)
George Turner created WFLY-6527:
-----------------------------------
Summary: Cannot lookup RemoteConnectionFactory using https-remoting
Key: WFLY-6527
URL: https://issues.jboss.org/browse/WFLY-6527
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 10.0.0.Final
Environment: RedHat Linux, Java 1.8
Reporter: George Turner
Assignee: David Lloyd
I have successfully configured the system for two way ssl. I can connect to a topic from a standalone client, but I cannot connect with the same code from an EJB client using the following:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
ctx = new InitialContext(props);
ConnectionFactory cf = (ConnectionFactory) ctx.lookup("jms/RemoteConnectionFactory");
It seems to "attach" the stateless bean to the first remote instance and then the second remote instance lookup fails. I have tried using the EJBClientContext properties (as used for EJB lookups) but no help. There is VERY little documentation about using https-remoting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years