[jira] [Commented] (AXIS2-5219) Deploying SampleService as a folder throws java.lang.ClassCastException

2012-05-01 Thread Kishanthan Thangarajah (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265694#comment-13265694
 ] 

Kishanthan Thangarajah commented on AXIS2-5219:
---

Hi,
This is fixed in later releases of axis2(v1.5.5) to prevent such class cast 
exceptions. Can you try with a new release?

Thanks,
Kishanthan.  

 Deploying SampleService as a folder throws java.lang.ClassCastException
 ---

 Key: AXIS2-5219
 URL: https://issues.apache.org/jira/browse/AXIS2-5219
 Project: Axis2
  Issue Type: Bug
Affects Versions: 1.5
 Environment: Windows XP
Reporter: John Zoetebier
Priority: Minor
  Labels: documentation

 Page site/docs/userguide-buildingservices.html says:
 Finally, deploy the service by copying the SampleService directory to the 
 webapps/axis2/WEB-INF/services directory on the servlet engine
 This throws an exception:
 =
 [INFO] The SampleService service, which is not valid, caused 
 java.lang.ClassCastException: org.apache.axis2.classloader.JarFileClassLoader 
 c
 annot be cast to org.apache.axis2.deployment.DeploymentClassLoader
 at 
 org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:131)
 at 
 org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:101)
 at 
 org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:178)
 at 
 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82)
 at 
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at 
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:661)
 at 
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at 
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:337)
 at 
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:241)
 at 
 org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131)
 at 
 org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:284)
 at 
 org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
 at 
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:567)
 at 
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:452)
 at 
 org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1068)
 at 
 org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:900)
 at 
 org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3823)
 at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4087)
 at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
 at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
 at 
 org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
 at 
 org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:800)
 at 
 org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:695)
 at 
 org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1106)
 at 
 org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
 at 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at 
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1019)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at 
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1011)
 at 
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:440)
 at 
 org.apache.catalina.core.StandardService.start(StandardService.java:450)
 at 
 org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
 

[jira] [Resolved] (AXIS2-5309) Usr jsr311-api version 1.1.1

2012-05-01 Thread Sagara Gunathunga (JIRA)

 [ 
https://issues.apache.org/jira/browse/AXIS2-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sagara Gunathunga  resolved AXIS2-5309.
---

   Resolution: Fixed
Fix Version/s: 1.6.3
   1.7.0
 Assignee: Sagara Gunathunga 

Fixed in r1332545.

 Usr jsr311-api version 1.1.1
 

 Key: AXIS2-5309
 URL: https://issues.apache.org/jira/browse/AXIS2-5309
 Project: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.2
Reporter: Hendy Irawan
Assignee: Sagara Gunathunga 
 Fix For: 1.7.0, 1.6.3


 I recently had a conflict in my project where Axis2 wanted jsr311-api version 
 1.0 where the other component (specifically neo4j-rest-graph 1.6) wanted 
 jsr311-api version 1.1.1.
 Manually overriding axis2 and using the jsr311-api 1.1.1 makes the whole app 
 work fine.
 Since axis2 works fine with 1.1.1 and it is the latest version of jsr311-api, 
 this should be the jsr311-api version Axis2 depends on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Commented] (AXIS2-5310) Axis2.0 : 1.6.2 : Memory Leak Issue

2012-05-01 Thread Andreas Veithen (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265708#comment-13265708
 ] 

Andreas Veithen commented on AXIS2-5310:


Do you have any evidence that the class loader is indeed not garbage collected 
and that it's Axis2's fault (and not your service's)? Note that the messages 
generated by Tomcat are not evidence because they are not reliable as explained 
above.

 Axis2.0 : 1.6.2 : Memory Leak Issue 
 

 Key: AXIS2-5310
 URL: https://issues.apache.org/jira/browse/AXIS2-5310
 Project: Axis2
  Issue Type: Bug
  Components: databinding, transports
Affects Versions: 1.6.2
 Environment: Axis2.0 version used : 1.6.2
 NSJSP7.0 and ITP webserver 7.2 for HP Nonstop Tandem
Reporter: Santhosh
  Labels: Memory, leak, performance
   Original Estimate: 972h
  Remaining Estimate: 972h

 I'm facing below error message after deploying a webservice using Axis2.0 in 
 webserver.
 Mon, Apr 30, 16:08:27;$Z0QF;INFO;StandardService#stopInternal;Stopping 
 service NSJSP
 Mon, Apr 30, 
 16:08:29;$Z0QF;SEVERE;WebappClassLoader#clearReferencesThreads;The web 
 application [/PSAPI-V1-0/axis2] is still processing a request that has yet to 
 finish. This is very likely to create a memory leak. You can control the time 
 allowed for requests to finish by using the unloadDelay attribute of the 
 standard Context implementation.
 Mon, Apr 30, 
 16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web 
 application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type 
 [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@2465e5]) and a value of 
 type [org.apache.axis2.context.MessageContext] (value [[MessageContext: 
 logID=3fecb85757bee1e6fd9cdc8eb6a0e146d5c1eaa7dd28d0e7]]) but failed to 
 remove it when the web application was stopped. Threads are going to be 
 renewed over time to try and avoid a probable memory leak.
 Mon, Apr 30, 
 16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web 
 application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type 
 [org.apache.axiom.util.UIDGenerator$1] (value 
 [org.apache.axiom.util.UIDGenerator$1@b103dd]) and a value of type [long[]] 
 (value [[J@174d4c9]) but failed to remove it when the web application was 
 stopped. Threads are going to be renewed over time to try and avoid a 
 probable memory leak.
 Mon, Apr 30, 16:08:29;$Z0QF;INFO;AbstractProtocolHandler#stop;Stopping 
 ProtocolHandler [http-bio-0]
 As per error logs i understand that Axis2.0 - framework is not able to 
 delete/failed to cleanup a thread. Please provide me with resolution if any.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Commented] (AXIS2-5309) Usr jsr311-api version 1.1.1

2012-05-01 Thread Hendy Irawan (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265713#comment-13265713
 ] 

Hendy Irawan commented on AXIS2-5309:
-

Thank you Sagara ! :)

 Usr jsr311-api version 1.1.1
 

 Key: AXIS2-5309
 URL: https://issues.apache.org/jira/browse/AXIS2-5309
 Project: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.2
Reporter: Hendy Irawan
Assignee: Sagara Gunathunga 
 Fix For: 1.7.0, 1.6.3


 I recently had a conflict in my project where Axis2 wanted jsr311-api version 
 1.0 where the other component (specifically neo4j-rest-graph 1.6) wanted 
 jsr311-api version 1.1.1.
 Manually overriding axis2 and using the jsr311-api 1.1.1 makes the whole app 
 work fine.
 Since axis2 works fine with 1.1.1 and it is the latest version of jsr311-api, 
 this should be the jsr311-api version Axis2 depends on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Commented] (AXIS2-5309) Usr jsr311-api version 1.1.1

2012-05-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265718#comment-13265718
 ] 

Hudson commented on AXIS2-5309:
---

Integrated in Axis2 #1414 (See [https://builds.apache.org/job/Axis2/1414/])
Fixed AXIS2-5309.

* Changed JSR311-api version.
* Removed  JSR311-api from HTTP transport test cases. (Revision 1332545)

 Result = SUCCESS
sagara : 
Files : 
* /axis/axis2/java/core/trunk/modules/kernel/pom.xml
* /axis/axis2/java/core/trunk/modules/parent/pom.xml
* 
/axis/axis2/java/core/trunk/modules/transport/http/test/org/apache/axis2/transport/http/HTTPSenderTest.java


 Usr jsr311-api version 1.1.1
 

 Key: AXIS2-5309
 URL: https://issues.apache.org/jira/browse/AXIS2-5309
 Project: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.2
Reporter: Hendy Irawan
Assignee: Sagara Gunathunga 
 Fix For: 1.7.0, 1.6.3


 I recently had a conflict in my project where Axis2 wanted jsr311-api version 
 1.0 where the other component (specifically neo4j-rest-graph 1.6) wanted 
 jsr311-api version 1.1.1.
 Manually overriding axis2 and using the jsr311-api 1.1.1 makes the whole app 
 work fine.
 Since axis2 works fine with 1.1.1 and it is the latest version of jsr311-api, 
 this should be the jsr311-api version Axis2 depends on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Assigned] (AXIS2-5303) In case of multiple Axis2 instances, some of them fail during parallel startup, as result of NPE in TempFileManager

2012-05-01 Thread Sagara Gunathunga (JIRA)

 [ 
https://issues.apache.org/jira/browse/AXIS2-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sagara Gunathunga  reassigned AXIS2-5303:
-

Assignee: Sagara Gunathunga 

 In case of multiple Axis2 instances, some of them fail during parallel 
 startup, as result of NPE in TempFileManager
 ---

 Key: AXIS2-5303
 URL: https://issues.apache.org/jira/browse/AXIS2-5303
 Project: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.0
 Environment: AIX 6, WebSphere AS 7.0
Reporter: Stoyan Tsonev
Assignee: Sagara Gunathunga 

 We are running WebSphere cluster with multiple instances of Axis2.
 During parallel start-up all of them (together) are trying to do temp 
 folders clean-up in the static initializer of TempFileManager
 But some instances are faster, some are slower and as result of this 
 time-race slow instances can end-up in non-functional state (see the log 
 bellow).
 Solution: A simple check in method  private static void recursiveDelete(File 
 rootDir) after File[] files = rootDir.listFiles();
 if (files != null) { ...}
 should fix the issue.
 --- attached log --
 java.lang.ExceptionInInitializerError
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
   at org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:227)
   at 
 org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:168)
   at 
 org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:852)
   at 
 org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
   at 
 org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:70)
   at 
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
   at 
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813)
   at 
 org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:264)
   at 
 org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:69)
   at 
 org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:64)
   at 
 org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:158)
   at 
 org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:228)
   at 
 org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
   at 
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:584)
   at 
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:454)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
   at 
 com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
   at 
 com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
   at 
 com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
   at 
 com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
   at 
 com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)
   at 
 com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)
   at 
 com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
   at 
 com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
   at 
 com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
   at 
 com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
   at 
 com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
   at 
 com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)
   at 
 com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
   at 
 

[jira] [Commented] (AXIS2-3278) Allow Customizable WSDL generation error messages

2012-05-01 Thread Kishanthan Thangarajah (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265740#comment-13265740
 ] 

Kishanthan Thangarajah commented on AXIS2-3278:
---

Hi,
The scenario for exposeServiceMetadata returns 403 (forbidden) error code. 
For this particular scenario, we can return a 404, if the useOriginalwsdl 
property is set true and no wsdl is found. WDYT?

Kishanthan.

 Allow Customizable WSDL generation error messages
 -

 Key: AXIS2-3278
 URL: https://issues.apache.org/jira/browse/AXIS2-3278
 Project: Axis2
  Issue Type: New Feature
  Components: wsdl
Affects Versions: 1.3
 Environment: Axis2 (1.3)
Reporter: Nathan Hook
Assignee: Deepal Jayasinghe
Priority: Minor

 When setting the value useOriginalwsdl to true in a services.xml and not 
 providing a wsdl file in your directory the following message occurs:
 Unable to generate WSDL 1.1 for this serviceIf you wish Axis2 to 
 automatically generate the WSDL 1.1, then please +set  useOriginalwsdl as 
 false in your services.xml
 However, it would be better if a customizable error message (including a 
 blank message) could be returned or even better allow the behavior to return 
 different http error codes like 404 where the wsdl is effectively hidden 
 without giving a clue that it exists.
 A work around for this is to create a filter that will check to see if 
 someone is try to access the wsdl file directly and then return a 404 or what 
 ever type of message they chose.
 Here is an example filter class:
 import java.io.*;
 import java.util.*;
 import javax.servlet.*;
 import javax.servlet.http.*;
 public class WebServiceSecurityFilter implements Filter
 {
   private static org.apache.log4j.Logger log = 
 org.apache.log4j.Logger.getLogger(WebServiceSecurityFilter.class);
   
   public void doFilter(ServletRequest request, ServletResponse response, 
 FilterChain filterChain) throws IOException, ServletException
   {
   HttpServletRequest httpRequest = (HttpServletRequest)request;
   
   if(!httpRequest.getQueryString().contains(wsdl))
   {
   filterChain.doFilter(request, response);
   }
   else
   {
   log.debug(WebServiceSecurityFilter - Unauthorized WSDL 
 Access Attempt);
   log.debug(remote ip:  + address);
   
   HttpServletResponse httpResponse = 
 (HttpServletResponse)response;
   
 httpResponse.setStatus(HttpServletResponse.SC_NOT_FOUND);
   
   RequestDispatcher dispatcher = 
 request.getRequestDispatcher(/WEB-INF/error_pages/404.html);
   dispatcher.forward(request, response);
   }
   }
   
   public void init(FilterConfig config)
   {
   
   }
   
   public void destroy()
   {
   
   }
 }
 Thank you for your time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Commented] (AXIS2-5303) In case of multiple Axis2 instances, some of them fail during parallel startup, as result of NPE in TempFileManager

2012-05-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265770#comment-13265770
 ] 

Hudson commented on AXIS2-5303:
---

Integrated in Axis2 #1415 (See [https://builds.apache.org/job/Axis2/1415/])
AXIS2-5303 - Fixed possible NullPointerException (Revision 1332587)

 Result = SUCCESS
sagara : 
Files : 
* 
/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/deployment/util/TempFileManager.java


 In case of multiple Axis2 instances, some of them fail during parallel 
 startup, as result of NPE in TempFileManager
 ---

 Key: AXIS2-5303
 URL: https://issues.apache.org/jira/browse/AXIS2-5303
 Project: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.0
 Environment: AIX 6, WebSphere AS 7.0
Reporter: Stoyan Tsonev
Assignee: Sagara Gunathunga 

 We are running WebSphere cluster with multiple instances of Axis2.
 During parallel start-up all of them (together) are trying to do temp 
 folders clean-up in the static initializer of TempFileManager
 But some instances are faster, some are slower and as result of this 
 time-race slow instances can end-up in non-functional state (see the log 
 bellow).
 Solution: A simple check in method  private static void recursiveDelete(File 
 rootDir) after File[] files = rootDir.listFiles();
 if (files != null) { ...}
 should fix the issue.
 --- attached log --
 java.lang.ExceptionInInitializerError
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
   at org.apache.axis2.deployment.util.Utils.createTempFile(Utils.java:227)
   at 
 org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java:168)
   at 
 org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:852)
   at 
 org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
   at 
 org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:70)
   at 
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
   at 
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813)
   at 
 org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:264)
   at 
 org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:69)
   at 
 org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:64)
   at 
 org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:158)
   at 
 org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:228)
   at 
 org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
   at 
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:584)
   at 
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:454)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:358)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:169)
   at 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1809)
   at 
 com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:98)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:1038)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:959)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:638)
   at 
 com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:436)
   at 
 com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:304)
   at 
 com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
   at 
 com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
   at 
 com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)
   at 
 com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)
   at 
 com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)
   at 
 com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)
   at 
 com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1127)
   at 
 com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)
   at 
 com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)
   

[jira] [Commented] (AXIS2-5306) No schemaLocation for import of http://rmi.java/xsd

2012-05-01 Thread Sameer Tiwari (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265828#comment-13265828
 ] 

Sameer Tiwari commented on AXIS2-5306:
--

Can somebody please have a quick look and respond on this issue?

 No schemaLocation for import of http://rmi.java/xsd
 ---

 Key: AXIS2-5306
 URL: https://issues.apache.org/jira/browse/AXIS2-5306
 Project: Axis2
  Issue Type: Bug
  Components: databinding
Affects Versions: 1.6.2
Reporter: Sameer Tiwari
Priority: Critical
 Attachments: notification-service.wsdl


 I have attached a wsdl (notification-service) used by me
 Axis2 version details: Axis2 1.6.1
 I am using following command to generate server side classes wsdl2java.sh
 **./bin/wsdl2java.sh -uri notification-service.wsdl -d adb -s -ss -sd -ssi -o 
 samples/notification-service-adb/src**
 On doing so i get following error:
 **[WARN] No schemaLocation for import of http://io.java/xsd; compilation may 
 fail**
 [WARN] No schemaLocation for import of 
 http://dto.nbi.service.xyz.abc.com/xsd; compilation may fail
 [WARN] No schemaLocation for import of 
 http://response.types.functions.xyz.abcwer/xsd; compilation may fail
 [WARN] No schemaLocation for import of 
 http://service.notification.nbi.xyz.abc.com; compilation may fail
 **[WARN] No schemaLocation for import of http://rmi.java/xsd; compilation may 
 fail**
 [WARN] No schemaLocation for import of 
 http://notification.dto.nbi.service.xyz.abc.com/xsd; compilation may fail
 [WARN] No schemaLocation for import of 
 http://dto.nbi.service.xyz.abc.com/xsd; compilation may fail
  
 From ant build i prepare *aar* file and copy it to *repository\services* 
 folder and start axis2 server, after this when i send request from my 
 application to axis2 i get following error:
 faultstringProhibited package name: java.rmi.xsd/faultstring
 Could you please provide me any pointer on how to get over this issue without 
 having to modify WSDL file!!
 Thanks,
 Sameer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



[jira] [Updated] (AXIS2-3278) Allow Customizable WSDL generation error messages

2012-05-01 Thread Kishanthan Thangarajah (JIRA)

 [ 
https://issues.apache.org/jira/browse/AXIS2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishanthan Thangarajah updated AXIS2-3278:
--

Attachment: AXIS2-3278.patch

This patch includes the proposed improvement. If the useOriginalWsdl is set to 
true and if the wsdl file is not found, then 404 status will be returned.

 Allow Customizable WSDL generation error messages
 -

 Key: AXIS2-3278
 URL: https://issues.apache.org/jira/browse/AXIS2-3278
 Project: Axis2
  Issue Type: New Feature
  Components: wsdl
Affects Versions: 1.3
 Environment: Axis2 (1.3)
Reporter: Nathan Hook
Assignee: Deepal Jayasinghe
Priority: Minor
 Attachments: AXIS2-3278.patch


 When setting the value useOriginalwsdl to true in a services.xml and not 
 providing a wsdl file in your directory the following message occurs:
 Unable to generate WSDL 1.1 for this serviceIf you wish Axis2 to 
 automatically generate the WSDL 1.1, then please +set  useOriginalwsdl as 
 false in your services.xml
 However, it would be better if a customizable error message (including a 
 blank message) could be returned or even better allow the behavior to return 
 different http error codes like 404 where the wsdl is effectively hidden 
 without giving a clue that it exists.
 A work around for this is to create a filter that will check to see if 
 someone is try to access the wsdl file directly and then return a 404 or what 
 ever type of message they chose.
 Here is an example filter class:
 import java.io.*;
 import java.util.*;
 import javax.servlet.*;
 import javax.servlet.http.*;
 public class WebServiceSecurityFilter implements Filter
 {
   private static org.apache.log4j.Logger log = 
 org.apache.log4j.Logger.getLogger(WebServiceSecurityFilter.class);
   
   public void doFilter(ServletRequest request, ServletResponse response, 
 FilterChain filterChain) throws IOException, ServletException
   {
   HttpServletRequest httpRequest = (HttpServletRequest)request;
   
   if(!httpRequest.getQueryString().contains(wsdl))
   {
   filterChain.doFilter(request, response);
   }
   else
   {
   log.debug(WebServiceSecurityFilter - Unauthorized WSDL 
 Access Attempt);
   log.debug(remote ip:  + address);
   
   HttpServletResponse httpResponse = 
 (HttpServletResponse)response;
   
 httpResponse.setStatus(HttpServletResponse.SC_NOT_FOUND);
   
   RequestDispatcher dispatcher = 
 request.getRequestDispatcher(/WEB-INF/error_pages/404.html);
   dispatcher.forward(request, response);
   }
   }
   
   public void init(FilterConfig config)
   {
   
   }
   
   public void destroy()
   {
   
   }
 }
 Thank you for your time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org



Build failed in Jenkins: Rampart #866

2012-05-01 Thread Apache Jenkins Server
See https://builds.apache.org/job/Rampart/866/

--
[...truncated 80 lines...]
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-core/0.8-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-core/0.8-SNAPSHOT/maven-metadata.xml
 (2 KB at 1.1 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-core/0.8-SNAPSHOT/apache-mime4j-core-0.8-20120501.004225-253.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-core/0.8-SNAPSHOT/apache-mime4j-core-0.8-20120501.004225-253.pom
 (3 KB at 16.5 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/james/apache-mime4j-project/0.8-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-project/0.8-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-project/0.8-SNAPSHOT/maven-metadata.xml
 (825 B at 1.7 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-project/0.8-SNAPSHOT/apache-mime4j-project-0.8-20120501.004208-281.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/james/apache-mime4j-project/0.8-SNAPSHOT/apache-mime4j-project-0.8-20120501.004208-281.pom
 (10 KB at 64.0 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/ws/commons/axiom/axiom-impl/1.2.14-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/ws/commons/axiom/axiom-impl/1.2.14-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/ws/commons/axiom/axiom-impl/1.2.14-SNAPSHOT/maven-metadata.xml
 (2 KB at 2.3 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/ws/commons/axiom/axiom-impl/1.2.14-SNAPSHOT/axiom-impl-1.2.14-20120501.201819-86.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/ws/commons/axiom/axiom-impl/1.2.14-SNAPSHOT/axiom-impl-1.2.14-20120501.201819-86.pom
 (8 KB at 43.8 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/maven-metadata.xml
 (283 B at 0.5 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/XmlSchema-1.4.8-SNAPSHOT.pom
Downloading: 
http://repository.apache.org/snapshots/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/XmlSchema-1.4.8-SNAPSHOT.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/ws/commons/schema/XmlSchema/1.4.8-SNAPSHOT/XmlSchema-1.4.8-SNAPSHOT.pom
 (18 KB at 76.1 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/neethi/neethi/3.0.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/neethi/neethi/3.0.3-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/neethi/neethi/3.0.3-SNAPSHOT/maven-metadata.xml
 (360 B at 0.2 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/neethi/neethi/3.0.3-SNAPSHOT/neethi-3.0.3-20120501.203245-71.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/neethi/neethi/3.0.3-SNAPSHOT/neethi-3.0.3-20120501.203245-71.pom
 (14 KB at 43.0 KB/sec)
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/woden/woden-api/1.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/woden/woden-api/1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/woden/woden-api/1.0-SNAPSHOT/maven-metadata.xml
 (775 B at 0.9 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/woden/woden-api/1.0-SNAPSHOT/woden-api-1.0-20120402.023555-405.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/woden/woden-api/1.0-SNAPSHOT/woden-api-1.0-20120402.023555-405.pom
 (3 KB at 15.2 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/woden/woden/1.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://shibboleth.internet2.edu/downloads/maven2/org/apache/woden/woden/1.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/woden/woden/1.0-SNAPSHOT/maven-metadata.xml
 (598 B at 0.8 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/woden/woden/1.0-SNAPSHOT/woden-1.0-20120402.023554-405.pom
Downloaded: 
http://repository.apache.org/snapshots/org/apache/woden/woden/1.0-SNAPSHOT/woden-1.0-20120402.023554-405.pom
 (14 KB at 81.9 KB/sec)
Downloading: 

Build failed in Jenkins: Axis2-trunk-java-1.6 #879

2012-05-01 Thread Apache Jenkins Server
See https://builds.apache.org/job/Axis2-trunk-java-1.6/879/changes

Changes:

[veithen] Added an integration test for Badgerfish with a POJO service.

--
[...truncated 6454 lines...]
[INFO] org/apache/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/axis2/ already added, skipping
[INFO] org/apache/axis2/clustering/ already added, skipping
[INFO] org/apache/axis2/clustering/management/ already added, skipping
[INFO] org/apache/axis2/clustering/state/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/axis2/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/axis2/ already added, skipping
[INFO] org/apache/axis2/handlers/ already added, skipping

mojoStarted 
org.apache.maven.plugins:maven-install-plugin:2.3(default-install)[INFO] 
Installing 
https://builds.apache.org/job/Axis2-trunk-java-1.6/ws/axis2/pom.xml to 
https://builds.apache.org/job/Axis2-trunk-java-1.6/ws/.repository/org/apache/axis2/axis2/1.7.0-SNAPSHOT/axis2-1.7.0-SNAPSHOT.pom
[INFO] Installing 
https://builds.apache.org/job/Axis2-trunk-java-1.6/ws/axis2/target/axis2-1.7.0-SNAPSHOT.jar
 to 
https://builds.apache.org/job/Axis2-trunk-java-1.6/ws/.repository/org/apache/axis2/axis2/1.7.0-SNAPSHOT/axis2-1.7.0-SNAPSHOT.jar

[INFO] 
[INFO] --- maven-install-plugin:2.3:install (default-install) @ axis2 ---
mojoSucceeded org.apache.maven.plugins:maven-install-plugin:2.3(default-install)
projectSucceeded org.apache.axis2:axis2:1.7.0-SNAPSHOT
sessionEnded
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Axis2 - Parent . SUCCESS [32.168s]
[INFO] Apache Axis2 - Resource bundle  SUCCESS [3.739s]
[INFO] Apache Axis2 - Kernel . SUCCESS [37.869s]
[INFO] Apache Axis2 - Data Binding ... SUCCESS [10.176s]
[INFO] Apache Axis2 - Transport - Local .. SUCCESS [5.407s]
[INFO] Apache Axis2 - Transport - HTTP ... SUCCESS [11.076s]
[INFO] Apache Axis2 - Code Generation  SUCCESS [10.564s]
[INFO] Apache Axis2 - ADB Codegen  SUCCESS [34.124s]
[INFO] Apache Axis2 - Addressing . SUCCESS [6.354s]
[INFO] Apache Axis2 - Java2WSDL .. SUCCESS [11.642s]
[INFO] Apache Axis2 - tool - Repository Maven Plugin . SUCCESS [10.321s]
[INFO] Apache Axis2 - Fast Infoset ... SUCCESS [19.077s]
[INFO] Apache Axis2 - Clustering . SUCCESS [1:13.980s]
[INFO] Apache Axis2 - Scripting .. SUCCESS [14.055s]
[INFO] Apache Axis2 - JAXB-RI Data Binding ... SUCCESS [15.058s]
[INFO] Apache Axis2 - SAAJ ... SUCCESS [21.117s]
[INFO] Apache Axis2 - Metadata ... SUCCESS [29.961s]
[INFO] Apache Axis2 - JAXWS .. SUCCESS [42.892s]
[INFO] Apache Axis2 - Test Utilities . SUCCESS [1.880s]
[INFO] Apache Axis2 - XMLBeans Data Binding .. SUCCESS [40.523s]
[INFO] Apache Axis2 - tool - WSDL2Code Maven Plugin .. SUCCESS [6.718s]
[INFO] Apache Axis2 - JAXWS Integration Tests  SUCCESS [11:02.350s]
[INFO] Apache Axis2 - JiBX Data Binding .. SUCCESS [19.745s]
[INFO] Apache Axis2 - MTOM Policy  SUCCESS [9.019s]
[INFO] Apache Axis2 - spring . SUCCESS [3.293s]
[INFO] Apache Axis2 - OSGi Integration ... SUCCESS [4.917s]
[INFO] Apache Axis2 - Integration  SUCCESS [10:27.746s]
[INFO] Apache Axis2 - JSON ... SUCCESS [7.866s]
[INFO] Apache Axis2 - MEX  SUCCESS [2.968s]
[INFO] Apache Axis2 - MTOM Policy module . SUCCESS [3.109s]
[INFO] Apache Axis2 - Ping ... SUCCESS [2.497s]
[INFO] Apache Axis2 - Version Service  SUCCESS [2.867s]
[INFO] Apache Axis2 - SOAP Monitor Servlet ... SUCCESS [3.418s]
[INFO] Apache Axis2 - SOAP Monitor Module  SUCCESS [2.162s]
[INFO] Apache Axis2 - tool - AAR Maven Plugin  SUCCESS [3.885s]
[INFO] Apache Axis2 - tool - Ant Plugin .. SUCCESS [19.992s]
[INFO] Apache Axis2 - tool - Eclipse Codegen Plugin .. SUCCESS [2:30.991s]
[INFO] Apache Axis2 - tool - Eclipse service Plugin .. SUCCESS [2:43.425s]
[INFO] Apache Axis2 - tool - Intellij IDEA Plugin  SUCCESS [1:46.522s]
[INFO] Apache Axis2 - tool - Java2WSDL Maven Plugin .. SUCCESS [1:31.054s]
[INFO] Apache Axis2 - tool - MAR Maven Plugin  SUCCESS [50.607s]
[INFO] Apache Axis2 Simple HTTP server Maven