April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1923) Node cannot enter cluster during failover

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1923?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1923: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Node cannot enter cluster during failover > ----------------------------------------- > > Key: JBMESSAGING-1923 > URL: https://issues.jboss.org/browse/JBMESSAGING-1923 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Clustering > Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP8 > Reporter: Terrence Cowhey > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > The setup is a cluster of 4 nodes, arranged into 2 'sites': > Primary Site: site2blade1, site2blade2 > Secondary Site: site2blade3, site2blade4 > After restarting the nodes of the secondary site many times, one of them fails to come up, with a deployment failure in JMS - the PostOffice fails with an IllegalStateException. > The previous restarts were induced by either 'kill -KILL' on the app server, or a graceful shutdown. The final (failed) restart was on site2blade4, and was induced by a graceful shutdown of the app server. > The IllegalStateException is being thrown during a failover while a new node is starting to join the cluster. Waiting 60 seconds to start the node in question fixes the issue. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1905) Proper handling the timeout issue in receive(timeout)

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1905?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1905: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Proper handling the timeout issue in receive(timeout) > ----------------------------------------------------- > > Key: JBMESSAGING-1905 > URL: https://issues.jboss.org/browse/JBMESSAGING-1905 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade > Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP3 > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1880) JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer)

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1880?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1880: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer) > --------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-1880 > URL: https://issues.jboss.org/browse/JBMESSAGING-1880 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade > Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > If a client consumer receives a message and exit without acknowledging it or close the connection/session/consumer object, the message will be cancelled at the server side. When the message is delivered, its JMSRedelivered flag should be true. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3297) Hibernate with enabled enhancer throws error at deployment

by Markus D (JIRA)

[ https://issues.jboss.org/browse/WFLY-3297?page=com.atlassian.jira.plugin.... ] Markus D updated WFLY-3297: --------------------------- Description: When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. https://community.jboss.org/message/871056#871056 public class TornadoStrikeSkill extends SelfTargetSkill { private static final long serialVersionUID = 1123460060768124078L; public TornadoStrikeSkill() { } @Override protected void executeSkill() { ..... GameObjectService gameObjectService = BeanLocator.lookup(GameObjectService.class); // getting the characters from an EJB for(GameCharacter victim : gameObjectService.calculateVictims()) { } } public class GameCharacter extends GameObject { @OneToMany(mappedBy = "caster") private List<Skill> skills = new ArrayList<Skill>(); When I remove the for loop the error is gone. When I deploy the same application on JBoss 7.1 it works. So I guess the classloading has changed. Maybe the cyclic dependency messes with the javassist? was: When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. https://community.jboss.org/message/871056#871056 > Hibernate with enabled enhancer throws error at deployment > ---------------------------------------------------------- > > Key: WFLY-3297 > URL: https://issues.jboss.org/browse/WFLY-3297 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading > Affects Versions: 8.1.0.CR1 > Reporter: Markus D > Assignee: David Lloyd > Labels: hibernate > Attachments: verbose_log.txt > > > When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. > https://community.jboss.org/message/871056#871056 > public class TornadoStrikeSkill extends SelfTargetSkill { > private static final long serialVersionUID = 1123460060768124078L; > public TornadoStrikeSkill() { } > @Override > protected void executeSkill() { > ..... > GameObjectService gameObjectService = BeanLocator.lookup(GameObjectService.class); > // getting the characters from an EJB > for(GameCharacter victim : gameObjectService.calculateVictims()) { > > } > } > public class GameCharacter extends GameObject { > @OneToMany(mappedBy = "caster") > private List<Skill> skills = new ArrayList<Skill>(); > When I remove the for loop the error is gone. When I deploy the same application on JBoss 7.1 it works. So I guess the classloading has changed. > Maybe the cyclic dependency messes with the javassist? -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-464) osgi issue with jbpm-commons feature in karaf

by Charles Moulliard (JIRA)

[ https://issues.jboss.org/browse/DROOLS-464?page=com.atlassian.jira.plugin... ] Charles Moulliard resolved DROOLS-464. -------------------------------------- Resolution: Done > osgi issue with jbpm-commons feature in karaf > --------------------------------------------- > > Key: DROOLS-464 > URL: https://issues.jboss.org/browse/DROOLS-464 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta2 > Reporter: James Strachan > Assignee: Charles Moulliard > Labels: osgi > > this bit of 6.1.0.Beta2 feature XML doesn't load in karaf 2.3.3 or fabric8: > <feature name="jbpm-commons" version="6.1.0.Beta2" description="jBPM Commons"> > <bundle>wrap:mvn:javax.security/jacc/1.0</bundle> > as it can't be downloaded as the jar doesn't exist in maven central: > http://central.maven.org/maven2/javax/security/jacc/1.0/ > Not sure how the above has ever worked unless someone's got an old cached jar in their local repo? Or is there some repo thats got it in? > Maybe it needs changing to this which has a jar in maven central? > http://central.maven.org/maven2/javax/security/jacc/javax.security.jacc-a... -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3297) Hibernate with enabled enhancer throws error at deployment

by Markus D (JIRA)

[ https://issues.jboss.org/browse/WFLY-3297?page=com.atlassian.jira.plugin.... ] Markus D updated WFLY-3297: --------------------------- Description: When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. https://community.jboss.org/message/871056#871056 Labels: hibernate (was: ) Affects Version/s: 8.1.0.CR1 > Hibernate with enabled enhancer throws error at deployment > ---------------------------------------------------------- > > Key: WFLY-3297 > URL: https://issues.jboss.org/browse/WFLY-3297 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading > Affects Versions: 8.1.0.CR1 > Reporter: Markus D > Assignee: David Lloyd > Labels: hibernate > Attachments: verbose_log.txt > > > When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. > https://community.jboss.org/message/871056#871056 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3297) Hibernate with enabled enhancer throws error at deployment

by Markus D (JIRA)

[ https://issues.jboss.org/browse/WFLY-3297?page=com.atlassian.jira.plugin.... ] Markus D updated WFLY-3297: --------------------------- Attachment: verbose_log.txt Log with the deployment error. > Hibernate with enabled enhancer throws error at deployment > ---------------------------------------------------------- > > Key: WFLY-3297 > URL: https://issues.jboss.org/browse/WFLY-3297 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading > Affects Versions: 8.1.0.CR1 > Reporter: Markus D > Assignee: David Lloyd > Labels: hibernate > Attachments: verbose_log.txt > > > When I enable the enhancer in the persistence.xml then I receive an error from javassist at deployment. > https://community.jboss.org/message/871056#871056 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3297) Hibernate with enabled enhancer throws error at deployment

by Markus D (JIRA)

Markus D created WFLY-3297: ------------------------------ Summary: Hibernate with enabled enhancer throws error at deployment Key: WFLY-3297 URL: https://issues.jboss.org/browse/WFLY-3297 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Class Loading Reporter: Markus D Assignee: David Lloyd -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3252) First HTTPS / SSL request after startup of Wildfly 8.0.0.Final is blocked for many seconds

by bene.net (JIRA)

[ https://issues.jboss.org/browse/WFLY-3252?page=com.atlassian.jira.plugin.... ] bene.net commented on WFLY-3252: -------------------------------- Your fix works for me. I can confirm that the problem does not occur with WildFly 8.1.0.Final-SNAPSHOT "Kenny" (build #1083). Thanks a lot for your work! > First HTTPS / SSL request after startup of Wildfly 8.0.0.Final is blocked for many seconds > ------------------------------------------------------------------------------------------ > > Key: WFLY-3252 > URL: https://issues.jboss.org/browse/WFLY-3252 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Environment: Win7, Java 1.7.0_51 and 1.8.0 > Reporter: bene.net > Assignee: Tomaz Cerar > Priority: Critical > Labels: Blocked, HTTPS, JAX-RS, Performance, SSL, Start-Up, bouncycastle > Fix For: 8.1.0.Final > > Attachments: server_keystore.jks, standalone-full.xml > > > The first HTTPS / SSL request after startup of Wildfly 8.0.0.Final is blocked for many seconds. > Please note that subsequent requests perform normally. HTTP requests also perform fine. > We use curl to call a JAX-RS service (just in case this matters). > My first thought was, that we had hit the following bug: > https://issues.jboss.org/browse/XNIO-226?jql= > However, I can also reproduce the problem with xnio-3.2.2.Final (which contains a fix for bug XNIO-226). > So I inserted some logging statements in > {code:title=AbstractAcceptingSslChannel.java} > System.out.println("calling createSSLEngine..."); > long t1 = System.currentTimeMillis(); > final SSLEngine engine = sslContext.createSSLEngine(JsseSslUtils.getHostNameNoResolve(peerAddress), peerAddress.getPort()); > long t2 = System.currentTimeMillis(); > long duration = t2 - t1; > System.out.println("createSSLEngine took "+duration+" ms. "); > {code} > and in > {code:title=JsseSslConduitEngine.java} > case NEED_TASK: { > Runnable task; > synchronized (engine) { > // run the tasks needed for handshaking > while ((task = engine.getDelegatedTask()) != null) { > try { > System.out.println("calling task.run() in handleHandshake..."); > long t1 = System.currentTimeMillis(); > task.run(); > long t2 = System.currentTimeMillis(); > long duration = t2 - t1; > System.out.println("task.run() in handleHandshake took "+duration+" ms. "); > } catch (Exception e) { > throw new IOException(e); > } > } > } > // caller should try to wrap/unwrap again > return true; > } > {code} > I found out, that sslContext.createSSLEngine in AbstractAcceptingSslChannel.java is quite slow (468ms) but it is not the cause > for the blocking request. Instead org.xnio.ssl.JsseSslConduitEngine.handleHandshake(JsseSslConduitEngine.java:512) needs > 95 seconds to return!!! > Here is the relevant part from my log file: > {noformat} > INFO ; 2014-04-11 18:29:52,115; [Controller Boot Thread ]; JBAS015874: WildFly 8.0.0.Final "WildFly" started in 6477ms - Started 334 of 386 services (107 services are lazy, passive or on-demand); [org.jboss.as.server.BootstrapListener.done(BootstrapListener.java:93)]; ; > INFO ; 2014-04-11 18:30:05,566; [default I/O-3 ]; calling createSSLEngine... > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:30:06,035; [default I/O-3 ]; createSSLEngine took 468 ms. > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:30:06,066; [default I/O-3 ]; calling task.run() in handleHandshake... > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:31:41,128; [default I/O-3 ]; task.run() in handleHandshake took 95061 ms. > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:31:41,133; [default I/O-3 ]; calling task.run() in handleHandshake... > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:31:41,145; [default I/O-3 ]; task.run() in handleHandshake took 10 ms. > ; [org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71)]; ; > INFO ; 2014-04-11 18:31:41,573; [default task-1 ]; SecurityFilter received request. ; [de.head.vetsone.rest_ifc.SecurityFilter.filter(SecurityFilter.java:62)]; ; > {noformat} > Using JConsole I could extract the full stacktrace: > Name: default I/O-2 > State: RUNNABLE > Total blocked: 0 Total waited: 2 > Stack trace: > {noformat} > java.math.BigInteger.oddModPow(BigInteger.java:2700) > java.math.BigInteger.modPow(BigInteger.java:2443) > java.math.BigInteger.passesMillerRabin(BigInteger.java:1019) > java.math.BigInteger.primeToCertainty(BigInteger.java:875) > java.math.BitSieve.retrieve(BitSieve.java:203) > java.math.BigInteger.largePrime(BigInteger.java:744) > java.math.BigInteger.<init>(BigInteger.java:650) > org.bouncycastle.crypto.generators.DHParametersHelper.generateSafePrimes(Unknown Source) > org.bouncycastle.crypto.generators.DHParametersGenerator.generateParameters(Unknown Source) > org.bouncycastle.jce.provider.JDKKeyPairGenerator$DH.generateKeyPair(Unknown Source) > sun.security.ssl.DHCrypt.generateDHPublicKeySpec(DHCrypt.java:225) > sun.security.ssl.DHCrypt.<init>(DHCrypt.java:101) > sun.security.ssl.ServerHandshaker.setupEphemeralDHKeys(ServerHandshaker.java:1350) > sun.security.ssl.ServerHandshaker.trySetCipherSuite(ServerHandshaker.java:1194) > sun.security.ssl.ServerHandshaker.chooseCipherSuite(ServerHandshaker.java:1002) > sun.security.ssl.ServerHandshaker.clientHello(ServerHandshaker.java:724) > sun.security.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:213) > sun.security.ssl.Handshaker.processLoop(Handshaker.java:925) > sun.security.ssl.Handshaker$1.run(Handshaker.java:865) > sun.security.ssl.Handshaker$1.run(Handshaker.java:862) > java.security.AccessController.doPrivileged(Native Method) > sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1302) > - locked sun.security.ssl.SSLEngineImpl@3f3d2d55 > org.xnio.ssl.JsseSslConduitEngine.handleHandshake(JsseSslConduitEngine.java:512) > - locked sun.security.ssl.SSLEngineImpl@3f3d2d55 > org.xnio.ssl.JsseSslConduitEngine.unwrap(JsseSslConduitEngine.java:595) > org.xnio.ssl.JsseSslConduitEngine.unwrap(JsseSslConduitEngine.java:543) > org.xnio.ssl.JsseSslStreamSourceConduit.read(JsseSslStreamSourceConduit.java:89) > org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127) > io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:111) > io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:69) > io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:38) > org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) > org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > org.xnio.nio.NioTcpServerHandle.handleReady(NioTcpServerHandle.java:53) > org.xnio.nio.WorkerThread.run(WorkerThread.java:531) > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-464) osgi issue with jbpm-commons feature in karaf

by Charles Moulliard (JIRA)

[ https://issues.jboss.org/browse/DROOLS-464?page=com.atlassian.jira.plugin... ] Charles Moulliard commented on DROOLS-464: ------------------------------------------ As this jar file when wrapped has dependencies with Servlet 3.0 and doc-files Import-Package = doc-files;version=1.5, javax.security.jacc;version=1.5, javax.servlet.http;version=3.0 we will use the geronimo or JBoss spec which are already OSGIfied. > osgi issue with jbpm-commons feature in karaf > --------------------------------------------- > > Key: DROOLS-464 > URL: https://issues.jboss.org/browse/DROOLS-464 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta2 > Reporter: James Strachan > Assignee: Charles Moulliard > Labels: osgi > > this bit of 6.1.0.Beta2 feature XML doesn't load in karaf 2.3.3 or fabric8: > <feature name="jbpm-commons" version="6.1.0.Beta2" description="jBPM Commons"> > <bundle>wrap:mvn:javax.security/jacc/1.0</bundle> > as it can't be downloaded as the jar doesn't exist in maven central: > http://central.maven.org/maven2/javax/security/jacc/1.0/ > Not sure how the above has ever worked unless someone's got an old cached jar in their local repo? Or is there some repo thats got it in? > Maybe it needs changing to this which has a jar in maven central? > http://central.maven.org/maven2/javax/security/jacc/javax.security.jacc-a... -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2014