[JBoss JIRA] (JBFORUMS-295) JBOSS-4.0.4GA generates errors
by Regimantas Kontrimas (JIRA)
Regimantas Kontrimas created JBFORUMS-295:
---------------------------------------------
Summary: JBOSS-4.0.4GA generates errors
Key: JBFORUMS-295
URL: https://issues.jboss.org/browse/JBFORUMS-295
Project: JBoss Forums
Issue Type: Feature Request
Environment: JBOSS 4.0.4 GA works on RedHat
Reporter: Regimantas Kontrimas
Assignee: Luca Stancapiano
We have product, which works with jboss-4.0.4GA, and sometimes (recently it happens very often) and all my soft performance is very slow. My jboss-4.0.4GA server generates errors (my caught errors)
****Error
2012-01-26 08:16:16,615 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/xnet].[XNET2]] Servlet.service() for servlet XNET2 threw exception
javax.servlet.ServletException: SecurityException
at com.thrasys.xnet.servlets.XNetServlet2.doPost(XNetServlet2.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.thrasys.xnet.servlets.XNetServlet.service(XNetServlet.java:406)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at com.thrasys.xnet.servlets.XNetServlet.service(XNetServlet.java:415)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
****Error2*****
2012-01-26 09:45:56,182 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@95730337 { url=file:/usr/local/special/jboss-4.0.4.GA/server/default/deploy/run.conf }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/usr/local/special/jboss-4.0.4.GA/server/default/deploy/run.conf
altDD: null
lastDeployed: 1327563956181
lastModified: 1327563956000
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@95730337 { url=file:/usr/local/special/jboss-4.0.4.GA/server/default/deploy/run.conf }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/usr/local/special/jboss-4.0.4.GA/server/default/deploy/run.conf
altDD: null
lastDeployed: 1327563956181
lastModified: 1327563956000
mbeans:
*****Error3****
12-01-26 09:51:16,035 ERROR [STDERR] java.lang.NullPointerException
2012-01-26 09:51:16,036 ERROR [STDERR] at org.openedix.logging.LogManager.run(LogManager.java:322)
2012-01-26 09:51:16,036 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-2273) JPS Output
by Rich Sharples (Created) (JIRA)
JPS Output
----------
Key: AS7-2273
URL: https://issues.jboss.org/browse/AS7-2273
Project: Application Server 7
Issue Type: Enhancement
Components: Server
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Jason Greene
Fix For: 7.1.0.Beta1
All JBoss AS processes need to provide jps (JVM Process Status Tool) with a descriptive identifier - currently JPS reports a default domain as :
34151 jboss-modules.jar
34152 jboss-modules.jar
34153 jar
34154 jar
The first two are server instances, the last two are the DC and HC.
Even a verbose listing (jps -v) doesn't help distinguish server instances from each other or the DC from the HC. Maybe a dummy argument "-Dname="Host Controller" or in the case of a server instance the server nam might help.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3475) Properly integrate DMR configuration model with Host Environment and Server Environment
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-3475:
-------------------------------------
Summary: Properly integrate DMR configuration model with Host Environment and Server Environment
Key: AS7-3475
URL: https://issues.jboss.org/browse/AS7-3475
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.1.0.Final
When users update items in the DMR configuration model that are also reflected in ServerEnvironment or HostEnvironment, synchronization needs to take place. This can either be:
1) The XXEnvironment class is updated. For example if the server name is set via xml, that should be recorded in ServerEnvironment and any auto-created system properties (e.g. jboss.node.name) should be updated (but only if they were auto-created, not if set by the user.)
2) The configuration change is rejected. For example, the user tries to change jboss.home.dir via the <system-properties> elements in standalone.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months