ramanika kollareddy

Hi all,

I am using bytesmessages in a queue in UTF-8 format. partial code snippet:

BytesMessage bytesMessage = session.createBytesMessage(); bytesMessage.writeBytes( message.getBytes( "UTF-8" ) );

In the mdb onMessage(), I am getting EOFException at ByteMessage.readUTF().

Any help is appreciated.

Thank you in advance.

Hi

Couple of quick questions:

1) Is there a way to have security common to soap and simple rest style http requests at the servlet level? like using an interface that has authenciation/authorization methods. Also can servlet filters be used instead?

2) how to generate the security tokens and store them. Is there a tool that can be used for this?

Any pointers to examples are highly appreciated.

Thanks in advance for your time.

Yes. the http client requests are simple http requests passing xml.

Few more questions:

1) Is HTTP Basic Authentication useful/fast in case of thousands and thousands of client requests per second?

2) Is there any other mechanism to deal with high volume requests? How about the cases where the client requests without user credentials still need to be processed and thus pass the security mechanism?

3) Also is http basic authentication be used with weblogic server?

Thanks in advance.

Hi

Thank you for the prompt reply.

I am new to webservices and security.
I need to do authentication and authorization but the client requests might not always contain the user credentials information.

I am not sure about your question about SOAP stack. We have a axis based webservice generated from an existing pojo.

The SOAP clients uses dot-net to access this webservice.
The http clients use direct http url that we provide for the client requests.

I am not sure what type of security authentication and authorization to proceed with and whether to implement it at weblogic server or use spring or any other techology.

Any more pointers and useful information in terms of books, methodologies, technologies and examples would be highly appreciated.

Thanks in advance.

Hi all,

I am new to security area.

I have a requirement to add security to webservices in a J2EE application where the clients are other applications. My application handles pure http and soap requests that need security. The application runs on weblogic and Spring is used for autowiring the components.

I have done some research and leaning towards PKI approach. But not sure as how and where to implement it.

Any pointers to the examples, current security trends/patterns and preferable techologies would be highly appreciated.

Thanks a lot in advance.

Hi all,

I have a requirement to add security to webservices in a J2EE application where the clients are other applications. The application handles pure http and soap requests that need security. The application runs on weblogic and Spring is used for autowiring the components.

I am leaning towards PKI approach. But not sure as how to implement it.

Any pointers to the examples and preferable techologies would be highly appreciated.

Thanks a lot in advance.

Hi all,

I would like to simulate a production enviornment test for a day. Thus I would like to introduce think time and number of requests in my loadrunner test.
I am using a java code vuser script and set the vusers to run as threads.

I did a sample test with 200 vusers ramping up and running for 40 minutes. The vuser script also takes into account the various think times at various times.

When I looked at the vuser log files, I noticed that the total number of requests/load runner iterations issued are more than the total requests that I want to simulate.

So my question is - Is there a way to limit the loadrunner iterations/requests issued by each vuser to those that I want?
Example - I need only 150 requests to come in at a given time and a different number of requests coming in at a different time in a given test duration.

Your valuable input at the earliest is highly appreciated.

Thanks a bunch in advance.

Hi all,


We are doing pre-production testing aganist a weblogic version 9.2 cluster with several nodes on each of 3 machines. Whenever a new ear is deployed with no cluster restart, the application performance degrades quickly and drastically over time. But if the cluster is restarted before a new ear is started or made active...the application performance is better.

But in the case of a non-clustered enviornment, we observed that the application server does not need a restart after every a new ear deployment.

So the questions are:
- Does the weblogic cluster need to be restarted for every new deployment?
- Is there any other setting that is missing in the cluster setup??

Your valuable input and time is highly appreciated.

Thanks in advance.