You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by Samisa Abeysinghe <sa...@yahoo.com> on 2004/08/02 05:59:50 UTC

Client failed to load parser lib - axiscpp.conf location changed

I spent several hours struglling to get the client working as it was complaining 
"Exception : DLOPEN FAILED in loading parser library"

I checked and rechecked the settings on my systems several times but they were correct.

Looking into the code, I found that the location of axiscpp.conf has been changed from
$AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf

I am not sure if this change was informed to the mailing list (to my knowlege, I did not see any
message).
However, if you get problems running the client, please check this.

Thanks,
Samisa...


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail

Re: Client failed to load parser lib - axiscpp.conf location changed

Posted by Samisa Abeysinghe <sa...@yahoo.com>.

Hi Damitha,
    I hardly use deploy_apache2.sh (or deploy_apache.sh) as I less often use the server side.
    I usually only use the client side (as per my requirement), and often with my own custom
settings. 

    However, this kind of a change (like introducing a new folder) should have been informed over
the mailing list, as there can be many who do not use the default settings like me. It is ok to
use 'etc' but only if I new, it could have saved my time.

    Thanks for the reply.
Regards,
Samisa...

--- damitha kumarage <da...@opensource.lk> wrote:

> Hi Samisa,
> When installing axiscpp.conf is copied into $AXISCPP_DEPLOY/etc
> by the installer. And this place is correctly located by the engine
> by use of $AXISCPP_DEPLOY env.
> So there is nothing to do manually to locate axiscpp.conf.
> You may be copying the files in the older way.
> Anyway when you run $AXISCPP_DEPLOY/bin/deploy_apache2.sh if it can't
> find axiscpp.conf it complains like this
> 
>  cannot stat `../etc/axiscpp.conf_linux': No such file or directory
> 
> thanks
> damitha
> 
> On Mon, 2004-08-02 at 09:59, Samisa Abeysinghe wrote:
> > I spent several hours struglling to get the client working as it was complaining 
> > "Exception : DLOPEN FAILED in loading parser library"
> > 
> > I checked and rechecked the settings on my systems several times but they were correct.
> > 
> > Looking into the code, I found that the location of axiscpp.conf has been changed from
> > $AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf
> > 
> > I am not sure if this change was informed to the mailing list (to my knowlege, I did not see
> any
> > message).
> > However, if you get problems running the client, please check this.
> > 
> > Thanks,
> > Samisa...
> > 
> > 
> > 		
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Address AutoComplete - You start. We finish.
> > http://promotions.yahoo.com/new_mail
> > 
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Re: Client failed to load parser lib - axiscpp.conf location changed

Posted by damitha kumarage <da...@opensource.lk>.

Hi Samisa,
When installing axiscpp.conf is copied into $AXISCPP_DEPLOY/etc
by the installer. And this place is correctly located by the engine
by use of $AXISCPP_DEPLOY env.
So there is nothing to do manually to locate axiscpp.conf.
You may be copying the files in the older way.
Anyway when you run $AXISCPP_DEPLOY/bin/deploy_apache2.sh if it can't
find axiscpp.conf it complains like this

 cannot stat `../etc/axiscpp.conf_linux': No such file or directory

thanks
damitha

On Mon, 2004-08-02 at 09:59, Samisa Abeysinghe wrote:
> I spent several hours struglling to get the client working as it was complaining 
> "Exception : DLOPEN FAILED in loading parser library"
> 
> I checked and rechecked the settings on my systems several times but they were correct.
> 
> Looking into the code, I found that the location of axiscpp.conf has been changed from
> $AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf
> 
> I am not sure if this change was informed to the mailing list (to my knowlege, I did not see any
> message).
> However, if you get problems running the client, please check this.
> 
> Thanks,
> Samisa...
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We finish.
> http://promotions.yahoo.com/new_mail
>

Re: Client crashes with both transports

Posted by Samisa Abeysinghe <sa...@yahoo.com>.

OK, I found the solution:
SoapSerializer::releaseBufferCallBack has been removed from the serializer.
Hence it makes no sence to use m_pReleaseBufferCallback anymore.

(Yes I remeber that I saw a email thread on removal of buffering: Cool)

Now I have a question, who should (or does) delete the passed pointer to sendBytes?

Also, would it be not nice to update all the codes when applying a patch? (Or at lease use
depricate option in place; please) 

PS: I did not touch the serializer code to fix this rather only the LibWWW trasport code.
I cannot still get the other trasport (axis transport i.e.) working.

Thanks,
Samisa...

--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> I have been working on the LibWWW trasport to ensure thread safety.
> 
> I was able to get my updates working with the cvs checkout I got on 27th.
> However, when I tried the same with the latest cvs this morning, I saw the client was crashing.
> 
> The point of crash is 
>  0x40153185 in LibWWWTransport::sendBytes(char const*, void const*) (this=0x8059be8,
>     pcSendBuffer=0x4007a0e0 "<?xml version='1.0' encoding='utf-8' ?>", pBufferid=0x8059b98) at
> LibWWWTransport.cpp:133
> 
> where it calls:
> m_pReleaseBufferCallback(pcSendBuffer, pBufferid);
> 
> I tested the client with Axis trasport as well, that too fails to work.
> 
> I doubt the latest changes to SoapSerializer class would have caused the problems.
> I am desperate to finish off the LibWWW related work. But this bug is a bloker.
> Please help fix this.
> 
> Thanks,
> Samisa...
> 
> 
> 
> 	
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail 
> 

__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

Client crashes with both transports

Posted by Samisa Abeysinghe <sa...@yahoo.com>.

I have been working on the LibWWW trasport to ensure thread safety.

I was able to get my updates working with the cvs checkout I got on 27th.
However, when I tried the same with the latest cvs this morning, I saw the client was crashing.

The point of crash is 
 0x40153185 in LibWWWTransport::sendBytes(char const*, void const*) (this=0x8059be8,
    pcSendBuffer=0x4007a0e0 "<?xml version='1.0' encoding='utf-8' ?>", pBufferid=0x8059b98) at
LibWWWTransport.cpp:133

where it calls:
m_pReleaseBufferCallback(pcSendBuffer, pBufferid);

I tested the client with Axis trasport as well, that too fails to work.

I doubt the latest changes to SoapSerializer class would have caused the problems.
I am desperate to finish off the LibWWW related work. But this bug is a bloker.
Please help fix this.

Thanks,
Samisa...



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail