[JBossWS] - Re: Help! Call Web service error!
by lixun
Thank you Peter, you give me some instructions! But I don't think my classpath error!
In my windows platform, Jboss 4.2.2 runs OK!
But Jboss 4.2.3 and Jboss 5.0.* runs error!
Follow your instruction, I add option -verbose:gc to JAVA_OPTS in run.bat, and I find following information in server.log:
sun.boot.class.path=D:\jboss\lib\endorsed\activation.jar;D:\jboss\lib\endorsed\jaxb-api.jar;D:\jboss\lib\endorsed\jbossws-native-jaxws-ext.jar;D:\jboss\lib\endorsed\jbossws-native-jaxws.jar;D:\jboss\lib\endorsed\jbossws-native-saaj.jar;D:\jboss\lib\endorsed\resolver.jar;D:\jboss\lib\endorsed\serializer.jar;D:\jboss\lib\endorsed\stax-api.jar;D:\jboss\lib\endorsed\xalan.jar;D:\jboss\lib\endorsed\xercesImpl.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_04\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_04\jre\classes
I think all is OK!
Can you find sth wrong! Peter?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231463#4231463
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231463
17 years, 2 months
[JBoss Cache: Core Edition] - Re: optimal storage parameters for cache node?
by java.mastro
Dear Member,
I do faced the same problem some time back.
Right now i can not give the statistics that you requested. But will let you know the work around(s) and
follow if it suits for you.
solution 1
--------------
Instead of keeping 10,000 key value attributes under a single node,
put your all key value pairs in a hash map and keep this hash map in the node.
As effect the jboss cache will have only one node under a node. In this way jboss cache overhead will be
eliminated and will give you the more performance in start up of jboss cache and reading the contents of it.
One side effect of jboss cache is that, as the size of the node increases the performance of cache start up and persisting the updates will be affected.
solution 2
------------
do segmentation using hashing Instead of putting all key value pairs under a single node.
What i mean to say is that, as your key is a long, Apply some kind of hashing so that, for any given number you will get the hash code between 0 to 9.
now distribute your key value pairs under different nodes as below.
if /x/y/z is your node under which you are placing attributes, after segmentation it will be
/x/y/z/0 - some key value pairs
/x/y/z/1 - some key value pairs
...
/x/y/z/9 - some key value pairs
performance wise there wont be any diff between depth of 3 and 4 if your are having values only at the leaf node.
Please note that, using database persistence for a node with MBs of data will be too slow and chances of failures are more. BJDBC is preferred in such cases.
hope your requirement satisfied
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231459#4231459
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231459
17 years, 2 months
[JNDI/Naming/Network] - Re: distributed application
by vphagura
Code where the exception happens is on the 'return line where the cast is:
public FlightReservationAccessorRemote getFlightReservationAccessorRemote() throws NamingException
| {
| return (FlightReservationAccessorRemote)fetchRemoteObject( "flightReservationAccessorRemote", "FlightReservationAccessorBean" );
| }
Lookup is done here:
private Object fetchRemoteObject(String key, String clsName ) throws NamingException
| {
| Object ret = null;
| if( cache.containsKey( key ))
| {
| ret = cache.get( key );
| log.info( "Got it from CACHE..." );
| }
| else
| {
| if( ctx != null )
| {
| log.info(clsName );
| ret = ctx.lookup( "reservation/" + clsName + "/remote");
| if( ret != null )
| {
| cache.put( key, ret );
| }
| }
| }
| return ret;
| }
Here is the full JNDIView listing from 'Global JNDI Namespace'
+- UserTransactionSessionFactory (proxy: $Proxy103 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
| +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
| +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
| +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
| +- topic (class: org.jnp.interfaces.NamingContext)
| +- reservation (class: org.jnp.interfaces.NamingContext)
| | +- FlightReservationAccessorBean (class: org.jnp.interfaces.NamingContext)
| | | +- local (class: Proxy for: com.vsp.reservation.ejb.accessor.FlightReservationAccessor)
| | | +- local-com.vsp.reservation.ejb.accessor.FlightReservationAccessor (class: Proxy for: com.vsp.reservation.ejb.accessor.FlightReservationAccessor)
| | | +- remote (class: Proxy for: com.vsp.reservation.ejb.accessor.FlightReservationAccessorRemote)
| | | +- remote-com.vsp.reservation.ejb.accessor.FlightReservationAccessorRemote (class: Proxy for: com.vsp.reservation.ejb.accessor.FlightReservationAccessorRemote)
| | +- ReservationAccessorBean (class: org.jnp.interfaces.NamingContext)
| | | +- local (class: Proxy for: com.vsp.reservation.ejb.accessor.ReservationAccessor)
| | | +- remote-com.vsp.reservation.ejb.accessor.ReservationAccessorRemote (class: Proxy for: com.vsp.reservation.ejb.accessor.ReservationAccessorRemote)
| | | +- remote (class: Proxy for: com.vsp.reservation.ejb.accessor.ReservationAccessorRemote)
| | | +- local-com.vsp.reservation.ejb.accessor.ReservationAccessor (class: Proxy for: com.vsp.reservation.ejb.accessor.ReservationAccessor)
| | +- CarReservationAccessorBean (class: org.jnp.interfaces.NamingContext)
| | | +- local (class: Proxy for: com.vsp.reservation.ejb.accessor.CarReservationAccessor)
| | | +- local-com.vsp.reservation.ejb.accessor.CarReservationAccessor (class: Proxy for: com.vsp.reservation.ejb.accessor.CarReservationAccessor)
| | | +- remote-com.vsp.reservation.ejb.accessor.CarReservationAccessorRemote (class: Proxy for: com.vsp.reservation.ejb.accessor.CarReservationAccessorRemote)
| | | +- remote (class: Proxy for: com.vsp.reservation.ejb.accessor.CarReservationAccessorRemote)
| | +- HotelReservationAccessorBean (class: org.jnp.interfaces.NamingContext)
| | | +- remote (class: Proxy for: com.vsp.reservation.ejb.accessor.HotelReservationAccessorRemote)
| | | +- remote-com.vsp.reservation.ejb.accessor.HotelReservationAccessorRemote (class: Proxy for: com.vsp.reservation.ejb.accessor.HotelReservationAccessorRemote)
| | +- CustomerAccessorBean (class: org.jnp.interfaces.NamingContext)
| | | +- local (class: Proxy for: com.vsp.reservation.ejb.accessor.CustomerAccessor)
| | | +- local-com.vsp.reservation.ejb.accessor.CustomerAccessor (class: Proxy for: com.vsp.reservation.ejb.accessor.CustomerAccessor)
| | | +- remote-com.vsp.reservation.ejb.accessor.CustomerAccessorRemote (class: Proxy for: com.vsp.reservation.ejb.accessor.CustomerAccessorRemote)
| | | +- remote (class: Proxy for: com.vsp.reservation.ejb.accessor.CustomerAccessorRemote)
| +- persistence.unit:unitName=reservation.ear (class: org.jnp.interfaces.NamingContext)
| | +- reservation.jar#reservation(class: org.hibernate.impl.SessionFactoryImpl)
| +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
| +- ProfileService (class: AOPProxy$0)
| +- queue (class: org.jnp.interfaces.NamingContext)
| | +- DLQ (class: org.jboss.jms.destination.JBossQueue)
| | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue)
| +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
| +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
| +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
| +- jmx (class: org.jnp.interfaces.NamingContext)
| | +- invoker (class: org.jnp.interfaces.NamingContext)
| | | +- RMIAdaptor (proxy: $Proxy98 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
| | +- rmi (class: org.jnp.interfaces.NamingContext)
| | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
| +- TomcatAuthenticators (class: java.util.Properties)
| +- console (class: org.jnp.interfaces.NamingContext)
| | +- PluginManager (proxy: $Proxy100 implements org.jboss.console.manager.PluginManagerMBean (no security manager: RMI class loader disabled))
|
| Here is the Bean and the Remote interface, in case:
|
|
| @Stateless
| | public class FlightReservationAccessorBean implements FlightReservationAccessor, FlightReservationAccessorRemote
| | {
| | @PersistenceContext( unitName="reservation" )
| | EntityManager eMgr;
| |
| | public Integer createFlightResevation( Flight flight ) throws Exception
| | {
| | eMgr.persist( flight );
| | return flight.getFlightId();
| | }
| |
| | public void deleteFlightResevation( Flight flight ) throws Exception
| | {
| | eMgr.remove( flight );
| | }
| |
| | @TransactionAttribute(TransactionAttributeType.NEVER)
| | public Flight findFlightById( Integer id ) throws Exception
| | {
| | return eMgr.find( Flight.class, id );
| | }
| |
| | public void updateFlightResevation( Flight flight ) throws Exception
| | {
| | eMgr.merge( flight );
| | }
| |
| | }
|
| @Remote
| | public interface FlightReservationAccessorRemote extends FlightReservation
| | {
| | }
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231455#4231455
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231455
17 years, 2 months