[JBoss JIRA] (JBJCA-1285) rar-info: CCI interface information missing
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBJCA-1285:
--------------------------------------
Summary: rar-info: CCI interface information missing
Key: JBJCA-1285
URL: https://issues.jboss.org/browse/JBJCA-1285
Project: IronJacamar
Issue Type: Bug
Components: AS
Reporter: Jesper Pedersen
Assignee: Johnathon Lee
Fix For: 1.26
If a resource adapter is using CCI then the ConnectionFactory and Connection information isn't included in the report.
The information should be based directly on the actual interface classes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JGRP-809) Copyless stack
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-809?page=com.atlassian.jira.plugin.s... ]
Bela Ban updated JGRP-809:
--------------------------
Attachment: Buf.java
BufAllocator.java
Added Buf and BufAllocator, will be renamed to Buffer (replacing the Buffer class)
> Copyless stack
> --------------
>
> Key: JGRP-809
> URL: https://issues.jboss.org/browse/JGRP-809
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: Buf.java, BufAllocator.java, Message.java
>
>
> Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can
> - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to)
> - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return
> - each thread in the pool has its own buffer into which the buffer is read from the socket
> Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JGRP-809) Copyless stack
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-809?page=com.atlassian.jira.plugin.s... ]
Bela Ban updated JGRP-809:
--------------------------
Attachment: Message.java
Added setBuffer() / getBuffer() based on Buf
> Copyless stack
> --------------
>
> Key: JGRP-809
> URL: https://issues.jboss.org/browse/JGRP-809
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: Message.java
>
>
> Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can
> - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to)
> - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return
> - each thread in the pool has its own buffer into which the buffer is read from the socket
> Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JGRP-1946) Auth succeeds when the node without auth starts first
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1946?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1946:
---------------------------
Fix Version/s: 3.6.5
> Auth succeeds when the node without auth starts first
> -----------------------------------------------------
>
> Key: JGRP-1946
> URL: https://issues.jboss.org/browse/JGRP-1946
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.6.4
> Environment: jdk 1.7
> Reporter: fatih fatih
> Assignee: Bela Ban
> Fix For: 3.6.5
>
> Attachments: HAController2.java, udp.xml, udp.xml
>
>
> Node starts without auth it becomes coordinator of its cluster
> In the same cluster another node starts with X509 Auth
> The node starting with auth succeeds to join to the cluster that is started by the first node instead of creating its own cluster.
> The purpose is not to allow the nodes that is with auth and the nodes that is without auth to join with each other.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4956) Automatically enable Hibernate Search in deployments and allow override properties
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-4956?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on WFLY-4956:
---------------------------------------
Discussed this further in chats, and decided:
= use the "wildfly.jpa.hibernate.search.module" property name, as the project name is Hibernate Search and it's not just "the Search component of Hibernate" (the previous proposal is confusing in terms of branding)
= keep the 'auto' option, as that's very handy for people who do variable injection in their configuration files
> Automatically enable Hibernate Search in deployments and allow override properties
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4956
> URL: https://issues.jboss.org/browse/WFLY-4956
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Sanne Grinovero
> Assignee: Scott Marlow
>
> In case a deployment is using Hibernate ORM - either native Hibernate APIs or JPA - we should check if Hibernate Search also needs to be made available to the deployment (the *application classpath*).
> * if any entity class has the `(a)org.hibernate.search.annotations.Indexed` annotation
> * and/or if the persistence.xml has a any configuration property matching `hibernate.search.*`.
> If either of these is true, *and* the default Hibernate ORM module is being added as well, then we should also add the module {{org.hibernate.search.orm:main}}.
> If the user is overriding the Hibernate ORM version, then we shall not add this dependency either as the org.hibernate.search.orm:main module strictly refers and imports the module {{org.hibernate:main}}.
> In all cases, the user should be able to override the deployer decision using a configuration property defined in the persistence unit
> {{wildfly.jpa.hibernate.search.includedSlot}}
> * if not present, use the automatic decision rules described above, and possibly log the action being taken
> * if set to `none`, do not include Hibernate Search
> * if set to `auto`, will behave like not having set the property
> * if set to something else, use it as a slot name for the module you
> will depend on
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-3355) MDB fails to deploy on reload
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3355?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil reassigned WFLY-3355:
---------------------------------
Assignee: Jeff Mesnil (was: Stuart Douglas)
> MDB fails to deploy on reload
> -----------------------------
>
> Key: WFLY-3355
> URL: https://issues.jboss.org/browse/WFLY-3355
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMS
> Affects Versions: 10.0.0.Alpha4
> Environment: Windows 7, 64bit
> Reporter: Bart Van Dosselaer
> Assignee: Jeff Mesnil
> Attachments: leak-0.0.1-SNAPSHOT.jar
>
>
> When an MDB is deployed and a :reload command is issues, the application server fails to deploy this MDB.
> Stacktrace:
> {noformat}
> 2014-05-14 16:11:22,284 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 57) MSC000001: Failed to start service jboss.deployment.unit."wildfly-helloworld-mdb.war".component.HelloWorldQueueMDB.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-helloworld-mdb.war".component.HelloWorldQueueMDB.START: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-8.1.0.CR2.jar:8.1.0.CR2]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_55]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> Caused by: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:215)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:186)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-8.1.0.CR2.jar:8.1.0.CR2]
> ... 6 more
> Caused by: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
> at org.jboss.jca.core.workmanager.WorkManagerImpl.doFirstChecks(WorkManagerImpl.java:776) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final]
> at org.jboss.jca.core.workmanager.WorkManagerImpl.scheduleWork(WorkManagerImpl.java:617) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final]
> at org.jboss.jca.core.workmanager.WorkManagerImpl.scheduleWork(WorkManagerImpl.java:602) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final]
> at org.hornetq.ra.inflow.HornetQActivation.start(HornetQActivation.java:264) [hornetq-ra-2.4.1.Final.jar:]
> at org.hornetq.ra.HornetQResourceAdapter.endpointActivation(HornetQResourceAdapter.java:166) [hornetq-ra-2.4.1.Final.jar:]
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:191) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final]
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:213)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months