[JBoss JIRA] Commented: (JBAS-3381) The
by Dheeraj Uppalapati (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-3381?page=com.atlassian.jira.plug... ]
Dheeraj Uppalapati commented on JBAS-3381:
------------------------------------------
I'm not sure whether I'm posting my issue at the right place, but I'm facing the same issue when I'm trying to access the JMX console on the production server. But I'm able to access JMX console on the development. Can you please tell me how can I resolve this issue (OR) where should I start to resolve this issue.
18:27:40,126 INFO [Server] Starting JBoss (MX MicroKernel)...
18:27:40,126 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
18:27:40,141 INFO [Server] Home Dir: C:\jboss-4.0.5.GA
18:27:40,141 INFO [Server] Home URL: file:/C:/jboss-4.0.5.GA/
18:27:40,141 INFO [Server] Patch URL: null
18:27:40,141 INFO [Server] Server Name: default
18:27:40,141 INFO [Server] Server Home Dir: C:\jboss-4.0.5.GA\server\default
18:27:40,141 INFO [Server] Server Home URL: file:/C:/jboss-4.0.5.GA/server/default/
18:27:40,141 INFO [Server] Server Log Dir: C:\jboss-4.0.5.GA\server\default\log
18:27:40,141 INFO [Server] Server Temp Dir: C:\jboss-4.0.5.GA\server\default\tmp
18:27:40,141 INFO [Server] Root Deployment Filename: jboss-service.xml
18:27:40,782 INFO [ServerInfo] Java version: 1.5.0_22,Sun Microsystems Inc.
18:27:40,782 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_22-b03,Sun Microsystems Inc.
18:27:40,782 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
> The
> ----
>
> Key: JBAS-3381
> URL: https://jira.jboss.org/jira/browse/JBAS-3381
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: JBossAS-4.0.4.GA
> Environment: [sstark@sstark bin]$ $JAVA_HOME/bin/java -version
> java version "1.6.0-beta2"
> Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86)
> Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing)
> Reporter: Scott M Stark
> Assignee: Scott M Stark
> Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta1
>
>
> When bridging the jboss MBeanServer and the jdk platform MBeanServer using the javax.management.builder.initial and jboss.platform.mbeanserver settings:
> JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
> JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
> the following error can be seen tyring to display the mbeans on the jmx-console:
> 13:41:31,812 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception
> javax.management.InstanceNotFoundException: com.sun.management:type=HotSpotDiagnostic is not registered.
> at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
> at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:666)
> at org.jboss.system.server.jmx.LazyMBeanServer.getMBeanInfo(LazyMBeanServer.java:308)
> at org.jboss.jmx.adaptor.control.Server.getDomainData(Server.java:78)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.displayMBeans(HtmlAdaptorServlet.java:181)
> The problem is that the selection of the correct MBeanServer is not considering all of the possible domains. Currently only domains prefixed with "java" are considered to belong to the platform MBeanServer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBAS-7659) Timeouts in org.jboss.test.deployers.seam.test.Seam*ExampleUnitTestCase
by Brian Stansberry (JIRA)
Timeouts in org.jboss.test.deployers.seam.test.Seam*ExampleUnitTestCase
-----------------------------------------------------------------------
Key: JBAS-7659
URL: https://jira.jboss.org/jira/browse/JBAS-7659
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
SeamDvdExampleUnitTestCase and SeamNumberguessExampleUnitTestCase, both part of the tests-profileservice target, are timing out on the hudson runs. They pass for me locally.
Looking through the logs at http://hudson.qa.jboss.com/hudson/job/JBoss-AS-6.0.x-testSuite-sun16/524/... it seems the problem is an inability to resolve an xsd:
2010-01-26 13:23:42,577 DEBUG [org.jbpm.persistence.db.DbPersistenceService] (WorkerThread#0[10.16.95.21:39912]) closing hibernate session
2010-01-26 13:23:42,587 DEBUG [org.jbpm.svc.Services] (WorkerThread#0[10.16.95.21:39912]) closing service 'tx': org.jbpm.tx.TxService@9ddd71
2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) instantiating Seam component: org.jboss.seam.core.resourceLoader
2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) initializing new instance of: org.jboss.seam.core.resourceLoader
2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) done initializing: org.jboss.seam.core.resourceLoader
2010-01-26 13:23:42,588 DEBUG [org.jboss.seam.util.Resources] (WorkerThread#0[10.16.95.21:39912]) Loaded resource from context classloader: newuser.jpdl.xml
2010-01-26 13:23:42,588 DEBUG [org.jbpm.configuration.JbpmContextInfo] (WorkerThread#0[10.16.95.21:39912]) creating jbpm context with service factories '[]'
2010-01-26 13:23:42,588 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) creating org.jbpm.JbpmContext@1600573
2010-01-26 13:23:42,592 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) resolving schema reference publicId(null) systemId(http://jboss.com/products/seam/pageflow-2.1.xsd)
2010-01-26 13:23:42,592 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) original systemId as input source
[bes@besdev tmp]$ grep 13:23:5 server.log | more
[bes@besdev tmp]$ grep 13:24 server.log | more
[bes@besdev tmp]$ grep 13:25 server.log | more
[bes@besdev tmp]$ grep 13:26 server.log | more
2010-01-26 13:26:51,638 WARN [org.jbpm.jpdl.xml.JpdlXmlReader] (WorkerThread#0[10.16.95.21:39912]) process parse warning: line 8: schema_reference.4: Failed to read schema document 'http://jboss.com/products/seam/pageflow-2.1.xsd', because 1) could not f
nd the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
2010-01-26 13:26:51,639 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) closing jbpmContext org.jbpm.JbpmContext@1600573
2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) instantiating Seam component: org.jboss.seam.core.resourceLoader
2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) initializing new instance of: org.jboss.seam.core.resourceLoader
2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) done initializing: org.jboss.seam.core.resourceLoader
2010-01-26 13:26:51,640 DEBUG [org.jboss.seam.util.Resources] (WorkerThread#0[10.16.95.21:39912]) Loaded resource from context classloader: checkout.jpdl.xml
2010-01-26 13:26:51,640 DEBUG [org.jbpm.configuration.JbpmContextInfo] (WorkerThread#0[10.16.95.21:39912]) creating jbpm context with service factories '[]'
2010-01-26 13:26:51,640 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) creating org.jbpm.JbpmContext@16701a2
2010-01-26 13:26:51,651 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) resolving schema reference publicId(null) systemId(http://jboss.com/products/seam/pageflow-2.1.xsd)
2010-01-26 13:26:51,651 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) original systemId as input source
[bes@besdev tmp]$ grep 13:27 server.log | more
[bes@besdev tmp]$ grep 13:28 server.log | more
2010-01-26 13:28:12,890 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#1[10.16.95.21:35891]) WorkerThread#1[10.16.95.21:35891] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35891,localport=4446].1615a5f]
2010-01-26 13:28:12,904 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#2[10.16.95.21:35890]) WorkerThread#2[10.16.95.21:35890] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35890,localport=4446].743bb0]
2010-01-26 13:28:12,926 DEBUG [org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget] (WorkerThread#1[10.16.95.21:35892]) new StreamingTarget: InvokerLocator [socket://10.16.95.21:4446/?dataType=invocation&enableTcpNoDelay=true&marsh
ller=org.jboss.invocation.unified.marshall.InvocationMarshaller&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
2010-01-26 13:28:12,953 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#1[10.16.95.21:35892]) WorkerThread#1[10.16.95.21:35892] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35892,localport=4446].1898f52]
2010-01-26 13:28:12,986 DEBUG [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#2[10.16.95.21:35893]) invoke, payload: {DeploymentTargetID=names=[jboss-seam-jpa.war], copyContent=false, description=file:/mnt/hudson_workspac
/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/output/lib/jboss-seam-jpa.war, clientAddress=/10.16.95.21}, parameter: distribute
2010-01-26 13:28:12,986 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#2[10.16.95.21:35893]) Begin distribute, content url: file:/mnt/hudson_workspace/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/outp
t/lib/jboss-seam-jpa.war
The logging beginning at 13:2812 is the next test starting.
I suspect an environmental issue on the hudson server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBAS-5041) MDB transaction timeout from method-attributes
by Adrian Brock (JIRA)
MDB transaction timeout from method-attributes
----------------------------------------------
Key: JBAS-5041
URL: http://jira.jboss.com/jira/browse/JBAS-5041
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: EJB2, EJB3
Affects Versions: JBossAS-4.2.2.GA
Reporter: Adrian Brock
The parent task was not implemented correctly. Instead a new activation-config-property was introduced on
our jms rar.
What is really required is that there should be a JBossMessageEndpoint interface that we implement
that allows a getTransactionTimeout(Method) for use by the inbound rars.
I'd guess the activation-config-property should override the jboss.xml or EJB3 annotation.
Additionally when the MessageEndpoint starts the transaction (rather than the rar in our JMS rar)
it should also look at this configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Resolved: (JBAS-7704) Injecting Session Beans into Servlet in EAR archiv throws exception
by Marius Bogoevici (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7704?page=com.atlassian.jira.plug... ]
Marius Bogoevici resolved JBAS-7704.
------------------------------------
Resolution: Done
Assignee: Martin Gencur (was: Marius Bogoevici)
fixed w/rev 100656.
Martin, I tested you app with it and it works (well, at least the injection part :) ). Please validate and close.
> Injecting Session Beans into Servlet in EAR archiv throws exception
> -------------------------------------------------------------------
>
> Key: JBAS-7704
> URL: https://jira.jboss.org/jira/browse/JBAS-7704
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBossAS 6.0.0.M1 udpated with current version of Weld core
> Reporter: Martin Gencur
> Assignee: Martin Gencur
> Fix For: JBossAS-6.0.0.M2
>
> Attachments: pastietrimmed.zip
>
>
> Injecting Session bean using either @Inject annotation directly or Instance<T> with following .get() into Servlet in EAR archiv throws an exception
> Steps to reproduce:
> 1) download attached zip file and unpack it among weld/jsf examples
> 2) run "mvn clean package" in root directory of the new project
> 3) deploy resulting weld-pastie.ear into JBossAS default configuration
> 4) go to localhost: http://localhost:8080/weld-pastie/download //which invokes the servlet
> 5) now you can see following exception at jboss console:
> 08:52:56,537 ERROR [[/weld-pastie]] StandardWrapper.Throwable
> java.lang.NullPointerException
> at org.jboss.weld.examples.pastie.DownloadServlet.init(DownloadServlet.java:31)
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
> 08:52:56,538 ERROR [[DownloadServlet]] Allocate exception for servlet DownloadServlet
> java.lang.NullPointerException
> at org.jboss.weld.examples.pastie.DownloadServlet.init(DownloadServlet.java:31)
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Moved: (JBAS-7704) Injecting Session Beans into Servlet in EAR archiv throws exception
by Marius Bogoevici (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7704?page=com.atlassian.jira.plug... ]
Marius Bogoevici moved WELDINT-42 to JBAS-7704:
-----------------------------------------------
Project: JBoss Application Server (was: Weld Integration)
Key: JBAS-7704 (was: WELDINT-42)
Fix Version/s: JBossAS-6.0.0.M2
(was: 6.0.0.Beta7)
Security: Public
> Injecting Session Beans into Servlet in EAR archiv throws exception
> -------------------------------------------------------------------
>
> Key: JBAS-7704
> URL: https://jira.jboss.org/jira/browse/JBAS-7704
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBossAS 6.0.0.M1 udpated with current version of Weld core
> Reporter: Martin Gencur
> Assignee: Marius Bogoevici
> Fix For: JBossAS-6.0.0.M2
>
> Attachments: pastietrimmed.zip
>
>
> Injecting Session bean using either @Inject annotation directly or Instance<T> with following .get() into Servlet in EAR archiv throws an exception
> Steps to reproduce:
> 1) download attached zip file and unpack it among weld/jsf examples
> 2) run "mvn clean package" in root directory of the new project
> 3) deploy resulting weld-pastie.ear into JBossAS default configuration
> 4) go to localhost: http://localhost:8080/weld-pastie/download //which invokes the servlet
> 5) now you can see following exception at jboss console:
> 08:52:56,537 ERROR [[/weld-pastie]] StandardWrapper.Throwable
> java.lang.NullPointerException
> at org.jboss.weld.examples.pastie.DownloadServlet.init(DownloadServlet.java:31)
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
> 08:52:56,538 ERROR [[DownloadServlet]] Allocate exception for servlet DownloadServlet
> java.lang.NullPointerException
> at org.jboss.weld.examples.pastie.DownloadServlet.init(DownloadServlet.java:31)
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months