[JBoss JIRA] (AS7-6419) Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
by Rainer Pfannkuch (JIRA)
[ https://issues.jboss.org/browse/AS7-6419?page=com.atlassian.jira.plugin.s... ]
Rainer Pfannkuch commented on AS7-6419:
---------------------------------------
Hello Stefano,
I'm a collegue from Martin Keller.
We still have the same problems running our tests (Validation exception). I will change my application to remove your NoClassDefFoundError: Lnet/fsc/tpbasics/logging/BCLog and send you an update soon.
> Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6419
> URL: https://issues.jboss.org/browse/AS7-6419
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Environment: Configuration:
> JDK-Version: 1.6.0_33
> Operating System: Windows 7 (32 Bit)
> JBoss Application Server jboss-as-7.2.0.Alpha1-SNAPSHOT (build Dec. 19th 2012)
> JDK-Version: 1.6.0_33
> Resource Adapter: BeanConnect 3.0 developed by our Company (Fujitsu)
> Reporter: Martin Keller
> Assignee: Stefano Maestri
>
> Tbis Problem was reported before see https://issues.jboss.org/browse/AS7-6384, but now the components to reproduce it is included.
> Starting an application using our JCA 1.6 resource adapter fails with
> java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> It works ok in the JBoss JCA 1.5 environment and on other application servers with JCA1.6 environment:
> GlassFish OS Edition 3, IBM WebSphere 8.0 and WebLogic 12.
> Questions:
> What could be the cause for this exception?
> Can we switch off the validation?
> What is missing to run the validation successful?
> Details:
> The full stack is:
> 15:04:02,128 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 64) MSC00001: Failed to start service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:177)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 7 more
> Caused by: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:147)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:175)
> ... 8 more
> Caused by: javax.validation.ValidationException: Unable to find a default provider
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) [validation-api-1.0.0.GA.jar:]
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:135)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-5498) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-5498?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky commented on AS7-5498:
----------------------------------------
My problem went away.
> infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
> --------------------------------------------------------------------
>
> Key: AS7-5498
> URL: https://issues.jboss.org/browse/AS7-5498
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering, Test Suite
> Environment: affected master
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 7.2.0.Alpha1
>
> Attachments: org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.txt, TEST-org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.xml
>
>
> Noticed by alexey
> [rhusar@rhusar jboss-as]$ java -version
> java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> {noformat}
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan ---
> [INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan ---
> [INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec
> Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest
> Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE!
> Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> Results :
> Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null>
> getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null>
> Tests in error:
> removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest)
> Tests run: 33, Failures: 2, Errors: 6, Skipped: 0
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-5498) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5498?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar commented on AS7-5498:
-------------------------------------
After upgrading Open JDK I am building OK:
{noformat}
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [1.368s]
[INFO] JBoss Application Server: Clustering Server API ... SUCCESS [10.998s]
[INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [3.676s]
[INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [5.741s]
[INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [32.820s]
[INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [1.247s]
[INFO] JBoss Application Server: Clustered registry service SUCCESS [0.618s]
[INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [0.687s]
[INFO] JBoss Application Server: Clustered singleton services SUCCESS [1.333s]
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [1.150s]
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [2.070s]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [1.563s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:04.602s
[INFO] Finished at: Tue Feb 05 13:17:21 CET 2013
[INFO] Final Memory: 77M/732M
[INFO] ------------------------------------------------------------------------
[rhusar@x220 clustering]$ java -version
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (fedora-2.3.5.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
{noformat}
However, when I try to build entire AS, protocol utilities fail completely:
{noformat}
Tests in error:
testSimpleRequest(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase)
testSimpleRequest(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.logging.LoggerProviders
testTwoSimpleRequests(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testTwoSimpleRequests(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testSeveralConcurrentSimpleRequests(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testSeveralConcurrentSimpleRequests(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testMissingOperationHandler(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testMissingOperationHandler(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testMissingRequestHandler(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testMissingRequestHandler(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testExceptionInRequestHandlerRead(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testExceptionInRequestHandlerRead(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testExceptionInRequestHandlerWrite(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testExceptionInRequestHandlerWrite(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testExceptionInRequestWrite(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testExceptionInRequestWrite(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testNoResponse(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testNoResponse(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testCancelAsyncTask(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testCancelAsyncTask(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
testAwaitCompletion(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.jboss.threads.QueueExecutor
testAwaitCompletion(org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase): Could not initialize class org.xnio.IoUtils
Tests run: 22, Failures: 0, Errors: 22, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.558s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [0.771s]
[INFO] JBoss Application Server: Protocol Utilities ...... FAILURE [3.790s]
{noformat}
Anyone else seeing the same now?
> infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
> --------------------------------------------------------------------
>
> Key: AS7-5498
> URL: https://issues.jboss.org/browse/AS7-5498
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering, Test Suite
> Environment: affected master
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 7.2.0.Alpha1
>
> Attachments: org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.txt, TEST-org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.xml
>
>
> Noticed by alexey
> [rhusar@rhusar jboss-as]$ java -version
> java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> {noformat}
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan ---
> [INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan ---
> [INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec
> Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest
> Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE!
> Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> Results :
> Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null>
> getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null>
> Tests in error:
> removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest)
> Tests run: 33, Failures: 2, Errors: 6, Skipped: 0
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JGRP-1576) org.jgroups.protocols.TP.ChannelThreadGroup leaks classloaders / PermGen memory
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1576?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1576:
--------------------------------
OK, I cherry-picked the commit from master where I removed ThreadGroups. Running the test suite now. If it passes I'll release 3.2.7 today.
> org.jgroups.protocols.TP.ChannelThreadGroup leaks classloaders / PermGen memory
> -------------------------------------------------------------------------------
>
> Key: JGRP-1576
> URL: https://issues.jboss.org/browse/JGRP-1576
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.2.5
> Reporter: Mattias Jiderhamn
> Assignee: Bela Ban
> Fix For: 3.2.7
>
>
> Just like JGRP-1410 there is a custom ThreadGroup org.jgroups.protocols.TP.ChannelThreadGroup which is not destroyed so the parent thread group will keep a reference and keep the classloader from being garbage collected. There is actually code for destroying the thread groups (line 1026-1030) but for some reason it is commented out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6450) Missing <recovery> element. XA recovery disabled for: java:/JmsXA
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-6450:
--------------------------------
Summary: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
Key: AS7-6450
URL: https://issues.jboss.org/browse/AS7-6450
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
With latest version of HornetQ and IronJacamar, when AS7 is started with the standalone-full.xml, it logs a WARN message:
{noformat}
11:23:11,152 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingpaging)
11:23:11,154 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221008: Waiting to obtain live lock
11:23:11,175 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221017: Using NIO Journal
11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221039: Waiting to obtain live lock
11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221040: Live Server Obtained live lock
11:23:11,489 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol
11:23:11,490 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol
11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221009: Server is now live
11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [0ac0dcd4-6f7e-11e2-9c21-f566250843f7]
11:23:11,507 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
11:23:11,508 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
11:23:11,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
11:23:11,545 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
11:23:11,568 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
11:23:11,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
11:23:11,570 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
{noformat}
This WARN was not present in AS7 7.1.2.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JGRP-1573) Non-atomic retrieval of seqnos causes IllegalArgumentException
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1573?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1573.
----------------------------
Resolution: Done
Using getDigest() instead of getHighestDelivered()/getHighestReceived()
> Non-atomic retrieval of seqnos causes IllegalArgumentException
> --------------------------------------------------------------
>
> Key: JGRP-1573
> URL: https://issues.jboss.org/browse/JGRP-1573
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.6
> Reporter: Radim Vansa
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.2.7, 3.3
>
>
> In {{UNICAST2.handleDataReceived}} the hr and hd arguments are read non-atomically (out of lock) and neither are {{volatile}}, therefore, the order of reading the values may be interchanged (even if the values were updated in the correct order, reading delivered prior to received does not help currently). This may lead to later {{IllegalArgumentException}}.
> This could be fixed by either requesting the seqnos synchronously or in a loop until hd <= hr holds (and set them to be volatile).
> {code}
> 04:39:37,939 ERROR [org.jgroups.protocols.TCP] (OOB-32,null) failed handling incoming message: java.lang.IllegalArgumentException: low (16456815) needs to be <= high (16456814)
> at org.jgroups.protocols.UNICAST2$Unicast2Header.createStableHeader(UNICAST2.java:1037) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.UNICAST2.sendStableMessage(UNICAST2.java:611) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:754) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:420) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:606) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.FD.up(FD.java:253) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.MPING.up(MPING.java:179) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2642) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1289) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1852) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1825) [jgroups-3.2.6.Final-redhat-1.jar:3.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6415) Access Log directory - XML Parse issue
by narayana b (JIRA)
[ https://issues.jboss.org/browse/AS7-6415?page=com.atlassian.jira.plugin.s... ]
narayana b commented on AS7-6415:
---------------------------------
Hi,
Is this replicated at your end?
Pls update me.
> Access Log directory - XML Parse issue
> --------------------------------------
>
> Key: AS7-6415
> URL: https://issues.jboss.org/browse/AS7-6415
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Environment: Jboss 7.1.1 win xp 32 bit
> Reporter: narayana b
>
> step1)
> <!-- -->
> <paths>
> <path path="E:/jboss/jboss-as-7.1.1.Final/standalone" name="access-log-dir" />
> </paths>
> step2) created a "access-log" dir under E:/jboss/jboss-as-7.1.1.Final/standalone
> <virtual-server name="default-host" enable-welcome-root="true">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <acesss-log pattern="Time Taken: %T %h %l %u %t %r %s %b" resolve-hosts="false" extended="false" prefix="access_log." rotate="true">
> <directory path ="access-log" relative-to="access-log-dir" />
> </acesss-log>
> </virtual-server>
> Parse Error
> -----------
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1
> at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[351,5]
> Message: JBAS014789: Unexpected element '{urn:jboss:domain:web:1.1}acesss-log' encountered
> at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.web.WebSubsystemParser.parseHost(WebSubsystemParser.java:582)
> at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:329)
> at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:65)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Fi.........
> Please let me know is this fixed? ready to release??
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months