[JBoss JIRA] (ELY-645) Unable to remove elytron subsystem with defined properties-realm
by Bartosz Baranowski (JIRA)
Bartosz Baranowski created ELY-645:
--------------------------------------
Summary: Unable to remove elytron subsystem with defined properties-realm
Key: ELY-645
URL: https://issues.jboss.org/browse/ELY-645
Project: WildFly Elytron
Issue Type: Bug
Reporter: Bartosz Baranowski
Assignee: Darran Lofthouse
When having elytron subsystem with only defined property-realm and calling remove on the subsystem, it fails due unsatisfied dependencies [1]. The subsystem is created from scratch with no dependencies outside of the subsystem => it shouldn't fail to remove.
[1]
[standalone@localhost:9990 /] /subsystem=elytron:remove
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service elytron.security-properties was depended upon by service org.wildfly.security.security-realm.elytron-security
Service elytron.core-service was depended upon by service org.wildfly.security.security-realm.elytron-security",
"rolled-back" => true
}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JGRP-2102) bind_interface="eth0" and bind_addr="LINK_LOCAL" config are conflict
by 俐佳 张 (JIRA)
俐佳 张 created JGRP-2102:
--------------------------
Summary: bind_interface="eth0" and bind_addr="LINK_LOCAL" config are conflict
Key: JGRP-2102
URL: https://issues.jboss.org/browse/JGRP-2102
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.1
Environment: [root@wtc2k01v27 ~] CLONE # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 2606:ae00:e200:3f::83/128 scope global
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:50:56:ab:2a:ea brd ff:ff:ff:ff:ff:ff
inet 107.250.167.28/25 brd 107.250.167.127 scope global eth0
inet6 2606:ae00:e200:3f::28/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feab:2aea/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:50:56:ab:d6:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.59/24 brd 192.168.0.255 scope global eth1
inet6 fe80::250:56ff:feab:d612/64 scope link
valid_lft forever preferred_lft forever
There're eth0 and eth1 exists in the environment
Reporter: 俐佳 张
Assignee: Bela Ban
Attachments: jgroups-udp.xml
Error happens while
Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000085: Error while trying to create a channel using the specified configuration file: /opt/oss/NSN-icf_notification_dispatcher/conf/jgroups-udp.xml
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:406)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannel(JGroupsTransport.java:307)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:351)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:188)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:226)
... 26 more
Caused by: java.lang.Exception: Property assignment of bind_interface in UDP with original property value eth0 and converted to null could not be assigned
at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1153)
at org.jgroups.stack.Configurator.createLayer(Configurator.java:444)
at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398)
at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90)
at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477)
at org.jgroups.JChannel.init(JChannel.java:854)
at org.jgroups.JChannel.<init>(JChannel.java:159)
at org.jgroups.JChannel.<init>(JChannel.java:129)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:404)
... 39 more
Caused by: java.lang.Exception: Conversion of bind_interface in UDP with original property value eth0 failed
at org.jgroups.conf.PropertyHelper.getConvertedValue(PropertyHelper.java:84)
at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1147)
... 48 more
Caused by: java.lang.mail(a)example.comIllegalArgumentException: network interface eth0 does not contain address fe80:0:0:0:250:56ff:feab:d612%3
at org.jgroups.util.Util.validateBindAddressFromInterface(Util.java:3132)
bind_interface="eth0" and bind_addr="LINK_LOCAL" config are config at the same time
but it couldn't get the eth0 link local address but return eth1 link local address
This code return the first address that match
jgroups-3.6.1.Final-sources\org\jgroups\util\Util.java
public static InetAddress getAddress(AddressScope scope) ----> scope is LINK_LOCAL
throws SocketException
{
InetAddress address = null;
Enumeration intfs = NetworkInterface.getNetworkInterfaces();
while (intfs.hasMoreElements()) {
NetworkInterface intf = (NetworkInterface)intfs.nextElement();
try {
if (intf.isUp()) {
address = getAddress(intf, scope); -------> It will return the first LINK_LOCAL address from NICs list
if (address != null)
return address;
}
}
catch (SocketException e) {
}
}
return null;
}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7233) Add ExtendedJBossXATerminator service to the transactions subsystem
by Gytis Trikleris (JIRA)
Gytis Trikleris created WFLY-7233:
-------------------------------------
Summary: Add ExtendedJBossXATerminator service to the transactions subsystem
Key: WFLY-7233
URL: https://issues.jboss.org/browse/WFLY-7233
Project: WildFly
Issue Type: Enhancement
Components: Transactions
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 11.0.0.Alpha1
ExtendedJBossXATerminator from Narayana SPI is not currently injectable as a service. However, it is needed to check if the specific transaction is available in the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7212) Cannot use BMT in @Schedule service
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7212?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-7212:
--------------------------------------
The Schedule method is on a different bean, so it will start a transaction. The transaction will then time out and an exception will be thrown when it is commited. You need both beans to use BMT.
> Cannot use BMT in @Schedule service
> -----------------------------------
>
> Key: WFLY-7212
> URL: https://issues.jboss.org/browse/WFLY-7212
> Project: WildFly
> Issue Type: Feature Request
> Components: EE, EJB, Transactions
> Affects Versions: 10.0.0.Final, 10.1.0.Final
> Environment: Wildfly 10.1.0-Final. Windows 10. MySql 5.5.
> Reporter: Karl Nicholas
> Labels: arjuna, ejb, scheduled, scheduled_tasks, transaction
>
> When injecting a `@Resource private UserTransaction tx;`, a `TransactionReaper` terminates kills my `UserTransaction` after 5 minutes no matter what. Since it's a batch update, I need more than 5 minutes.
> Here is a simple piece of code that doesn't work:
> {code:java}
> @EJB private TestFiveMinuteBatch testFiveMinuteBatch;
> @Schedule(second="0", minute="8", hour="10", persistent=false) // 03:30 am (12:30 am CA ) every day
> public void updateTest() {
> testFiveMinuteBatch.test();
> }
> @Stateless
> @TransactionManagement(TransactionManagementType.BEAN)
> public class TestFiveMinuteBatch {
> @Resource private UserTransaction tx;
> public void test() {
> for ( int i=0; i < 6; ++i ) {
> System.out.println("Minute: " + i);
> try {
> Thread.sleep(60000);
> } catch (InterruptedException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
> }
> }
> }
> {code}
> After 5 minutes I get this warning:
> {noformat}
> 10:13:00,034 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffac1f6209:-595568e4:57e80419:e in state RUN
> 10:13:00,039 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffac1f6209:-595568e4:57e80419:e
> 10:13:00,130 INFO [stdout] (EJB default - 1) Minute: 5
> {noformat}
> After service terminates I get this error:
> {noformat}
> 10:14:00,131 WARN [com.arjuna.ats.arjuna] (EJB default - 1) ARJUNA012077: Abort called on already aborted atomic action 0:ffffac1f6209:-595568e4:57e80419:e
> 10:14:00,163 ERROR [org.jboss.as.ejb3.timer] (EJB default - 1) WFLYEJB0020: Error invoking timeout for timer: [id=8a8f4546-28d0-491e-85a6-f668f58ab5dc timedObjectId=opca-ear.opca-ejb.ScheduledService auto-timer?:true persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@31fe8c3e initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Mon Sep 26 10:08:00 PDT 2016 timerState=IN_TIMEOUT info=null]: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:137)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:117)
> at org.jboss.as.ejb3.tx.TimerCMTTxInterceptor.endTransaction(TimerCMTTxInterceptor.java:67)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:279)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:110)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99)
> at org.jboss.as.ejb3.timerservice.CalendarTimerTask.invokeBeanMethod(CalendarTimerTask.java:64)
> at org.jboss.as.ejb3.timerservice.CalendarTimerTask.callTimeout(CalendarTimerTask.java:53)
> at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:157)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1215)
> 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)
> Caused by: javax.transaction.RollbackException: WFLYEJB0447: Transaction 'TransactionImple < ac, BasicAction: 0:ffffac1f6209:-595568e4:57e80419:e status: ActionStatus.ABORTED >' was already rolled back
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:98)
> ... 38 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-7209:
---------------------------------------
I'm not sure I'm following 100%. Resource adapters could be activate in 2 different way:
# w/ an entry in resource-adapters subsystem configuration
# w/ ironjacamar.xml file in the rar archive
in the first case you have all configuration and stats under its resource-adpater entry in DMR.
In the second case you have all readonly attribute and stats under /deployment=<rar-name>. For example this is a valid command :
/deployment=amq-ij.rar/subsystem=resource-adapters/ironjacamar=ironjacamar/resource-adapter=amq-ij.rar:read-resource()
If you are not in one of those 2 cases the rar is not activated and in fact it's just a library deployment until it will be activated w/ a valid configuration.
I don't understand what else you need, but maybe I'm not getting your use case. Could you explain a bit further?
S.
> Operation to list installed Resource Adapters
> ---------------------------------------------
>
> Key: WFLY-7209
> URL: https://issues.jboss.org/browse/WFLY-7209
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Guillermo González de Agüero
> Assignee: Stefano Maestri
> Fix For: 10.1.0.Final
>
>
> Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time.
> I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them.
> The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list()
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (DROOLS-1311) PDF asciidoc generation
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1311:
----------------------------------------
Summary: PDF asciidoc generation
Key: DROOLS-1311
URL: https://issues.jboss.org/browse/DROOLS-1311
Project: Drools
Issue Type: Feature Request
Components: docs
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Using approach from optaplanner-docs in asciidoc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7206) Graceful Shutdown and Quiescing for Transactions
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/WFLY-7206?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris closed WFLY-7206.
---------------------------------
Fix Version/s: (was: 11.0.0.Alpha1)
Resolution: Duplicate Issue
> Graceful Shutdown and Quiescing for Transactions
> ------------------------------------------------
>
> Key: WFLY-7206
> URL: https://issues.jboss.org/browse/WFLY-7206
> Project: WildFly
> Issue Type: Feature Request
> Components: Server, Transactions, Web Console, XTS
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Critical
>
> * During the quiesce period - the server component will not accept new requests.
> * Components of the server will support controlled shutdown or quiescence - ie. In-flight transactions and requests will be serviced before the shutdown.
> This also implies eing able to control all request paths - HTTP (via mod_cluster), JMS and RMI (via smart proxies).
> * The Quiesce operation will accept a timeout which will indicate the maximum period that a shutdown will wait for in-flight requests / transactions to complete. After the timeout expires the server component will shutdown immediately.
> * It applies to servers that are started with all supported server profiles (i.e. default, default-ha, full and full-ha) in both standalone and domain modes.
> * In a clustered environment if a node in cluster is on graceful shutdown, the other node(s) in the cluster should not log warnings, but infos (or debug or nothing) because this is a normal situation (Ref: PRODMGT-815)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months