[JBoss JIRA] (WFLY-6081) [Migration][WebToUndertow] Access log valves are not automaticaly migrated
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-6081?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet moved JBEAP-3074 to WFLY-6081:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6081 (was: JBEAP-3074)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
(was: Migration)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR5
(was: 7.0.0.ER4)
> [Migration][WebToUndertow] Access log valves are not automaticaly migrated
> --------------------------------------------------------------------------
>
> Key: WFLY-6081
> URL: https://issues.jboss.org/browse/WFLY-6081
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Reporter: ehsavoie Hugonnet
> Assignee: Stuart Douglas
>
> Access log valves are not automatically migrated, it should be either printed warning for them to be migrated automatically or migrated automatically.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFCORE-1336) Upgrade jboss-modules to 1.5.1
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-1336:
-----------------------------------
Summary: Upgrade jboss-modules to 1.5.1
Key: WFCORE-1336
URL: https://issues.jboss.org/browse/WFCORE-1336
Project: WildFly Core
Issue Type: Component Upgrade
Components: Modules
Affects Versions: 2.0.7.Final
Reporter: Tomaz Cerar
Assignee: David Laffranchi
Priority: Blocker
Fix For: 2.0.8.Final
We need new jboss-modules release that addresses MODULES-239
so we can fix JBEAP-2112
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBMESSAGING-1959) Getting establishLease Thread Blocked even after applying JBREM1297
by Rajesh Malla (JIRA)
Rajesh Malla created JBMESSAGING-1959:
-----------------------------------------
Summary: Getting establishLease Thread Blocked even after applying JBREM1297
Key: JBMESSAGING-1959
URL: https://issues.jboss.org/browse/JBMESSAGING-1959
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Reporter: Rajesh Malla
Priority: Critical
We are getting following error even after applying JBREM-1297 patch applied.
Hence we are not able to find out cause for this.
Caused by: java.lang.Exception: Error setting up client lease
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:563)
at org.jboss.remoting.Client.setupClientLease(Client.java:2070)
at org.jboss.remoting.Client.connect(Client.java:1924)
... 83 more
Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out. Waited 30000 milliseconds for response while calling on InvokerLocator [bisocket://denalicm002:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&failureDisconnectTimeout=0&generalizeSocketException=true&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=5&pingFrequency=30000&pingWindowFactor=71582&socket.check_connection=false&stopLeaseOnFailure=true&timeout=300000&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&useClientConnectionIdentity=true&validatorPingPeriod=10000&validatorPingTimeout=5000]; nested exception is:
java.net.SocketTimeoutException: Read timed out
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:137)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.handleOtherException(MicroSocketClientInvoker.java:1079)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:941)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:470)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169)
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:529)
... 85 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at java.io.FilterInputStream.read(FilterInputStream.java:83)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1342)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:895)
... 88 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months