[JBoss JIRA] (REMJMX-95) RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-95?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved REMJMX-95.
------------------------------------
Resolution: Done
> RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around
> --------------------------------------------------------------------------------------------
>
> Key: REMJMX-95
> URL: https://issues.jboss.org/browse/REMJMX-95
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 2.0.0.Final
> Environment: Wildfly 8.2.0
> Reporter: Sergiy Barlabanov
> Assignee: Darran Lofthouse
> Fix For: 2.0.1.CR2
>
>
> The javadoc of javax.management.remote.JMXConnector#connect says that "If connect has already been called successfully on this object, calling it again has no effect.".
> But this does not work with org.jboss.remotingjmx.RemotingConnector. Every connect result in a creation of a remoting endpoint with the corresponding io/worker threads, which are not closed when close() method is called. Only the threads from the first connect() invocation are closed, all threads created from the subsequent connect() invocations are not closed and stay alive until the VM shutdown.
> Our application currently crashes after 10 minutes running - it pulls some JMX data periodically and after some time, the VM refuses to create new threads.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4332) Wrong path with Stateless WebService and serviceName
by Janario Oliveira (JIRA)
[ https://issues.jboss.org/browse/WFLY-4332?page=com.atlassian.jira.plugin.... ]
Janario Oliveira closed WFLY-4332.
----------------------------------
> Wrong path with Stateless WebService and serviceName
> ----------------------------------------------------
>
> Key: WFLY-4332
> URL: https://issues.jboss.org/browse/WFLY-4332
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.2.0.Final
> Reporter: Janario Oliveira
> Assignee: Alessio Soldano
>
> When I have a WebService with serviceName and it is a Stateless It adds a different url.
> e.g.
> @WebService(serviceName = "StatelessWeb") @Stateless
> public class StatelessWebService {
> public boolean executeTest() {return true;}
> }
> It will be available in /StatelessWeb/StatelessWebService. Once if it isn't a stateless it will be in /StatelessWeb
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4476) Unable to configure cxf socket timeout in wildfly_8.2.Final
by George Mathias (JIRA)
[ https://issues.jboss.org/browse/WFLY-4476?page=com.atlassian.jira.plugin.... ]
George Mathias commented on WFLY-4476:
--------------------------------------
What would really help is to be able to supply http conduit settings to cxf from standalone.xml config file.
> Unable to configure cxf socket timeout in wildfly_8.2.Final
> -----------------------------------------------------------
>
> Key: WFLY-4476
> URL: https://issues.jboss.org/browse/WFLY-4476
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final, 8.2.0.Final, 9.0.0.Beta2
> Environment: Java8, Ubuntu Linux Desktop
> Reporter: George Mathias
> Assignee: Alessio Soldano
> Priority: Critical
> Labels: cxf, saaj, undertow
> Fix For: 8.2.0.Final
>
>
> Socket times out after 60 seconds when calling SAAJ webservices from a wildfly servlet. Wildfly uses CXF internally and CXF HTTP Conduit times out in 60 seconds by default. Cannot find a way to configure this timeout (Receive timeout) in standalone.xml file.
> Following line throws socket read time out exception
> responseMsg = soapConn.call(soapMessage, wsdlLoc);
> Java Call is:
> private static String callWebService(String serviceName,
> String userName,
> org.w3c.dom.Document soapRequestDoc,
> String serviceType,
> String endPointAddress,
> String remoteClientAddress,
> String remoteClientHostname,
> String remoteClientUser,
> String clientApplicationId)
> throws SOAPException,java.io.IOException,CommunicationException
> {
> SOAPConnection soapConn = null;
> String wsdlLoc=endPointAddress;
> String resp = "";
> MessageFactory msgFactory;
> SOAPFactory soapFactory;
> SOAPMessage soapMessage;
> SOAPConnectionFactory soapConnFactory;
> SOAPMessage responseMsg;
>
> try
> {
> if (wsdlLoc == null)
> throw new SOAPException("Error: Endpoint address is NULL.");
> msgFactory = MessageFactory.newInstance();
> soapFactory = SOAPFactory.newInstance();
> soapMessage = msgFactory.createMessage();
>
> //Add headers
> addSoapHeaders(soapMessage,soapFactory,
> serviceType,userName,remoteClientAddress,remoteClientHostname,
> remoteClientUser,
> clientApplicationId);
>
> //Add Body addBody(soapMessage,soapFactory,soapRequestDoc,serviceName);
>
> logger.debug(soapMessage);
> soapConnFactory = SOAPConnectionFactory.newInstance();
> soapConn = soapConnFactory.createConnection();
> logger.debug("Invoking service ["+serviceName+
> "] on WSDL ["+
> wsdlLoc+"] ...");
>
> responseMsg = soapConn.call(soapMessage, wsdlLoc);
> logger.debug("Call completed ["+serviceName+
> "] on WSDL ["+
> wsdlLoc+"]!");
> resp = processResponseMessageStringParser(responseMsg);
> logger.debug("Return Document [" + resp + "]");
> }
> catch (SOAPException e)
> {
> logger.error(e);
> throw new CommunicationException(errorBuffer.toString());
> }
> finally
> {
> try
> {
> if (soapConn != null)
> soapConn.close();
> }
> catch (Exception e)
> {
> e.printStackTrace();
> }
> }
>
> return resp;
> }
> Exception thrown is:
> javax.xml.soap.SOAPException: JBWS024004: SOAP message could not be sent
> at org.jboss.wsf.stack.cxf.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:124)
> at com.qwest.servlet.Client.callWebService(Client.java:225)
> at com.qwest.servlet.Client.call(Client.java:138)
> at com.qwest.servlet.TestServlet.doGet(TestServlet.java:73)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:278)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:255)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/TestWS/v2.0.0/TestServer?wsdl: Read timed out
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1347)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1331)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:632)
> at org.jboss.wsf.stack.cxf.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:120)
> ... 31 more
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:703)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1534)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:266)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1545)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1515)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1318)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4476) Unable to configure cxf socket timeout in wildfly_8.2.Final
by George Mathias (JIRA)
[ https://issues.jboss.org/browse/WFLY-4476?page=com.atlassian.jira.plugin.... ]
George Mathias commented on WFLY-4476:
--------------------------------------
I was able to fix a workaround by changing receive timeout in apache-cxf source and rebuilding it for wildfly8.2
> Unable to configure cxf socket timeout in wildfly_8.2.Final
> -----------------------------------------------------------
>
> Key: WFLY-4476
> URL: https://issues.jboss.org/browse/WFLY-4476
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final, 8.2.0.Final, 9.0.0.Beta2
> Environment: Java8, Ubuntu Linux Desktop
> Reporter: George Mathias
> Assignee: Alessio Soldano
> Priority: Critical
> Labels: cxf, saaj, undertow
> Fix For: 8.2.0.Final
>
>
> Socket times out after 60 seconds when calling SAAJ webservices from a wildfly servlet. Wildfly uses CXF internally and CXF HTTP Conduit times out in 60 seconds by default. Cannot find a way to configure this timeout (Receive timeout) in standalone.xml file.
> Following line throws socket read time out exception
> responseMsg = soapConn.call(soapMessage, wsdlLoc);
> Java Call is:
> private static String callWebService(String serviceName,
> String userName,
> org.w3c.dom.Document soapRequestDoc,
> String serviceType,
> String endPointAddress,
> String remoteClientAddress,
> String remoteClientHostname,
> String remoteClientUser,
> String clientApplicationId)
> throws SOAPException,java.io.IOException,CommunicationException
> {
> SOAPConnection soapConn = null;
> String wsdlLoc=endPointAddress;
> String resp = "";
> MessageFactory msgFactory;
> SOAPFactory soapFactory;
> SOAPMessage soapMessage;
> SOAPConnectionFactory soapConnFactory;
> SOAPMessage responseMsg;
>
> try
> {
> if (wsdlLoc == null)
> throw new SOAPException("Error: Endpoint address is NULL.");
> msgFactory = MessageFactory.newInstance();
> soapFactory = SOAPFactory.newInstance();
> soapMessage = msgFactory.createMessage();
>
> //Add headers
> addSoapHeaders(soapMessage,soapFactory,
> serviceType,userName,remoteClientAddress,remoteClientHostname,
> remoteClientUser,
> clientApplicationId);
>
> //Add Body addBody(soapMessage,soapFactory,soapRequestDoc,serviceName);
>
> logger.debug(soapMessage);
> soapConnFactory = SOAPConnectionFactory.newInstance();
> soapConn = soapConnFactory.createConnection();
> logger.debug("Invoking service ["+serviceName+
> "] on WSDL ["+
> wsdlLoc+"] ...");
>
> responseMsg = soapConn.call(soapMessage, wsdlLoc);
> logger.debug("Call completed ["+serviceName+
> "] on WSDL ["+
> wsdlLoc+"]!");
> resp = processResponseMessageStringParser(responseMsg);
> logger.debug("Return Document [" + resp + "]");
> }
> catch (SOAPException e)
> {
> logger.error(e);
> throw new CommunicationException(errorBuffer.toString());
> }
> finally
> {
> try
> {
> if (soapConn != null)
> soapConn.close();
> }
> catch (Exception e)
> {
> e.printStackTrace();
> }
> }
>
> return resp;
> }
> Exception thrown is:
> javax.xml.soap.SOAPException: JBWS024004: SOAP message could not be sent
> at org.jboss.wsf.stack.cxf.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:124)
> at com.qwest.servlet.Client.callWebService(Client.java:225)
> at com.qwest.servlet.Client.call(Client.java:138)
> at com.qwest.servlet.TestServlet.doGet(TestServlet.java:73)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:278)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:255)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/TestWS/v2.0.0/TestServer?wsdl: Read timed out
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1347)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1331)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:632)
> at org.jboss.wsf.stack.cxf.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:120)
> ... 31 more
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:703)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1534)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1439)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:266)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1545)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1515)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1318)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (JBLOGGING-111) LoggerProvider configured with new ServiceLoader crash
by Ghislain Nadeau (JIRA)
[ https://issues.jboss.org/browse/JBLOGGING-111?page=com.atlassian.jira.plu... ]
Ghislain Nadeau commented on JBLOGGING-111:
-------------------------------------------
I see there's a pull request sent, and looking at the pull request itself, it looks like it has been merged.
Is it fixed?
> LoggerProvider configured with new ServiceLoader crash
> ------------------------------------------------------
>
> Key: JBLOGGING-111
> URL: https://issues.jboss.org/browse/JBLOGGING-111
> Project: JBoss Logging
> Issue Type: Bug
> Affects Versions: 3.2.0.Beta1
> Environment: Weblogic 10.3.2.0
> Configured in ejb jar, deployed by an ear file
> Reporter: Frederic Allard
> Assignee: James Perkins
>
> There is a new feature in the beta which uses the ServiceLoader to specify a LoggerProvider to be used by JBoss Logging.
> org.jboss.logging.LoggerProviders snippet :
> {code}
> // Next try for a service provider
> try {
> final ServiceLoader<LoggerProvider> loader = ServiceLoader.load(LoggerProvider.class, cl);
> if (loader.iterator().hasNext()) {
> return loader.iterator().next();
> }
> } catch (Throwable ignore) {
> // TODO consider printing the stack trace as it should only happen once
> }
> {code}
> When you try to configure a provider (ex. org.jboss.logging.Slf4jLoggerProvider), the ServiceLoader crash silently and ignore the provider.
> {code}
> java.util.ServiceConfigurationError: org.jboss.logging.LoggerProvider: Provider org.jboss.logging.Slf4jLoggerProvider could not be instantiated: java.lang.IllegalAccessException: Class java.util.ServiceLoader$LazyIterator can not access a member of class org.jboss.logging.Slf4jLoggerProvider with modifiers ""
> at java.util.ServiceLoader.fail(ServiceLoader.java:207)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:164)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:353)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:421)
> at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:70)
> at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:32)
> at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:29)
> at org.jboss.logging.Logger.getLogger(Logger.java:2177)
> at org.jboss.logging.Logger$1.run(Logger.java:2277)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2241)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2228)
> at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:176)
> ...
> {code}
> This is caused by the fact that all JBoss providers are not public classes and are instead package classes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-380) Operations to read content from the content repository
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-380?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-380:
---------------------------------------
Assignee: luck3y
Ken,
This may or may not conflict with the task of supporting exploded deployments in the content repository. Possible conflicts:
1) Adding an attribute for this just doesn't fit nicely with whatever API we add for managing exploding deployments.
2) Users may think this attribute will allow them to suck down a zipped version of an exploded deployment. (I guess this is a variant of 1) above.)
It's ok to reschedule this out of 1.0.0.CR1 if you're concerned about adding this API now before the full picture is clear.
> Operations to read content from the content repository
> ------------------------------------------------------
>
> Key: WFCORE-380
> URL: https://issues.jboss.org/browse/WFCORE-380
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: luck3y
> Priority: Minor
> Fix For: 1.0.0.CR1
>
>
> Ability to pull data out of the content repository. We can do that with rollout plans, but not for deployments or if we add deployment content overlays.
> Basically, if the user loses the original of the deployment, let's let them get it back via the management API and remove the temptation for them to hack into the repository.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-43) Clarify the meaning of the 'server-state' and 'host-state' attributes
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-43?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFCORE-43:
--------------------------------------
Assignee: luck3y
> Clarify the meaning of the 'server-state' and 'host-state' attributes
> ---------------------------------------------------------------------
>
> Key: WFCORE-43
> URL: https://issues.jboss.org/browse/WFCORE-43
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: luck3y
> Fix For: 1.0.0.CR1
>
>
> This JIRA is to implement what I described in the dev list discussion around the various states a server can be in for graceful shutdown (http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html)
> "I do think these are orthogonal and should not be combined.
> The existing attribute is fundamentally about how the state of the
> runtime services relates to the persistent configuration.
> STARTING == out of sync due to still getting in sync during start
> RUNNING == in sync
> RELOAD_REQURIRED = out of sync, needs a reload to get in sync
> RESTART_REQUIRED = out of sync, needs a full process restart to get in sync
> There are two problems though with the existing attribute that exposes this:
> 1) It's named "server-state" on a server and "host-state" on a Host
> Controller. Really crappy name; way too broad.
> That's fixable by creating a new attribute and making the old one an
> alias for compatibility purposes.
> 2) The RUNNING state is really poorly named.
> The could perhaps be fixed by coming up with a new name and translating
> it back to "RUNNING" in the handlers for the legacy "server-state" and
> "host-state" attributes."
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months