ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Definition file problem with Toolkit 7.0.0.2

Post new topic  Reply to topic
 Message Definition file problem with Toolkit 7.0.0.2 « View previous topic :: View next topic » 
Author Message
next
PostPosted: Tue Mar 01, 2011 6:17 am    Post subject: Message Definition file problem with Toolkit 7.0.0.2 Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

We have a message definition file created from a xsd, which works fine with toolkit 6.0. But when we import the message set into toolkit 7.0. It is giving compilation error.

It doesnt say anything particular about the error. But it just says "An internal error occurred"

I validated the xsd with XMLSpy and it is valid.

We are using toolkit 7.0.0. I upgraded to 7.0.0.2. But still we are facing the same issue.

I am not sure how to proceed. Any help is appreciated


Last edited by next on Tue Mar 01, 2011 6:30 am; edited 1 time in total
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Mar 01, 2011 6:24 am    Post subject: Re: Message Definition file problem Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

next wrote:
I am not sure how to proceed. Any help is appreciated


Does it work if you simply import the xsd into v7? (i.e. is it a problem with the message set or the xsd)

Have you checked the migration guide v6.0 -> v7 for any actions needed?

Does it just say "an internal error has occured" or is that surrounded by any other text?

Have you got a PMR open?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
next
PostPosted: Tue Mar 01, 2011 6:40 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

Yes . It works fine if i just import into the toolkit V7.

It says "An internal error occurred. Perform a full build or contact IBM support center "

I did check out the forums. But Could not find anything specific to this problem

We are yet to raise a PMR.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Mar 01, 2011 6:40 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

I've found that for a few of our message sets it is simnpler to re-import the XSD's again rather than trying the migration from 6.1 to 7.0.0.x

I do get the same error that you are seeing with the migration. Doing the 'create message definition from XSD' process seems to sort everything out.
It appears that those that fail have associated deployable WSDL's are well as the message definiitons.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
next
PostPosted: Tue Mar 01, 2011 6:45 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

I did try that option, still i am getting the same error.

And also, when i try to open the message definition file with the message definition editor, it gives a "Java.lang.NullPointerException "
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Mar 01, 2011 7:12 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Have you tried the

New
Clean
Empty
Workspace
Trick?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
next
PostPosted: Tue Mar 01, 2011 7:29 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

Yes
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Mar 01, 2011 7:35 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Then its PMR time methinks.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
next
PostPosted: Tue Mar 01, 2011 8:27 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

I fixed it.

There was an empty Import tag which was causing the issue.

<xsd:import/>

When i removed it. It was fine. But when i validated it with It was fine with XMLSpy
Back to top
View user's profile Send private message
next
PostPosted: Tue Mar 01, 2011 8:28 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

Thank you all for your suggestions and advice
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Mar 01, 2011 12:53 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

next wrote:
I fixed it.

There was an empty Import tag which was causing the issue.

<xsd:import/>


Did this show up as a warning under V6.1.0.x?
I've seen this type of thing before.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
next
PostPosted: Wed Mar 02, 2011 2:25 am    Post subject: Reply with quote

Voyager

Joined: 02 May 2010
Posts: 75

I am not sure about 6.1 since we are using 6.0 still.

In 6.0 it doesnt show any warnings.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Mar 02, 2011 2:55 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

next wrote:
I am not sure about 6.1 since we are using 6.0 still.

In 6.0 it doesnt show any warnings.


6.0 goes out of support in two months.

Upgrade really soon now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Definition file problem with Toolkit 7.0.0.2
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.