[JBoss JIRA] (WFCORE-519) Xalan Linkage error : TransformerConfigurationException
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-519?page=com.atlassian.jira.plugin... ]
David Lloyd moved WFLY-4174 to WFCORE-519:
------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-519 (was: WFLY-4174)
Affects Version/s: (was: 8.2.0.Final)
Component/s: Scripts
(was: Class Loading)
> Xalan Linkage error : TransformerConfigurationException
> -------------------------------------------------------
>
> Key: WFCORE-519
> URL: https://issues.jboss.org/browse/WFCORE-519
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Environment: Wildfly 8.1 & 8.2-Final
> JDK 1.7.0_45 & 1.7.0_71
> Windows & Linux
> Reporter: Stephen Kay
> Assignee: David Lloyd
> Priority: Critical
>
> Please note that this bug wasn't present on JBoss 7.1 / same WAR artifact
> This is full staktrace from our applicaion.
> 11:13:32,130 SEVERE ch.mitsa.credoc.ui.views.messages.MessagesTable (default task-9) Error getting message payload: : javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:765) rt.jar:1.7.0_71
> at _redirected.TransformerFactory.newTransformer(_TransformerFactory.java:132) jboss-modules.jar:1.3.3.Final
> at ch.mitsa.credoc.format.swift.impl.SwiftFormatter.getPrettyPrintedPayload(SwiftFormatter.java:196)
> at ch.mitsa.credoc.engine.service.OutputService.getPrettyPrintedMessage(OutputService.java:54)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) rt.jar:1.7.0_71
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) rt.jar:1.7.0_71
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) rt.jar:1.7.0_71
> at java.lang.reflect.Method.invoke(Method.java:606) rt.jar:1.7.0_71
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) wildfly-weld-8.2.0.Final.jar:8.2.0.Final
> (...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFCORE-491) Improve ManagedAuditLoggerImpl.log() performance when disabled
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-491?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-491:
-----------------------------------------
Thanks for this.
A quick note on the problem, in case this PR results in issues after I merge it. The problem seems like quite an edge case. Contention on the lock means concurrent management requests, not just a rapid succession of requests. So, lots and lots of clients or clients that for some reason are making a lot concurrent requests.
> Improve ManagedAuditLoggerImpl.log() performance when disabled
> --------------------------------------------------------------
>
> Key: WFCORE-491
> URL: https://issues.jboss.org/browse/WFCORE-491
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha15
> Reporter: James Livingston
> Assignee: James Livingston
> Priority: Minor
>
> org.jboss.as.controller.audit.ManagedAuditLoggerImpl.log/logJmxMethodAccess() does some work such as creating the log item which will just be thrown away if getLoggerStatus()==DISABLED.
> It may be worth checking if that is the case and skipping the work that will not be needed. If it was not for the applyHandlerUpdates() call, I think an "isDisabled" volatile flag could be used to avoid taking the lock at all there, which can be expensive due to it being a fair lock.
> This does not appear to show up as a issue unless you are performing a lot (thousands) of management operations in quick succession.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4286) ClassNotFoundException from xmlschema-core.jar
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-4286?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-4286.
-------------------------------
Resolution: Rejected
No, this is a usage error. WildFly does bundle this library, however it is not added to a deployment's class path by default.
You can include this dependency by adding a header like this to your MANIFEST.MF file (use the maven JAR plugin):
{noformat}
Dependencies: org.apache.ws.xmlschema
{noformat}
This will allow you to re-add the "provided" scope to your POM dependency specification.
> ClassNotFoundException from xmlschema-core.jar
> ----------------------------------------------
>
> Key: WFLY-4286
> URL: https://issues.jboss.org/browse/WFLY-4286
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.2.0.Final
> Reporter: Thomas Offner
> Assignee: David Lloyd
>
> Hi,
>
> I have a Maven project (which builds a war) with the following dependency:
> <dependency>
> <groupId>org.apache.ws.xmlschema</groupId>
> <artifactId>xmlschema-core</artifactId>
> <version>2.0.2</version>
> <scope>provided</scope>
> </dependency>
> However when i Deploy my Application to a Default Wildfly 8.2 Installation (Runs on JDK 1.8.31) then I get the following error:
> Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaMaxLengthFacet
> .....
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0_31]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0_31]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0_31]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408) [rt.jar:1.8.0_31]
> at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:113) [weld-core-impl-2.2.6.Final.jar:2014-10-03 10:05]
> ... 139 more
> Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaMaxLengthFacet from [Module "deployment.myapplication.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]
> ... 149 more
> However, the xmlschema-core.jar can be found in the wildfly installation folder: $WILDFLY_HOME\modules\system\layers\base\org\apache\ws\xmlschema\main
> When i change the dependency to:
> <dependency>
> <groupId>org.apache.ws.xmlschema</groupId>
> <artifactId>xmlschema-core</artifactId>
> <version>2.0.2</version>
> <!--<scope>provided</scope>-->
> </dependency>
> The ClassNotFoundException doesn't occur anymore. May this be a bug?
> Regards,
> Thomas
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4285) NullPointerException in InfinispanBatcher.createBatch
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-4285?page=com.atlassian.jira.plugin.... ]
Michal Vinkler commented on WFLY-4285:
--------------------------------------
The bug can be reproduced with 9.0.0.Alpha1 build as well as with the current WildFly master branch build. The stacktrace is from the current WildFly master branch build.
> NullPointerException in InfinispanBatcher.createBatch
> -----------------------------------------------------
>
> Key: WFLY-4285
> URL: https://issues.jboss.org/browse/WFLY-4285
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Attachments: clusterbench-ee7.ear
>
>
> When changing transaction mode to "NONE" for the cache containter "web" in standalone-ha.xml, starting the standalone server in the HA mode and deploying the "clusterbench" application (see the attachments), a NullPointerException occurs.
> Clusterbench git repo:
> https://github.com/clusterbench/clusterbench
> Stacktrace:
> {code}
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started dist cache from ejb container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started dist cache from web container
> 11:13:17,554 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 66) MSC000001: Failed to start service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.NullPointerException
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:64)
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:41)
> at org.wildfly.clustering.server.registry.CacheRegistry.getLocalEntry(CacheRegistry.java:128)
> at org.wildfly.clustering.server.registry.CacheRegistry.<init>(CacheRegistry.java:76)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory$1.<init>(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory.createRegistry(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.RegistryBuilder.start(RegistryBuilder.java:83)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> ... 4 more
> 11:13:17,586 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,587 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,601 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 11:13:18,102 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "web")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.clustering.registry.web.default" => "org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "sample.war" (runtime-name : "sample.war")
> 11:13:18,126 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> 11:13:18,146 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 11:13:18,147 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 11:13:18,147 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) started (with errors) in 6312ms - Started 769 of 960 services (12 services failed or missing dependencies, 333 services are lazy, passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1876:
--------------------------------
I looked at the PR and I'm skeptical: it delays possible merges in favor of waiting for INFO messages *only* from coordinators. Consider the following scenario:
* Subgroups are A1=AB, C1=C, D1=DE, F1=FG, H1=HIJ
* C gets the INFO messages:
** From B: A1
** From C: C1 (itself)
** From D: D1
** From F: F1
** From H: H1
The information about view A1 was not sent by A, but by B. Your code will now simply return from the merge attempt, because of this one single INFO sent from B instead of A. This prevents a partial merge between views C1, D1, F1 and H1 !
This problem gets worse with increasing number of subclusters: the likelihood that at least one _non-coordinator_ sends an INFO message increases and this stops a potential partial merge.
> MERGE3 : Strange number and content of subgroups
> ------------------------------------------------
>
> Key: JGRP-1876
> URL: https://issues.jboss.org/browse/JGRP-1876
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.2
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6, 3.6.2
>
> Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, JGRP-1876-1.pdf, karim-logs-files.zip, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt
>
>
> Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2).
> The final mergeView is correct and contains 210 members.
> Here is an extract of subviews:
> {code}
> INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172]
> 210 subgroups
> [....
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]]
> [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]]
> ....]
> {code}
> II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view.
> Example:
> {code}
> {A, B, C} => {A, B, C} and {C} => {A, B, C}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3664) Exceptions during download of webstart libraries
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3664?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3664:
---------------------------------
Assignee: Tomaz Cerar (was: Stuart Douglas)
> Exceptions during download of webstart libraries
> ------------------------------------------------
>
> Key: WFLY-3664
> URL: https://issues.jboss.org/browse/WFLY-3664
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 (64bit), Windows Server 2012 R2 (64bit)
> Reporter: Markus Schwarz
> Assignee: Tomaz Cerar
> Priority: Minor
> Attachments: demo-src.zip, lsof.log.gz, server.log, server.log.gz
>
>
> I have a webstart application using the JnlpDownloadServlet. If the client cache is empty, launching the JNLP will download the libraries. The webstart application works as expected, but in the server logs there are many errors regarding download of the libraries.
> Just to mention: Not always the same libraries are listed with erros in the logs files. Sometimes I even got now exceptions.
> For my tests I used Wildfly 8.1.0.FINAL as well as a nightly build from 24. of July without any further changes of the configuration files (https://ci.jboss.org/hudson/job/WildFly-latest-master/).
> I tested it under Windows 7 and Windows Server 2012 R2. The demo contains an older JnlpDownloadServlet, but I tested it also with the one coming with JDK 7u65.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4286) ClassNotFoundException from xmlschema-core.jar
by Thomas Offner (JIRA)
Thomas Offner created WFLY-4286:
-----------------------------------
Summary: ClassNotFoundException from xmlschema-core.jar
Key: WFLY-4286
URL: https://issues.jboss.org/browse/WFLY-4286
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 8.2.0.Final
Reporter: Thomas Offner
Assignee: David Lloyd
Hi,
I have a Maven project (which builds a war) with the following dependency:
<dependency>
<groupId>org.apache.ws.xmlschema</groupId>
<artifactId>xmlschema-core</artifactId>
<version>2.0.2</version>
<scope>provided</scope>
</dependency>
However when i Deploy my Application to a Default Wildfly 8.2 Installation (Runs on JDK 1.8.31) then I get the following error:
Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaMaxLengthFacet
.....
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0_31]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0_31]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0_31]
at java.lang.reflect.Constructor.newInstance(Constructor.java:408) [rt.jar:1.8.0_31]
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:113) [weld-core-impl-2.2.6.Final.jar:2014-10-03 10:05]
... 139 more
Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaMaxLengthFacet from [Module "deployment.myapplication.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]
... 149 more
However, the xmlschema-core.jar can be found in the wildfly installation folder: $WILDFLY_HOME\modules\system\layers\base\org\apache\ws\xmlschema\main
When i change the dependency to:
<dependency>
<groupId>org.apache.ws.xmlschema</groupId>
<artifactId>xmlschema-core</artifactId>
<version>2.0.2</version>
<!--<scope>provided</scope>-->
</dependency>
The ClassNotFoundException doesn't occur anymore. May this be a bug?
Regards,
Thomas
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4285) NullPointerException in InfinispanBatcher.createBatch
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4285?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4285:
-----------------------------------
Any chance you can try with latest nightly build that you can find at: https://developer.jboss.org/thread/224262
current builds already have infinispan 7 as base for clustering and few other improvements.
> NullPointerException in InfinispanBatcher.createBatch
> -----------------------------------------------------
>
> Key: WFLY-4285
> URL: https://issues.jboss.org/browse/WFLY-4285
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Attachments: clusterbench-ee7.ear
>
>
> When changing transaction mode to "NONE" for the cache containter "web" in standalone-ha.xml, starting the standalone server in the HA mode and deploying the "clusterbench" application (see the attachments), a NullPointerException occurs.
> Clusterbench git repo:
> https://github.com/clusterbench/clusterbench
> Stacktrace:
> {code}
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started dist cache from ejb container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started dist cache from web container
> 11:13:17,554 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 66) MSC000001: Failed to start service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.NullPointerException
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:64)
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:41)
> at org.wildfly.clustering.server.registry.CacheRegistry.getLocalEntry(CacheRegistry.java:128)
> at org.wildfly.clustering.server.registry.CacheRegistry.<init>(CacheRegistry.java:76)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory$1.<init>(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory.createRegistry(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.RegistryBuilder.start(RegistryBuilder.java:83)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> ... 4 more
> 11:13:17,586 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,587 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,601 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 11:13:18,102 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "web")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.clustering.registry.web.default" => "org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "sample.war" (runtime-name : "sample.war")
> 11:13:18,126 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> 11:13:18,146 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 11:13:18,147 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 11:13:18,147 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) started (with errors) in 6312ms - Started 769 of 960 services (12 services failed or missing dependencies, 333 services are lazy, passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4285) NullPointerException in InfinispanBatcher.createBatch
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-4285?page=com.atlassian.jira.plugin.... ]
Michal Vinkler commented on WFLY-4285:
--------------------------------------
Sorry for the missing description, everything should be here now.
> NullPointerException in InfinispanBatcher.createBatch
> -----------------------------------------------------
>
> Key: WFLY-4285
> URL: https://issues.jboss.org/browse/WFLY-4285
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Attachments: clusterbench-ee7.ear
>
>
> When changing transaction mode to "NONE" for the cache containter "web" in standalone-ha.xml, starting the standalone server in the HA mode and deploying the "clusterbench" application (see the attachments), a NullPointerException occurs.
> Clusterbench git repo:
> https://github.com/clusterbench/clusterbench
> Stacktrace:
> {code}
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started dist cache from ejb container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started dist cache from web container
> 11:13:17,554 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 66) MSC000001: Failed to start service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.NullPointerException
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:64)
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:41)
> at org.wildfly.clustering.server.registry.CacheRegistry.getLocalEntry(CacheRegistry.java:128)
> at org.wildfly.clustering.server.registry.CacheRegistry.<init>(CacheRegistry.java:76)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory$1.<init>(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory.createRegistry(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.RegistryBuilder.start(RegistryBuilder.java:83)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> ... 4 more
> 11:13:17,586 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,587 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,601 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 11:13:18,102 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "web")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.clustering.registry.web.default" => "org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "sample.war" (runtime-name : "sample.war")
> 11:13:18,126 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> 11:13:18,146 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 11:13:18,147 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 11:13:18,147 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) started (with errors) in 6312ms - Started 769 of 960 services (12 services failed or missing dependencies, 333 services are lazy, passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4285) NullPointerException in InfinispanBatcher.createBatch
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-4285?page=com.atlassian.jira.plugin.... ]
Michal Vinkler updated WFLY-4285:
---------------------------------
Attachment: clusterbench-ee7.ear
> NullPointerException in InfinispanBatcher.createBatch
> -----------------------------------------------------
>
> Key: WFLY-4285
> URL: https://issues.jboss.org/browse/WFLY-4285
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Attachments: clusterbench-ee7.ear
>
>
> When changing transaction mode to "NONE" for the cache containter "web" in standalone-ha.xml, starting the standalone server in the HA mode and deploying the "clusterbench" application (see the attachments), a NullPointerException occurs.
> Clusterbench git repo:
> https://github.com/clusterbench/clusterbench
> Stacktrace:
> {code}
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started dist cache from ejb container
> 11:13:17,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started dist cache from web container
> 11:13:17,554 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 66) MSC000001: Failed to start service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.NullPointerException
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:64)
> at org.wildfly.clustering.ee.infinispan.InfinispanBatcher.createBatch(InfinispanBatcher.java:41)
> at org.wildfly.clustering.server.registry.CacheRegistry.getLocalEntry(CacheRegistry.java:128)
> at org.wildfly.clustering.server.registry.CacheRegistry.<init>(CacheRegistry.java:76)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory$1.<init>(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.CacheRegistryFactory.createRegistry(CacheRegistryFactory.java:53)
> at org.wildfly.clustering.server.registry.RegistryBuilder.start(RegistryBuilder.java:83)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> ... 4 more
> 11:13:17,586 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,587 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> 11:13:17,601 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 11:13:18,102 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "web")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.clustering.registry.web.default" => "org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}}
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 11:13:18,125 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "sample.war" (runtime-name : "sample.war")
> 11:13:18,126 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.clustering.registry.web.default: org.jboss.msc.service.StartException in service jboss.clustering.registry.web.default: java.lang.NullPointerException
> 11:13:18,146 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 11:13:18,147 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 11:13:18,147 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) started (with errors) in 6312ms - Started 769 of 960 services (12 services failed or missing dependencies, 333 services are lazy, passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months