Re: Problem with instant deployment
But i had this working before and it's working on a linux box might
this minute. This xp machine I had working before until I started
trying to do custom deployment with wsdd files
jayachandra wrote:
Looks like we have a very interesting scenario here. If I
recollect correct, axis engine inside a jvm is a *singleton* and to
serve Service1 it might be existing as a singleton with serverside flag
set to true inside Tomcat JVM, and since inside your Service1 you try
to access the engine code as if like a client side client is trying to
call Service2, axis might be failing.
Axis can't be blamed for this either, for its an SOA framework
where client is assumed to be located in a seperate JVM. So I'd suggest
that don't try to invoke the Service2 methods via an axis client call
mechanism but rather import the corresponding Service2SoapBindingImpl
into your Service1SoapBindingImpl class and do a direct method call,
unless you want to truly *experiment* and find something for yourself
as a case study.
HTH,
Jaya
On 12/14/05, Frank <[EMAIL PROTECTED]> wrote:
Well
I've narrowed it down and it is a server problem but I'm not sure how
to fix it.
Service 1 and service 2 both work fine if called from a client or a
browser. Service 1 calls service 2 and that's where it stops and
returns to the client that useless exception. The server code has a
try catch around that call but produces nothing in the server log.
This except code works on another machine and I had it working on here
earlier. All I can figure is it's some config etc thing. The tubs are
compiled and in the \webapps\axis\WEB-INF\classes unjared.
Any thoughts?
Thanks,
Frank
jayachandra wrote:
Totally agree with Ron,
have a peep into catalina_home/logs and I bet 70% of the
time we'll know what to do.
Jaya
On 12/14/05, Ron Reynolds <[EMAIL PROTECTED]
> wrote:
errors in Axis are actually
logged (in some cases) at the DEBUG level. also make sure the request
is hitting your server (check your $TOMCAT_HOME/logs/ directory for
most recent catalina, localhost and access logs). there was a posting
earlier that sounded like the Axis engine never came up - if that's the
case check the localhost log as that's where the problem will be
logged.
in all cases where i got a
very generic error on the client it was a server-side error that had
somehow been "dumbed down" to a generic error, so that's why i
suggested checking the server-side logs.
.ron. (tho you can
call me "roy") ;-)
-
Original Message -
From:
De Graef Luc
To:
'axis-user@ws.apache.org'
Sent:
Tuesday, December 13, 2005 10:37 PM
Subject:
RE: Problem with instant deployment
Hello,
in the message 'Server.UserException /
InvocationTargetException with a new webs ervice', I described
approximately the same scenario, let's say the same output. I am also
working with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it
really is a server related issue, and that we need to check the server
logging output. It seems however that I don't have any logging, not
even with a log4j.properties file containing following info :
# Set root category priority to
INFO and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level,
# Must be one of ("trace", "debug", "info",
"warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL
and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL,
CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set to be a ConsoleAppender using
a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n
# LOGFILE is set to be a File appender using a
PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r
[%t] %-5p %c %x
Re: Problem with instant deployment
Looks like we have a very interesting scenario here. If I recollect correct, axis engine inside a jvm is a *singleton* and to serve Service1 it might be existing as a singleton with serverside flag set to true inside Tomcat JVM, and since inside your Service1 you try to access the engine code as if like a client side client is trying to call Service2, axis might be failing.
Axis can't be blamed for this either, for its an SOA framework where client is assumed to be located in a seperate JVM. So I'd suggest that don't try to invoke the Service2 methods via an axis client call mechanism but rather import the corresponding Service2SoapBindingImpl into your Service1SoapBindingImpl class and do a direct method call, unless you want to truly *experiment* and find something for yourself as a case study.
HTH,
Jaya
On 12/14/05, Frank <[EMAIL PROTECTED]> wrote:
Well I've narrowed it down and it is a server problem but I'm not sure how to fix it.Service 1 and service 2 both work fine if called from a client or a browser. Service 1 calls service 2 and that's where it stops and returns to the client that useless exception. The server code has a try catch around that call but produces nothing in the server log. This except code works on another machine and I had it working on here earlier. All I can figure is it's some config etc thing. The tubs are compiled and in the \webapps\axis\WEB-INF\classes unjared.
Any thoughts?Thanks,Frank
jayachandra wrote:
Totally agree with Ron,
have a peep into catalina_home/logs and I bet 70% of the time we'll know what to do.
Jaya
On 12/14/05, Ron Reynolds <[EMAIL PROTECTED]
> wrote:
errors in Axis are actually logged (in some cases) at the DEBUG level. also make sure the request is hitting your server (check your $TOMCAT_HOME/logs/ directory for most recent catalina, localhost and access logs). there was a posting earlier that sounded like the Axis engine never came up - if that's the case check the localhost log as that's where the problem will be logged.
in all cases where i got a very generic error on the client it was a server-side error that had somehow been "dumbed down" to a generic error, so that's why i suggested checking the server-side logs.
.ron. (tho you can call me "roy") ;-)
- Original Message -
From:
De Graef Luc
To:
'axis-user@ws.apache.org'
Sent: Tuesday, December 13, 2005 10:37 PM
Subject: RE: Problem with instant deployment
Hello,
in the message 'Server.UserException / InvocationTargetException with a new webs ervice', I described approximately the same scenario, let's say the same output. I am also working with Tomcat 5.0.28 but with Axis
1.3 .
A suggestion from Roy Reynolds was that it really is a server related issue, and that we need to check the server logging output. It seems however that I don't have any logging, not even with a log4j.properties
file containing following info :
# Set root category priority to INFO and its only appender to CONSOLE. log4j.rootCategory=INFO, CONSOLE, LOGFILE #log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level, # Must be one of ("trace", "debug", "info", "warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL and its only appender to CONSOLE. log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n # LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.Threshold=TRACE log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-Original Message- From: Frank [mailto:[EMAIL PROTECTED]
] Sent: woensdag 14 december 2005 0:51 To: axis Subject: Problem with instant deployment
Been using axis a little bit hear but still have lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on XP ). First I had this working with instant deployment before, now I get the following exception:
Caused by: AxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: jav
Re: Problem with instant deployment
Well I've narrowed it down and it is a server problem but I'm not sure
how to fix it.
Service 1 and service 2 both work fine if called from a client or a
browser. Service 1 calls service 2 and that's where it stops and
returns to the client that useless exception. The server code has a
try catch around that call but produces nothing in the server log.
This except code works on another machine and I had it working on here
earlier. All I can figure is it's some config etc thing. The tubs are
compiled and in the \webapps\axis\WEB-INF\classes unjared.
Any thoughts?
Thanks,
Frank
jayachandra wrote:
Totally agree with Ron,
have a peep into catalina_home/logs and I bet 70% of the time
we'll know what to do.
Jaya
On 12/14/05, Ron Reynolds <[EMAIL PROTECTED]> wrote:
errors in Axis are actually logged
(in some cases) at the DEBUG level. also make sure the request is
hitting your server (check your $TOMCAT_HOME/logs/ directory for most
recent catalina, localhost and access logs). there was a posting
earlier that sounded like the Axis engine never came up - if that's the
case check the localhost log as that's where the problem will be
logged.
in all cases where i got a very
generic error on the client it was a server-side error that had somehow
been "dumbed down" to a generic error, so that's why i suggested
checking the server-side logs.
.ron. (tho you can
call me "roy") ;-)
-
Original Message -
From:
De Graef Luc
To:
'axis-user@ws.apache.org'
Sent:
Tuesday, December 13, 2005 10:37 PM
Subject:
RE: Problem with instant deployment
Hello,
in the message 'Server.UserException /
InvocationTargetException with a new webs ervice', I described
approximately the same scenario, let's say the same output. I am also
working with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it
really is a server related issue, and that we need to check the server
logging output. It seems however that I don't have any logging, not
even with a log4j.properties file containing following info :
# Set root category priority to INFO
and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level,
# Must be one of ("trace", "debug", "info",
"warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL
and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL,
CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set to be a ConsoleAppender using
a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n
# LOGFILE is set to be a File appender using a
PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r
[%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-----Original Message-
From: Frank [mailto:[EMAIL PROTECTED]
]
Sent: woensdag 14 december 2005 0:51
To: axis
Subject: Problem with instant deployment
Been using axis a little bit hear but still
have lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b.
on XP ). First I had this working with instant deployment before, now
I get the following exception:
Caused by:
AxisFault
faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/
}stackTrace:java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement
(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.pars
Re: Problem with instant deployment
Ron,
I think your onto something here. Looking at the trace closer I
traced it through the service code. It appears to have stopped when it
tries to call the other service. Now service 1 calls service 2, service
2 needs the stubs generated from wsdl2java. I compiled those stubs.
Now first would not service 1 fail to start/compile if it could not
find the service 2 stubs? I have them @ webapps\axis\WEB-INF\classes
and have it un jared as I saw some posts that if you jar it and have it
in the path you might have problems and on other machines that's also
how I have it working .
I can hit that service on the server with
axis/OMS.jws?method=callObjectManager and it appears to be working (did
not pass doc but appears to be running).
Any thoughts?
Thanks,
Frank
Ron Reynolds wrote:
RE: Problem with instant deployment
errors in Axis are actually logged
(in some cases) at the DEBUG level. also make sure the request is
hitting your server (check your $TOMCAT_HOME/logs/ directory for most
recent catalina, localhost and access logs). there was a posting
earlier that sounded like the Axis engine never came up - if that's the
case check the localhost log as that's where the problem will be logged.
in all cases where i got a very
generic error on the client it was a server-side error that had somehow
been "dumbed down" to a generic error, so that's why i suggested
checking the server-side logs.
.ron. (tho you can call
me "roy") ;-)
-
Original Message -
From:
De Graef Luc
To:
'axis-user@ws.apache.org'
Sent:
Tuesday, December 13, 2005 10:37 PM
Subject:
RE: Problem with instant deployment
Hello,
in the message 'Server.UserException /
InvocationTargetException with a new webs ervice', I described
approximately the same scenario, let's say the same output. I am also
working with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it
really is a server related issue, and that we need to check the server
logging output. It seems however that I don't have any logging, not
even with a log4j.properties file containing following info :
# Set root category priority to INFO and
its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level,
# Must be one of ("trace", "debug", "info",
"warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL
and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL,
CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set to be a ConsoleAppender using
a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n
# LOGFILE is set to be a File appender using a
PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r
[%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-Original Message-----
From: Frank [mailto:[EMAIL PROTECTED]]
Sent: woensdag 14 december 2005 0:51
To: axis
Subject: Problem with instant deployment
Been using axis a little bit hear but still have
lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on
XP ). First I had this working with instant deployment before, now I
get the following exception:
Caused by:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(U
Re: Problem with instant deployment
' is OK.
TLS: ... finding input doc
... found 1
TLS: duplicating input doc
TLS: input doc set to the following:
<_flow-tags_ debug="1134564719">
SFGPEVU-US-
TLS: Processing request
De Graef Luc wrote:
RE: Problem with instant deployment
Hello,
in the message 'Server.UserException /
InvocationTargetException with a new webs ervice', I described
approximately the same scenario, let's say the same output. I am also
working with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it really
is a server related issue, and that we need to check the server logging
output. It seems however that I don't have any logging, not even with a
log4j.properties file containing following info :
# Set root category priority to INFO and
its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level,
# Must be one of ("trace", "debug", "info",
"warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL
and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL,
CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set to be a ConsoleAppender using
a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n
# LOGFILE is set to be a File appender using a
PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r
[%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-Original Message-
From: Frank [mailto:[EMAIL PROTECTED]]
Sent: woensdag 14 december 2005 0:51
To: axis
Subject: Problem with instant deployment
Been using axis a little bit hear but still have
lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on
XP ). First I had this working with instant deployment before, now I
get the following exception:
Caused by:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown
Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at
org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at
org.apache.axis.client.Call.invoke(Call.java:2748)
at
org.apache.axis.client.Call.invoke(Call.java:2424)
at
org.apache.axis.client.Call.invoke(Call.java:2347)
at
org.apache.axis.client.Call.invoke(Call.java:1804)
at
frankpc.axis.TLS_jws.TLSSoapBindingStub.callTrustedLabeler(TLSSoapBindingStub.java:103)
at
csds.service
Re: Problem with instant deployment
Totally agree with Ron,
have a peep into catalina_home/logs and I bet 70% of the time we'll know what to do.
Jaya
On 12/14/05, Ron Reynolds <[EMAIL PROTECTED]> wrote:
errors in Axis are actually logged (in some cases) at the DEBUG level. also make sure the request is hitting your server (check your $TOMCAT_HOME/logs/ directory for most recent catalina, localhost and access logs). there was a posting earlier that sounded like the Axis engine never came up - if that's the case check the localhost log as that's where the problem will be logged.
in all cases where i got a very generic error on the client it was a server-side error that had somehow been "dumbed down" to a generic error, so that's why i suggested checking the server-side logs.
.ron. (tho you can call me "roy") ;-)
- Original Message -
From:
De Graef Luc
To: 'axis-user@ws.apache.org'
Sent: Tuesday, December 13, 2005 10:37 PM
Subject: RE: Problem with instant deployment
Hello,
in the message 'Server.UserException / InvocationTargetException with a new webs ervice', I described approximately the same scenario, let's say the same output. I am also working with Tomcat 5.0.28 but with Axis
1.3 .
A suggestion from Roy Reynolds was that it really is a server related issue, and that we need to check the server logging output. It seems however that I don't have any logging, not even with a log4j.properties
file containing following info :
# Set root category priority to INFO and its only appender to CONSOLE. log4j.rootCategory=INFO, CONSOLE, LOGFILE #log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level, # Must be one of ("trace", "debug", "info", "warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL and its only appender to CONSOLE. log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=-
%m%n # LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.Threshold=TRACE log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-Original Message- From: Frank [mailto:[EMAIL PROTECTED]
] Sent: woensdag 14 december 2005 0:51 To: axis Subject: Problem with instant deployment
Been using axis a little bit hear but still have lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on XP ). First I had this working with instant deployment before, now I get the following exception:
Caused by: AxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.reflect.InvocationTargetException faultActor:
faultNode: faultDetail: {http://xml.apache.org/axis/
}stackTrace:java.lang.reflect.InvocationTargetException at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.apache.axis.message.SOAPFaultBuilder.endElement
(SOAPFaultBuilder.java:128) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.xerces.parsers.AbstractSAXParser.endElement
(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.axis.encoding.DeserializationContext.parse
(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClien
Re: Problem with instant deployment
Title: RE: Problem with instant deployment
errors in Axis are actually logged (in some cases)
at the DEBUG level. also make sure the request is hitting your server
(check your $TOMCAT_HOME/logs/ directory for most recent catalina, localhost and
access logs). there was a posting earlier that sounded like the Axis
engine never came up - if that's the case check the localhost log as that's
where the problem will be logged.
in all cases where i got a very generic error on
the client it was a server-side error that had somehow been "dumbed down" to a
generic error, so that's why i suggested checking the server-side
logs.
.ron. (tho you can call me "roy")
;-)
- Original Message -
From:
De Graef Luc
To: 'axis-user@ws.apache.org'
Sent: Tuesday, December 13, 2005 10:37
PM
Subject: RE: Problem with instant
deployment
Hello,
in the message 'Server.UserException /
InvocationTargetException with a new webs ervice', I described
approximately the same scenario, let's say the same output. I am also working
with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it really is a
server related issue, and that we need to check the server logging output. It
seems however that I don't have any logging, not even with a log4j.properties
file containing following info :
# Set root category
priority to INFO and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail
level, #
Must be one of ("trace", "debug", "info", "warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the
enterprise logger category to FATAL and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set
to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
# LOGFILE is set
to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x -
%m%n
Do you have some output at server side ?
Regards
Luc
-----Original Message- From: Frank
[mailto:[EMAIL PROTECTED]]
Sent: woensdag 14 december 2005 0:51 To: axis Subject: Problem with instant
deployment
Been using axis a little bit hear but still have lots to
learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on XP ).
First I had this working with instant deployment before, now I get the
following exception:
Caused by: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode: faultString: java.lang.reflect.InvocationTargetException
faultActor: faultNode:
faultDetail: {http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source) at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
javax.xml.parsers.SAXParser.parse(Unknown Source) at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at
org.apache.axis.Message.getSOAPEnvelope(Message.java:424) at
org.apache.axis.handlers.soap.MustUnde
RE: Problem with instant deployment
Title: RE: Problem with instant deployment
Hello,
in the message 'Server.UserException / InvocationTargetException with a new webs ervice', I described approximately the same scenario, let's say the same output. I am also working with Tomcat 5.0.28 but with Axis 1.3 .
A suggestion from Roy Reynolds was that it really is a server related issue, and that we need to check the server logging output. It seems however that I don't have any logging, not even with a log4j.properties file containing following info :
# Set root category priority to INFO and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
#log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Logging detail level,
# Must be one of ("trace", "debug", "info", "warn", "error", or "fatal").
org.apache.commons.logging.simplelog.defaultlog=trace
# Set the enterprise logger category to FATAL and its only appender to CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE
log4j.logger.org.apache=INFO, CONSOLE, LOGFILE
# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
# LOGFILE is set to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=axis.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=TRACE
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
Do you have some output at server side ?
Regards
Luc
-Original Message-
From: Frank [mailto:[EMAIL PROTECTED]]
Sent: woensdag 14 december 2005 0:51
To: axis
Subject: Problem with instant deployment
Been using axis a little bit hear but still have lots to learn. Need some help here (Using tomcat 5.0.28 Axis 1.2b. on XP ). First I had this working with instant deployment before, now I get the following exception:
Caused by:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at frankpc.axis.TLS_jws.TLSSoapBindingStub.callTrustedLabeler(TLSSoapBindingStub.java:103)
at csds.servicecall.AxisTlService.callService(AxisTlService.java:53)
at csds.servicecall.TlService.callService(TlService.java:100)
at csds.servicecall.ServiceCall.callTls(ServiceCall.java:71)
at csds.InterceptDDSMsgs.InterceptDDSMsgs.<init>(InterceptDDSMsgs.java:138)
at csds.InterceptDDSMsgs.RunDDSIntercept.main(RunDDSIntercept.java:23)
{http://xml.apache.org/axis/}hostname:FRANKPC
java.lang.reflect.InvocationTargetException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
Problem with instant deployment
Been using axis a little bit hear but still have lots to learn. Need
some help here (Using tomcat 5.0.28 Axis 1.2b. on XP ). First I had
this working with instant deployment before, now I get the following
exception:
Caused by:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
frankpc.axis.TLS_jws.TLSSoapBindingStub.callTrustedLabeler(TLSSoapBindingStub.java:103)
at csds.servicecall.AxisTlService.callService(AxisTlService.java:53)
at csds.servicecall.TlService.callService(TlService.java:100)
at csds.servicecall.ServiceCall.callTls(ServiceCall.java:71)
at
csds.InterceptDDSMsgs.InterceptDDSMsgs.(InterceptDDSMsgs.java:138)
at
csds.InterceptDDSMsgs.RunDDSIntercept.main(RunDDSIntercept.java:23)
{http://xml.apache.org/axis/}hostname:FRANKPC
java.lang.reflect.InvocationTargetException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
frankpc.axis.TLS_jws.TLSSoapBindingStub.callTrustedLabeler(TLSSoapBindingStub.java:103)
at csds.servicecall.AxisTlService.callService(AxisTlService.java:53)
at csds.servicecall.TlService.callService(TlService.java:100)
at csds.servicecall.ServiceCall.callTls(ServiceCall.java:71)
at
csds.InterceptDDSMsgs.InterceptDDSMsgs.(InterceptDDSMsgs.java:138)
at
csds.InterceptDDSMsgs.RunDDSIntercept.main(RunDDSIntercept.java:23)
I found similar problems with people on the net but tried them and
nothing helped. What I did after getting instant deployment to w
