Elango Valluvan

Greenhorn
+ Follow
since May 02, 2005
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Elango Valluvan

I had an existing webservice that was running. There was a method that returned a value object. I went ahead and updated the value object with few more attributes. The updated webservice has now got a new wsdl.

I noticed that the users who were using old client jar to access th old webservice are still not affected. How the webservice response is compatible (modified) to fit into the old client jar users?
16 years ago
I have a WLI application. I have a build script to build that project. I am building it using wlwBuild task. When I run the build script, I am getting this following error.

[wlwBuild] Error occurred during initialization of VM
[wlwBuild] java.lang.Error: java.lang.ClassNotFoundException: workshop.core.AppClassLoader

In the serverclasspath, I have the jar ${weblogic.home}/workshop/wlw-ide.jar. Though, I am getting this error. But when I set the classpath through command prompt (set classpath command) to point wlw-ide.jar, the build script is working fine. Its really strange and I could not figure out why it is not picking up the jar when it is in the serverclasspath of the wlwBuild task.

Is this error due to any other issue? Need your help.


Thanks in advance.
Elango
17 years ago
We found the cause for this issue. This kind of scenario will happen if the clustered environment (where the queue is created) is not stable.

Thought of sharing the solution for future references.
17 years ago
I also found in my queue listener's log the following exception stack trace.

weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.jms.client.JMSConnection.jmsPeerGone(JMSConnection.java:908)
at weblogic.jms.dispatcher.DispatcherWrapperState.peerGone(DispatcherWrapperState.java:691)
at weblogic.jms.dispatcher.DispatcherWrapperState.callback(DispatcherWrapperState.java:552)
at weblogic.rjvm.RJVMImpl$HeartbeatMonitorListenerDeliverer.execute(RJVMImpl.java:1412)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


Is this exception related in any way to the above stated issue?
17 years ago
We have created a queue in a cluster. We have an application that listens to a queue. Messages from another application will post message into this queue which is inturn picked up by the listener process.

We posted a message to the queue long back.But it was not picked up by the application. Then, again we sent two more messages. These recent two messages were picked up by the application.

We looked into the queue using QueueBrowse program from weblogic samples. The program "sometimes" shows that the first message (which was not picked up) is still there in the queue. Sometimes, it shows that there is no message in the queue.

Could any of you help me on this?
Have you faced any such scenarios earlier?

Thanks in advance.
Elango
17 years ago
I have a WLI application which is triggered by a timer. I am migrating the application to J2EE application (removing the jpd..). Is there any way that I can use the same weblogic timer to trigger my J2EE application?
17 years ago
Thanks a lot for your reply.

I very well know that the special characters when used in content portion will be converted to its equivalent entity references.

I think you have misunderstood my question. The change from '<' to '&1t;' is not happening in the data portion (or content portion). It is happening at the element tag (i.e. at <batch_document> tag). Strange...right??

The '<' character in the start element tag is converted to '&1t;' making the whole xml document completely invalid.

I am using weblogic workshop for development. The code that creates the xml document goes like this ...

BatchDocumentDocument bDoc= BatchDocumentDocument.Factory.newInstance();
BatchDocument bd= bDoc.addNewBatchDocument();
...
..

System.out.println(bDoc.toString());

The print statement prints the xml message as

&1t;batch_document> ----> change happens here in the element tag
....
..
</batch_document>

Note: I have used 1 instead of l in the text 'lt;' because the forum displays it as '<'.


[ March 15, 2006: Message edited by: Elango SV ]
[ March 15, 2006: Message edited by: Elango SV ]
18 years ago
Using the .xsd files provided to me, I created XMLBeans using the schema project in weblogic 8.1 sp2. (I am using "xbean.jar" of BEA)

These XMLBeans are used to create a XML document in my Weblogic Integration process. The values in the xml document are retrieved from a database (which cannot administered/viewed by me). XML document was formed perfectly. But recently when I tried running the application again, I found that the xml is not created properly.

When I tried to print the xml message, it displays the xml message with the first letter changed from '<' to '&1t;'.

eg.
<batch_document>
.....
...
</batch_document> is displayed as

&1t;batch_document>
...
..
</batch_document>


What may be the reason behind this change. Is it possible because of some invalid data from the backend? If so, what could be the data?
Is there any special characters which when inserted between the elements makes the document like this?

I would be grateful even if I am answered with any of these questions.

Thanks in advance.
[ March 14, 2006: Message edited by: Elango SV ]
18 years ago