This looks unfamiliar to me : "Bad envelope tag: tr" . Usually I get "Bad envelope tag: br" which is the way PHP formats its errors.

Can you install SOAP UI as described at http://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=Troubleshooting#Verifying_the_Mantis_SOAP_API_using_SOAP_UI and validate that the two listed operations works?

Hi,

The duplicate is 14039... not 14040, curious ?
In fact 14039 has generated an error code at submission.
Then I not found it a few hours later... The new redaction is more concise and includes the error report from Mylyn (I have not located this message as text, the panel content can't be copied)

So I will make now the the test about SOAP UI and install. But the best too should be to swap status between 39 and 40.

I go on quickly

Hi,
Can you tell me which is your hour span between Paris.
I often works late for Paris to have quick exchanges with US or Canada

I wait till status of 39 and 40 should be confirmed

Hi,

I've set the most recent bug as duplicate. I've looked at your screenshots, and it seems that the problem is only related to tagging. I've recently fixed that problem in git, so please use the latest git version ( master-1.2.x branch ) and reopen this report if the problem still happens.

The commit which solved the problem is https://github.com/mantisbt/mantisbt/commit/46ff26ec28a251817c7fff9992efcb3501477655

Hi,
I let in redact mode this tab while you were answering.
I send you the text.
About GIT I don't use it. All soft is SVN managed. May be it is a particular choice. In my knowledge we can use GIT or SVN not both, is-it fully true.
The other choice is to use Bugzilla...

Error loading http:__ld1.mantisbt.trebly.net/api/soap/mantisconnect.php?WSDL: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected character encountered: 'c

Best regard
Trebly

Note: Again I got an answer refused probables because of the presence of an URL into error message, I try again

Hi,

A few minutes after reading, I made the patch.

joined the screenshot : 2012-03-14 09:08 Trebly File Added: ECLIPSE-Myllyn-MantisBT-Submit-error-B20314-1.jpg

is wrong : must be deleted : error in patch

The patch don't changes anything.

Remark about upload of files :
I tried to send you here the file (text and no screenshot) of the full track but the system refuses (test content and refuses without explanation, it could filter and/or escape) the content.
The error has no message to explain which content is refused.
The content of the comment is lost if you have not saved it before submit "add note", may be a tagged file as {ESCAPE_ALL}<content with tags and so on>..... {/ESCAPE_ALL} or {CODE}<content with tags and so on>..... {/CODE} will avoid this no capability to upload such track files and display the content when need as ESCAPED CODE.

Just to make sure we're talking about the same thing. Try a fresh install from https://github.com/mantisbt/mantisbt/zipball/master-1.2.x . It is the most recent unreleased 1.2.x version. This will contain the fixes you need.

Also I'd like to know what PHP Version and what database server ( including version ) you're using. If using SQL server, let me know what driver it is.

I use mysql;
No problem of access an management using the site.
Only SOAP which is used by Mylyn connector generates the problem it is pure SOAP, in my opinion.
My current version was 1.2.9.
I got 1.2.10, I will upgrade and test tomorrow morning (for America hour).

The versions are :

Mysql : 5.5.10
Php : 5.3.6
Apache 2.2.17 DAV/2 mod_ssl/2.2.17 open SSL/0.9.8
SVN 1.6.6

Today :
No change with 1.2.10

Test with SOAP UI : More precise
WSDLException (at /html): faultCode=INVALID_WSDL: Expected element '{http://schemas.xmlsoap.org/wsdl/}definitions'.

It seems that SOAP don't answers what is waited.
Nevertheless with the same URL from mylyn I get all parameters from MantisBT DB to a good editions. It is the submit which fail, thus partially because each submit as previously said generates a task in MantisBT DB.

Hi,
I keep to same status with the error with Mylyn. I imagine maybe that the problem can come from the server MantisBT installation, XML ?.

About my installation (which runs SOAP from others applications) :

1- I have created a local repository on a sever, then access it with Apache. For this everything is OK (I would want nevertheless to install some plugins that I found).

2- Around this subject, with keeping in mind the aim to find the global solution and make it function with Mylyn (a necessity), I looked at plugings management. First I am interested in (Wiki edition, and Markup adaptations particularly), but too, may be I have an installation problem.

So I would want to check up my installation, I have not found specific recommendations from MantisBT, about such installation (I used the Developer documents and the SF doc you have ref first).

To do this, install plugins (may be develop in the future), after looking to the structure of the whole soft, I looked at plugins install. It remains, after several hours of work, a lot of things not completely clear (time to read many things about, what have been done, compatibility, packages, source management etc...).

1- First I have not found how to install the "source plugin" (it seems that there is a loop -an auto-reference - in documentation)

2- Install plugin can be made manually (sources), but I could not found the repository access to download all components of a plugin (which can be packed).

3- Many things seem to be several year old, so I am not sure that what I found is update and 1.2.10 compatible. Where is a synthesis about all plugins and compatibility, I am not sure to have visited.

I am conscious that these questions are farther than the "bug" but if my installation is not right, they are directly linked to.

Thanks for your answer.

Remark :
I don't understand how the above text can get a #2800 error code... when added.
Secondary why after returning and updated page the "add note" button is no more activated. - found : it is possible to submit a new comment to my own comment (suitable if there is a span of time) but this produced #2800 error, after the submit button is inactivated. Then the solution is to edit the previous comment and add new elements. Issue to check.

Paris 9:21 am.
Confirm about the #2800

I wrote this morning :
Hi,

About my organization and the SVN SouceForge choice.

I am working with the Opensource project TikiWiki, so I have repositories (wher I commit into my experimental branches in SourceForge and another local on my Server fro managing my own delopment with external access

Why MantisBT : because when I look up to a task manager, I have preferred widely MantisBT.

About the "bug" (a true one)
I have gone yesterday (last night), to the internal SOAP functions of MantisBT.
I feel now that the may be the origin is that the the error comes from the management of empty data in MantisBT DB from the concerned project (this because I am beginning with a minimum). It is after MantisBT update from Mylyn when MantisBT/SOAP tries to send some data to update the current view from ECLIPSE.
I could put a lot of test to trace when the error is sent (XML empty tag ?), but I don't know the product. It is not the most efficient now.
But this don't answers to the SOAP test issue...

Hi, Rombert

I have no solution till now.

1- the SOAP-UI serves on test the available functions and there is no connection problems
2- The 1.2.10 upgrade don't changes anything

I do believe that the lonely solution should to generate a trace from my MantisBT server.

I could try but has I don't know well the product it will generate a lot of time spend without efficiency and I have others priorities and my job is not done (I have near 50 bugs and enhancements to manage, the reason why for myself I was wishing to use Mantis and more a wiki linked to organized the whole project).

May be you have some patches and/or recommendations to find where the error is generated. If not I don't imagine how to solve this issue.

Best regards

Trebly

Trebly, I have no idea how to troubleshoot your issues from this information. I can take a look at your Mantis instance if you want - just by calling the SOAP API to see if I can find the issue. If you prefer the instance details to be private, notify me by email ( robert.munteanu@gmail.com ).

Hi,

I write private.

Here I can tell about my idea.
When SOAP is run, in my opinion if Xdebug is activated with directing trace to a local file may be I can get something.
The lonely problem (because I don't know the product in details) :
Set the began end trace of xdebug at right optimized places.
For the initialization (default on on my server - development tool) I can easily do it.
You can put them in a pseudo language with a pattern easy to find like //###rombert:xdebug:[begin, end, stop, start].

thanks

Trebly

I've performed some tests using the credentials you sent me. Apparently there is an error in your phpmailer configuration:

phpmailerException: Invalid address: root@localhost in ...\MantisBT\library\phpmailer\class.phpmailer.php on line 462 .

Can you correct this and try again? Also note that the task does get updated in my tests, just that this error comes up.

Hi,

The exception comes from an error in phpmailer the function "ValidateAddress" which returns always false and raises the exception...
May be it is not directly related to the application SMTP parameters (config_inc.php)

I will install a trace.
The problem for this is that I must change optionally a little the session management because the var_dump() and other xdebug informations, written as < pre >, too the exception trace are always cleared (new session) before showing the Mantis page. So the debug of this is not at all easy on user-developer platform without changes.

I use normally ssl with the port defined by my sites and domain host OVH.
Using domain management particular url as these I gave to you, access my local server on which I installed Mantis server.

There is no root@localhost defined anywhere.
I will have to change mail sender name (send the IP) in the message because it is defined into mails by an automatic completely wrong process, it is the local address of the router...
It is a detail I will look at this point.

If I am not successful tomorrow I will try for a while to define a standard smtp.
I have others products which uses the same parameters without problem. I must understand.

trebly

Best regards

note : a problem when submitting a note, I got "double registering", which generates not validated "Add note" and inactivation of the button. Refresh is identical and the "Add Note" button remains not activated. The page need to be closed to submit the note (saved separately) again.

EDIT (dregad) added spaces around html PRE tag to prevent wide page

1. Can you simply try disabling email notifications and see if that fixes the problem? At least we'll know who is to blame.

2. The problem you mention regarding submitting a note, is it related to submissions using SOAP or the web interface?

Any news on this?

Hi,
I have been locked on another problem till now. Not completely ended.

For mail I could not set the parameters in a good way but not only with MantisBT. So I have to write a test soft, or use an existing one. There is a problem on others applications on the server. The OVH documentation is not so clear. I will write a little soft which can allow to change parameters easily and control the mail process. There was no problem before so I need to identify the origin and be able to be quickly sure of the parameter of an installation.

I would know from you, where in the soft I can set a trace soft (it writes data with the help of xdebug functions sometimes) So if you could add into the MantisBT soft (soap module) the targeted points where to get information about soap transactions we could get a file with all is done when sending back information after registering a task.

To write this you have just to add add lines //###writetrac: <data>
If you think that is useful to get several ones with parrallelism you can use :
//###writetrac[tracname]: <data>
All elements of trac have the date+time and are sequenced

These optional "execution reports" are text/plain or html.

I made this so that with soft which must not write nothing to output (ob_) because of no text/html Mime types (as images) I could get targeted traces while the execution with checks (ECLIPSE) can't be always used efficiently or not easily used on a server.

About my note which cancerns execution of MantisBT application of MantisBT site :
This occurs :
1- I redact as now an answering note, I am loggged in when I start, this can take time (because I don't only do this at same time, it can take one hour or more...)

2- When I submit my "note" (Add note) I get a page with "Error, may be you submit twice" (If needed I have screenshot)

3- If I make a "back" (navigator) the page is normal with the note but the button "add note" is disactivated

4- I must reload, this reconnects but the message (note) is then lost (To avoid this I make always a copy on all sites)

5- I re-submit and it is OK

It is quite a bug, a classical cause is a session expiration during redaction. Then the system has to manage a note from an unknown user, incoherent situation, but it reconnects automatically, after... what appends ?, I have the same problem in an opensource larger than Mantis in which I have several roles, a little developer, and we have to solve this problem.
We send an expiration message to propose to save the document, we have an automatic local save, it will be solved (my solution) by a local save before submit followed after reconnect (may be long time after) by a recall you have a pending note... locally saved

The other solution is when a submit occurs to keep the received content and when the error page is reached, test auto-reconnect or ask please reconnect and if successful submit the waiting task (add-note)
Best regards

Trebly

note added by edit : it occurs for this note

Just to confirm, you mentioned two problems:

1. Unable to configure email with Mantis -> errors in the SOAP API
2. Session timeouts when writing -> loss of data

is that correct?

For problem 1 I'd need to know more details about your email settings.
For problem 2 you probably need to see bug 0012492 and other bugs related to it. It's still an open issue for us.

Hi,

Not exactly, 3 problems, one main et two secondary ones :

1- Main SOAP pb main of the thread the error
When I submit a task to MantisBT server (my installation) I get always an answer with
Operation failed : Bad envelope tag: tr
All the transaction goes well, and more the task is recorded into MantisBT

I was talking about the tools to find this bug. I have a lib which is able to make hidden traces (as XDEBUG which I use) but multi process.
I explain the use in my previous note, we could get exactly the SOAP transaction content. But as I explain, I don't know the product so the MantisBT developer should have to send to me some patched *.php with the elements of trace to get.

2- Secondary problems
a- the mail connection, it is a local private problem of system, I have to make test. Before I will disable the mail to avoid screen errors. I have no time to solve this problem for a week
b- the supposed timeout on session during redaction of a note, with data (text) loss. I will look at your refs.

Best regards

Trebly

Regarding 1 - your main problem . I am now convinced that the cause of the SOAP API errors is the the email delivery failure. To help you debug the problem, you can do the following:

1. Set $g_email_send_using_cronjob = ON; in config_inc.php to store emails in the database instead of sending them immediately
2. Periodically execute scripts/send_emails.php to deliver emails

I think that you will get clearer error messages when using scripts/end_emails.php .

I'm also downgrading the priority/severity since this is more or a configuration/integration issue.

Did you manage to try the configuration I suggested to debug/solve your email problems?

Trebly, you did not provide any feedback. I am resolving this issue as "no change required". Feel free to provide the requested feedback at a later time and to reopen the issue.