[
https://issues.apache.org/jira/browse/AXIS2-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518174
]
Davanum Srinivas commented on AXIS2-3093:
-----------------------------------------
Appreciate the enthusiasm :) Please try the release candidate artifacts:
http://people.apache.org/~deepal/axis2/1.3/
thanks,
dims
> axis2server.sh, wsdl2java.sh, java2wsdl.sh unusable without logging
> -------------------------------------------------------------------
>
> Key: AXIS2-3093
> URL: https://issues.apache.org/jira/browse/AXIS2-3093
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Upul Godage
> Fix For: nightly
>
> Attachments: log4j.properties.patch.jar
>
>
> I ran a sample without following all the instructions. Check out the present
> behavior. It does not say anything. Check the output after adding the
> patch.jar to the lib directory.
> If this is a minor issue, then it seems new users will have a second opinion
> when something goes wrong like this. This is a sure way to keep the new
> users away from Axis2. Without logs, troubleshooting problems is
> unthinkable. Imagine someone asking in the user list something like this.
> Most will not bother finding what's going on. They will go for something
> else.
> Attached log4j.properties.patch.jar can be added to the AXIS2_HOME/lib folder
> to fix the issue as quick fix for the moment. Jar contains log4j.properties
> file only. So when it is added to the classpath, log4j will see the
> properties file and initialize the logging system. This is a simple solution
> to fix all the scripts and samples at the moment.
> Present behaviour:
> --------------------
> [EMAIL PROTECTED]:~/apps/axis2/bin$ bash axis2server.sh
> Using AXIS2_HOME: /home/upul/apps/axis2
> Using JAVA_HOME: /usr/java
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.transport.http.SimpleHTTPServer).
> log4j:WARN Please initialize the log4j system properly.
> [SimpleAxisServer] Using the Axis2 Repository/home/upul/apps/axis2/repository
> [SimpleAxisServer] Using the Axis2 Configuration
> File/home/upul/apps/axis2/conf/axis2.xml
> [JAM] Warning: You are running under a pre-1.5 JDK. JSR175-style source
> annotations will not be available
> [SimpleAxisServer] Started
> [SimpleHTTPServer] Stop called
> with the fix:
> ------------------
> [EMAIL PROTECTED]:~/apps/axis2/bin$ bash axis2server.sh
> Using AXIS2_HOME: /home/upul/apps/axis2
> Using JAVA_HOME: /usr/java
> [INFO] [SimpleAxisServer] Starting
> [INFO] [SimpleAxisServer] Using the Axis2
> Repository/home/upul/apps/axis2/repository
> [SimpleAxisServer] Using the Axis2 Repository/home/upul/apps/axis2/repository
> [SimpleAxisServer] Using the Axis2 Configuration
> File/home/upul/apps/axis2/conf/axis2.xml
> [INFO] Deploying module: ping-1.3
> [INFO] Deploying module: addressing-1.3
> [INFO] Deploying module: soapmonitor-1.3
> [INFO] Deploying module: sample-logging
> [INFO] Deploying module: metadataExchange-1.3
> [INFO] Deploying module: script-1.3
> [INFO] Deploying module: sample-logging
> [INFO] script module activated
> [JAM] Warning: You are running under a pre-1.5 JDK. JSR175-style source
> annotations will not be available
> [INFO] Deploying Web service: sample-MyService.aar
> [ERROR] The sample-MyServiceWithModule.aar service, which is not valid,
> caused Did not find the desired phase 'loggingPhase' while deploying handler
> 'InFlowLogHandler'.
> org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase
> 'loggingPhase' while deploying handler 'InFlowLogHandler'.
> at
> org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:76)
> at
> org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToFlow(PhaseResolver.java:64)
> at
> org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:100)
> at
> org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:106)
> at
> org.apache.axis2.description.AxisOperation.onEngage(AxisOperation.java:158)
> at
> org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:458)
> at
> org.apache.axis2.description.AxisService.onEngage(AxisService.java:687)
> at
> org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:458)
> at
> org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:421)
> at
> org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:526)
> at
> org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:473)
> at
> org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:571)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:141)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:318)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:220)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:118)
> at
> org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:146)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180)
> at
> org.apache.axis2.transport.SimpleAxis2Server.<init>(SimpleAxis2Server.java:50)
> at
> org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.java:101)
> [INFO] org.apache.axis2.deployment.DeploymentException: Did not find the
> desired phase 'loggingPhase' while deploying handler 'InFlowLogHandler'.
> [INFO] Deploying Web service: sample-WsaMappingService.aar
> [INFO] [SimpleAxisServer] Started
> [SimpleAxisServer] Started
> [INFO] Listening on port 8080
> [SimpleHTTPServer] Stop called
> [INFO] Shut down connection listener
> [INFO] Shut down HTTP processors
> [INFO] HTTP protocol handler shut down
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
