[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException
by Anil Saldhana (JIRA)
Redeploy of Tomcat5 Service chokes with RuntimeException
--------------------------------------------------------
Key: JBAS-3517
URL: http://jira.jboss.com/jira/browse/JBAS-3517
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security, Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA
Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens.
You will notice the following Runtime Exception and the tomcat service fails to deploy.
==============================================================================================
13:33:30,421 INFO [Catalina] Initialization processed in 562 ms
13:33:30,421 INFO [StandardService] Starting service jboss.web
13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1
7
13:33:30,453 INFO [StandardHost] XML validation disabled
13:33:30,468 INFO [Catalina] Server startup in 47 ms
13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer
java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl
etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee
at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185)
at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
===================================================================================
Use the following api of PolicyContext in Tomcat5 service
http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h...
--
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
17 years, 11 months
[JBoss JIRA] Created: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
by David Kilzer (JIRA)
org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
--------------------------------------------------------------------------------------------------------
Key: JBAS-3775
URL: http://jira.jboss.com/jira/browse/JBAS-3775
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
Xerces-J 2.6.2
Reporter: David Kilzer
Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run outside of JBoss. The particular code run under JBoss was started through a Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the culprit (file path changed to protect the innocent):
java.io.FileNotFoundException: \c$\path\to\file.xml
at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
at java.net.URL.openStream(URL.java:1007)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
[...]
Here is some sample code that should reproduce the issue. Note the path used to create the java.io.File object.
File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
DocumentBuilderFactory factory = new org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlFile); // exception thrown under JBossAS
The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
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
17 years, 11 months
[JBoss JIRA] Created: (JBPORTAL-983) Upload of large files fails.
by Peter Johnson (JIRA)
Upload of large files fails.
----------------------------
Key: JBPORTAL-983
URL: http://jira.jboss.com/jira/browse/JBPORTAL-983
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Environment: Windows XP, JDK 1.5, JBoss AS 4.0.4GA
Reporter: Peter Johnson
Fix For: 2.4 Final
Using the CMS Admin portlet, I attempted to upload a zip file into a directory, as per section 3.2.9 of the User Guide. Initially I tried a zip ofabout 6MB containing many files, and eventually got down to a a zip file of about 500M with only a single Word document inside. The upload failed and an "SQLException: could not reset reader" error appeared (see forum post for stack trace).
I am, however, able to upload very small zip files.
--
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
17 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-820) Hardcoded Destination Manager Reference
by Juha Lindfors (JIRA)
Hardcoded Destination Manager Reference
---------------------------------------
Key: EJBTHREE-820
URL: http://jira.jboss.com/jira/browse/EJBTHREE-820
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - Patch 1
Environment: JBoss AS 4.0.5.GA + EJB 3.0 RC9 + JBoss Messaging
Reporter: Juha Lindfors
Priority: Minor
When deploying an MDB that has been configured wrongly with a non existing destination the dubious feature that creates a temporary destination automatically fails due to hard coded destination manager reference that no longer exists if JBoss Messaging is used instead of JBossMQ.
MessagingContainer:
protected void createTemporaryDestination(Class type, String jndiSuffix) throws Exception
513 ObjectName destinationManagerName = new ObjectName("jboss.mq:service=DestinationManager");
Apologies, did not check if this issue exists still with the current code in the head/trunk, just needed to write it down before I forget it.
--
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
17 years, 11 months