[JBoss JIRA] (WFLY-6617) Cannot inject session bean with @EJB to JSF PhaseListener
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-6617?page=com.atlassian.jira.plugin.... ]
Dmitrii Tikhomirov reassigned WFLY-6617:
----------------------------------------
Assignee: Dmitrii Tikhomirov (was: Farah Juma)
> Cannot inject session bean with @EJB to JSF PhaseListener
> ---------------------------------------------------------
>
> Key: WFLY-6617
> URL: https://issues.jboss.org/browse/WFLY-6617
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.0.0.Final
> Reporter: Tomas Remes
> Assignee: Dmitrii Tikhomirov
>
> Having something like following:
> {code}
> public class TestPhaseListener implements PhaseListener{
> @EJB
> TestEJB testEJB;
> ....
> }
> {code}
> result to null. Note that CDI injection works. Reading {{5.4.1
> JSF Managed Classes and Java EE Annotations}} in JSF spec I think this should work as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6966) FatalError on Transaction Expired Entry Monitor during server shutdown
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-6966?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-6966:
--------------------------------
Issue Type: Enhancement (was: Bug)
> FatalError on Transaction Expired Entry Monitor during server shutdown
> ----------------------------------------------------------------------
>
> Key: WFLY-6966
> URL: https://issues.jboss.org/browse/WFLY-6966
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP, Transactions
> Affects Versions: 10.1.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Minor
>
> I do experience intermittent errors being shown in server log during server shutdown. It happens time to time for server configured to use {{JTS}} transaction that {{Transaction Expired Entry Monitor}} shows {{FatalError}} during container shutdown.
> I do experience this failure when jdbc object store is used.
> The shutdown log looks
> {code}
> 2016-08-16 07:07:46,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment wmq.jmsra.rar (runtime-name: wmq.jmsra.rar) in 132ms
> 2016-08-16 07:07:46,914 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> 2016-08-16 07:07:46,914 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 2016-08-16 07:07:46,915 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
> 2016-08-16 07:07:46,921 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 2016-08-16 07:07:46,924 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment crashrecovery-jms-stateless-cmt.jar (runtime-name: crashrecovery-jms-stateless-cmt.jar) in 156ms
> 2016-08-16 07:07:46,947 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 16) WFLYCLINF0003: Stopped client-mappings cache from ejb container
> 2016-08-16 07:07:46,952 TRACE [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) InputObjectState::InputObjectState(0:ffff7f000001:55f44a88:57b2ec0b:8, Recovery/FactoryContact)
> 2016-08-16 07:07:46,959 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 32) AMQ151003: resource adaptor stopped
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) ORB::shutdown ()
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) OA::destroyRootPOA ()
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) RootOA::shutdownObject (Servant)
> 2016-08-16 07:07:46,962 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032018: Destroying TransactionManagerService
> 2016-08-16 07:07:46,963 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032014: Stopping transaction recovery manager
> 2016-08-16 07:07:47,000 FATAL [com.arjuna.ats.jts] (Transaction Expired Entry Monitor) ARJUNA022006: The ORB has not been initialized yet
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) Exception in thread "Transaction Expired Entry Monitor" com.arjuna.ats.arjuna.exceptions.FatalError
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.ORBManager.getORB(ORBManager.java:56)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restore_state(FactoryContactItem.java:264)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restoreMe(FactoryContactItem.java:320)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.recreate(FactoryContactItem.java:100)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.ExpiredContactScanner.scan(ExpiredContactScanner.java:99)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:171)
> 2016-08-16 07:07:47,001 DEBUG [com.arjuna.ats.arjuna] (Listener:4712) Recovery listener existing com.arjuna.ats.internal.arjuna.recovery.WorkerService
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: Mode <== TERMINATED
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown waiting for scan to end
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: scan TERMINATED at phase 1
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== INACTIVE
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread exiting
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown scan wait complete
> 2016-08-16 07:07:47,003 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0010: Unbound data source [java:jboss/datasources/jdbc-store]
> 2016-08-16 07:07:47,006 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = module_postgresql-9.4.1207.jar
> 2016-08-16 07:07:47,012 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 32) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.SP16-redhat-1 [023d1e88-638c-11e6-927a-a180c25082cf] stopped
> 2016-08-16 07:07:47,012 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
> 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0004: Undertow 1.3.21.Final-redhat-1 stopping
> 2016-08-16 07:07:47,018 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 250ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Marek Kopecký edited comment on WFCORE-1738 at 8/30/16 9:46 AM:
----------------------------------------------------------------
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: {{version}}
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
was (Author: mkopecky):
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: version
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-1738:
---------------------------------------
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: version
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky commented on WFCORE-1738:
-------------------------------------------
Could you please also post the CLI command you used to apply the patch and its output? Thanks.
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-835) @Resource UserTransaction error when file passivation store is selected
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-835?page=com.atlassian.jira.plugin.s... ]
Kabir Khan commented on WFLY-835:
---------------------------------
[~mmusgrov] I'm not resolving this one since I only merged PR 9137. If that is wrong, please go ahead and resolve for 11.0.0.Alpha1
> @Resource UserTransaction error when file passivation store is selected
> -----------------------------------------------------------------------
>
> Key: WFLY-835
> URL: https://issues.jboss.org/browse/WFLY-835
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.CR2
> Environment: Ubuntu 11.10, Intel® Core™ i3-2120 CPU @ 3.30GHz × 4
> Reporter: Abraham Cabanillas Piera
> Assignee: Michael Musgrove
> Priority: Critical
> Labels: jboss
> Attachments: serializationerr_server.log
>
>
> The following exception is launched when the server tries to passivate into the file passivation storage a stateful EJB session with UserTransaction injected as a resource:
> {noformat}
> [org.jboss.as.ejb3.cache.spi.impl.PassivateTask] (pool-10-thread-1) JBAS014538: Failed to passivate {[-36, 0, 14, -43, 72, 10, 76, -28, -105, -108, 24, 45, -70, -58, -48, -107]}: java.lang.RuntimeException: JBAS014538: Failed to passivate {[-36, 0, 14, -43, 72, 10, 76, -28, -105, -108, 24, 45, -70, -58, -48, -107]}
> at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:248) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:52) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.impl.backing.SimpleBackingCacheEntryStore.passivate(SimpleBackingCacheEntryStore.java:155) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:288) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:50) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:60) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.cache.spi.impl.PassivateTask.run(PassivateTask.java:45) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_13]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_13]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_13]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_13]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.io.NotSerializableException: org.jboss.tm.usertx.client.ServerVMClientUserTransaction
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:891)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:69)
> at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:60)
> at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:54)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342) [rt.jar:1.7.0_13]
> at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberImpl.writeObject(SerializationGroupMemberImpl.java:368) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_13]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_13]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_13]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_13]
> at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:175)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:239) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> ... 15 more
> Caused by: an exception which occurred:
> in field userTransaction
> in field instance
> in field instance
> in object org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberImpl@6a4de0c9
> {noformat}
> The EJB subsystem configuration is:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:ejb3:1.2">
> <session-bean>
> <stateless>
> <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
> </stateless>
> <stateful default-access-timeout="10000" cache-ref="passivating"/>
> <singleton default-access-timeout="5000"/>
> </session-bean>
> <mdb>
> <resource-adapter-ref resource-adapter-name="hornetq-ra"/>
> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
> </mdb>
> <pools>
> <bean-instance-pools>
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="50" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
> <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
> </bean-instance-pools>
> </pools>
> <caches>
> <cache name="simple" aliases="NoPassivationCache"/>
> <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
> </caches>
> <passivation-stores>
> <file-passivation-store name="file" idle-timeout="10" idle-timeout-unit="SECONDS"/>
> </passivation-stores>
> <async thread-pool-name="default"/>
> <timer-service thread-pool-name="default">
> <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
> </timer-service>
> <remote connector-ref="remoting-connector" thread-pool-name="default"/>
> <thread-pools>
> <thread-pool name="default">
> <max-threads count="100"/>
> <keepalive-time time="100" unit="milliseconds"/>
> </thread-pool>
> </thread-pools>
> <iiop enable-by-default="false" use-qualified-name="false"/>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service
by Arthur Borsboom (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ]
Arthur Borsboom commented on WFCORE-1719:
-----------------------------------------
This bug seems still to exist in Wildfly 10.1.0-Final.
The quotes are still in:
docs/contrib/scripts/service/service.bat
Removing them *before* installing the service is the key to get it working.
> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
> Key: WFCORE-1719
> URL: https://issues.jboss.org/browse/WFCORE-1719
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.2.0.Final
> Environment: Windows 8/Windows Server 2012
> Oracle Java 8
> Reporter: Anton Yudin
> Assignee: Tomaz Cerar
> Fix For: 3.0.0.Alpha6
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error:
> Incorrect function.
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
> <EventID Qualifiers="49152">7024</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8080000000000000</Keywords>
> <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
> <EventRecordID>196500</EventRecordID>
> <Correlation/>
> <Execution ProcessID="668" ThreadID="10184"/>
> <Channel>System</Channel>
> <Computer>ITPC7.intra.rfgh.net</Computer>
> <Security/>
> </System>
> -
> <EventData>
> <Data Name="param1">Wildfly</Data>
> <Data Name="param2">%%1</Data>
> <Binary>570069006C00640066006C0079000000</Binary>
> </EventData>
> </Event>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1221) Add fail-safe and scalability functionality to the Drools (CEP) rules engine
by Tom Pijl (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1221?page=com.atlassian.jira.plugi... ]
Tom Pijl commented on DROOLS-1221:
----------------------------------
Thanks [~youcefhilem] for these pointers.
The examples referenced in your first comment solves the high availability requirement at the cost of Rules flexibility (insert, update and delete facts are not allowed), but it didn't address the (horizontal) scalability requirement: distributing work over multiple engines. A solution is mentioned in the slide set: implementing Event partitioning, but the examples did notshow this.
I am still going through the project you referenced in your second comment....
> Add fail-safe and scalability functionality to the Drools (CEP) rules engine
> ----------------------------------------------------------------------------
>
> Key: DROOLS-1221
> URL: https://issues.jboss.org/browse/DROOLS-1221
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: Drools (CEP) Rule engine 6.4.0.Final
> Reporter: Tom Pijl
> Assignee: Mario Fusco
>
> The Drools Rule engine is currently not fail-safe and scalable which is a requirement for Cloud deployment.
> Add a possibility to persist the state of the working memory after each state change (perhaps linked to the fireAllRules()?) and related to that the possibility to restore the state in case of a crash (fail-safe requirement).
> This persistent state store can also be used to synchronize multiple engine instances (scalability requirement).
> Of course this has major impact on the performance of the engine, but it is the only way to make the engine useful in a multi-tenant Cloud environment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months