Home
Forums
New posts
What's new
New posts
Latest activity
Advertise
Resources
Log in
Register
What's new
New posts
Menu
Log in
Register
Install the app
Install
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
UBE Waiting
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="jgersic" data-source="post: 2831" data-attributes="member: 2238"><p>I don't know if this pertains to you, but..At my last employer for a long</p><p>time we had the same problem of UBE's going into a wait state. The only way</p><p>we could get them 'unstuck' was to start/stop the queue service on the</p><p>enterprise server. The unique thing with our setup was that we had two</p><p>enterprise servers, one for crp/dev and one for prod and central objects</p><p>were on the DEV/CRP box (this is because we had never thought we would have</p><p>a second enterprise and when we added it we did not move the objects</p><p>immediately). Anyways, after we moved central objects from the crp/dev box</p><p>to the enterprise box, the issue went away. This was a huge issue for us,</p><p>and we had JDE consultants/advanced technologies, as well as numerous</p><p>business partners and they never figured it out.</p><p> If you have two or more enterprise servers, are your central objects</p><p>residing on your production box? I know this should not make a difference,</p><p>and shouldn't have for us, but it is the only thing that changed in our</p><p>circumstance which leads me to believe maybe there was a communications</p><p>issue between the boxes and it would just timeout (nope, nothing in any logs</p><p>about jdenet timing out)...</p><p> I just bought the JDE complete reference, and they have a section in there</p><p>on troubleshooting, maybe there will be something in there that is new....</p><p></p><p>John</p></blockquote><p></p>
[QUOTE="jgersic, post: 2831, member: 2238"] I don't know if this pertains to you, but..At my last employer for a long time we had the same problem of UBE's going into a wait state. The only way we could get them 'unstuck' was to start/stop the queue service on the enterprise server. The unique thing with our setup was that we had two enterprise servers, one for crp/dev and one for prod and central objects were on the DEV/CRP box (this is because we had never thought we would have a second enterprise and when we added it we did not move the objects immediately). Anyways, after we moved central objects from the crp/dev box to the enterprise box, the issue went away. This was a huge issue for us, and we had JDE consultants/advanced technologies, as well as numerous business partners and they never figured it out. If you have two or more enterprise servers, are your central objects residing on your production box? I know this should not make a difference, and shouldn't have for us, but it is the only thing that changed in our circumstance which leads me to believe maybe there was a communications issue between the boxes and it would just timeout (nope, nothing in any logs about jdenet timing out)... I just bought the JDE complete reference, and they have a section in there on troubleshooting, maybe there will be something in there that is new.... John [/QUOTE]
Verification
Post reply
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
UBE Waiting
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top
