Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Connecting to Sevice Container

4 posts in General Discussion Last posting was on 2007-12-18 00:29:16.0Z
Klaic Matko Posted on 2007-12-16 20:46:07.0Z
From: "Klaic Matko" <mklaic@foi.hr>
Newsgroups: sybase.public.workspace.general
Subject: Connecting to Sevice Container
Lines: 104
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 78-0-21-56.adsl.net.t-com.hr
X-Original-NNTP-Posting-Host: 78-0-21-56.adsl.net.t-com.hr
Message-ID: <47658e8f$1@forums-1-dub>
Date: 16 Dec 2007 12:46:07 -0800
X-Trace: forums-1-dub 1197837967 78.0.21.56 (16 Dec 2007 12:46:07 -0800)
X-Original-Trace: 16 Dec 2007 12:46:07 -0800, 78-0-21-56.adsl.net.t-com.hr
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:553
Article PK: 1088237

I unable to connect to default Service Container in Worspace(I working on
XP). When i select Connect I get error message:

Could not connect to MyServiceContainer.
Error connecting to the "JMX Server" extension on profile
"MyServiceContainer" (Error: null)

When i select Ping I get this error message:

javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: amd; nested exception
is:
java.net.ConnectException: Connection refused: connect]

at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:92)

at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:98)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at mx4j.connector.rmi.RMIConnector.connect(RMIConnector.java:123)

at
com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:102)

at
com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:163)

at
com.sybase.io.admin.eas.profiles.IOServerConnection.<init>(IOServerConnection.java:61)

at
com.sybase.io.admin.eas.profiles.IOServerConnectionFactory.createConnection(IOServerConnectionFactory.java:31)

at
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:76)

at
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:60)

at
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:298)

at
com.sybase.stf.servers.internal.ui.actions.PingAction$PingJob.run(PingAction.java:127)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

Caused by: java.rmi.ConnectException: Connection refused to host: amd;
nested exception is:
java.net.ConnectException: Connection refused: connect

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)

at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)

at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)

at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)

at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)

at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:88)

... 12 more

Caused by: java.net.ConnectException: Connection refused: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)

at java.net.Socket.connect(Socket.java:452)

at java.net.Socket.connect(Socket.java:402)

at java.net.Socket.<init>(Socket.java:309)

at java.net.Socket.<init>(Socket.java:124)

at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)

at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)

... 17 more




I dont know what to do? Is this group right for this kind of questions?


Samir Nigam Posted on 2007-12-17 19:41:04.0Z
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47658e8f$1@forums-1-dub>
Subject: Re: Connecting to Sevice Container
Lines: 123
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: snigamxp.sybase.com
X-Original-NNTP-Posting-Host: snigamxp.sybase.com
Message-ID: <4766d0d0$1@forums-1-dub>
Date: 17 Dec 2007 11:41:04 -0800
X-Trace: forums-1-dub 1197920464 10.22.85.206 (17 Dec 2007 11:41:04 -0800)
X-Original-Trace: 17 Dec 2007 11:41:04 -0800, snigamxp.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:554
Article PK: 1088234

First, to make sure - how did you start the server?

After you install service container from the WorkSpace Developer Edition
runtimes installer (separate installer from WorkSpace installer), the
service container can be started using Programs|Sybase|WorkSpace|UO|Start UO
shortcut. That should start EAServer, SybAgent, Quartz, and UO runtime DB
processes.

If those servers start up ok, then you should be able to connect using
MyServiceContainer connection profile in WorkSpace.

Regards,
Samir

"Klaic Matko" <mklaic@foi.hr> wrote in message
news:47658e8f$1@forums-1-dub...
>I unable to connect to default Service Container in Worspace(I working on
>XP). When i select Connect I get error message:
>
> Could not connect to MyServiceContainer.
> Error connecting to the "JMX Server" extension on profile
> "MyServiceContainer" (Error: null)
>
> When i select Ping I get this error message:
>
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: amd; nested
> exception is:
> java.net.ConnectException: Connection refused: connect]
>
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:92)
>
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:98)
>
> at javax.naming.InitialContext.lookup(InitialContext.java:347)
>
> at mx4j.connector.rmi.RMIConnector.connect(RMIConnector.java:123)
>
> at
> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:102)
>
> at
> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:163)
>
> at
> com.sybase.io.admin.eas.profiles.IOServerConnection.<init>(IOServerConnection.java:61)
>
> at
> com.sybase.io.admin.eas.profiles.IOServerConnectionFactory.createConnection(IOServerConnectionFactory.java:31)
>
> at
> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:76)
>
> at
> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:60)
>
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:298)
>
> at
> com.sybase.stf.servers.internal.ui.actions.PingAction$PingJob.run(PingAction.java:127)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
>
> Caused by: java.rmi.ConnectException: Connection refused to host: amd;
> nested exception is:
> java.net.ConnectException: Connection refused: connect
>
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
>
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
>
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
>
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
>
> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:88)
>
> ... 12 more
>
> Caused by: java.net.ConnectException: Connection refused: connect
>
> at java.net.PlainSocketImpl.socketConnect(Native Method)
>
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
>
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
>
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
>
> at java.net.Socket.connect(Socket.java:452)
>
> at java.net.Socket.connect(Socket.java:402)
>
> at java.net.Socket.<init>(Socket.java:309)
>
> at java.net.Socket.<init>(Socket.java:124)
>
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
>
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
>
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
>
> ... 17 more
>
>
>
>
> I dont know what to do? Is this group right for this kind of questions?
>
>
>


Klaic Matko Posted on 2007-12-17 21:03:23.0Z
From: "Klaic Matko" <mklaic@foi.hr>
Newsgroups: sybase.public.workspace.general
References: <47658e8f$1@forums-1-dub> <4766d0d0$1@forums-1-dub>
Subject: Re: Connecting to Sevice Container
Lines: 148
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 78-1-31-121.adsl.net.t-com.hr
X-Original-NNTP-Posting-Host: 78-1-31-121.adsl.net.t-com.hr
Message-ID: <4766e41b$1@forums-1-dub>
Date: 17 Dec 2007 13:03:23 -0800
X-Trace: forums-1-dub 1197925403 78.1.31.121 (17 Dec 2007 13:03:23 -0800)
X-Original-Trace: 17 Dec 2007 13:03:23 -0800, 78-1-31-121.adsl.net.t-com.hr
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:555
Article PK: 1088236

Thans for response.

When I click Start UO shortcut I get Windows error message:

Jaguar CTS - Component Transaction Server has encountered a problem and
needs to close. We are sorry for the inconvenience.

Then I clicked on error details. Which said:

AppName: jagsrv.exe AppVer: 5.3.0.16 ModName: msvcrt.dll

ModVer: 7.0.2600.2180 Offset: 000378c0

I there possibility that some Workspace components are not installed well?



Thanks Samir.

Matko

"Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
news:4766d0d0$1@forums-1-dub...
>
> First, to make sure - how did you start the server?
>
> After you install service container from the WorkSpace Developer Edition
> runtimes installer (separate installer from WorkSpace installer), the
> service container can be started using Programs|Sybase|WorkSpace|UO|Start
> UO shortcut. That should start EAServer, SybAgent, Quartz, and UO runtime
> DB processes.
>
> If those servers start up ok, then you should be able to connect using
> MyServiceContainer connection profile in WorkSpace.
>
> Regards,
> Samir
>
> "Klaic Matko" <mklaic@foi.hr> wrote in message
> news:47658e8f$1@forums-1-dub...
>>I unable to connect to default Service Container in Worspace(I working on
>>XP). When i select Connect I get error message:
>>
>> Could not connect to MyServiceContainer.
>> Error connecting to the "JMX Server" extension on profile
>> "MyServiceContainer" (Error: null)
>>
>> When i select Ping I get this error message:
>>
>> javax.naming.ServiceUnavailableException [Root exception is
>> java.rmi.ConnectException: Connection refused to host: amd; nested
>> exception is:
>> java.net.ConnectException: Connection refused: connect]
>>
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:92)
>>
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:98)
>>
>> at javax.naming.InitialContext.lookup(InitialContext.java:347)
>>
>> at mx4j.connector.rmi.RMIConnector.connect(RMIConnector.java:123)
>>
>> at
>> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:102)
>>
>> at
>> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:163)
>>
>> at
>> com.sybase.io.admin.eas.profiles.IOServerConnection.<init>(IOServerConnection.java:61)
>>
>> at
>> com.sybase.io.admin.eas.profiles.IOServerConnectionFactory.createConnection(IOServerConnectionFactory.java:31)
>>
>> at
>> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:76)
>>
>> at
>> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:60)
>>
>> at
>> org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:298)
>>
>> at
>> com.sybase.stf.servers.internal.ui.actions.PingAction$PingJob.run(PingAction.java:127)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
>>
>> Caused by: java.rmi.ConnectException: Connection refused to host: amd;
>> nested exception is:
>> java.net.ConnectException: Connection refused: connect
>>
>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
>>
>> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
>>
>> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
>>
>> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
>>
>> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>>
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:88)
>>
>> ... 12 more
>>
>> Caused by: java.net.ConnectException: Connection refused: connect
>>
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>
>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
>>
>> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
>>
>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
>>
>> at java.net.Socket.connect(Socket.java:452)
>>
>> at java.net.Socket.connect(Socket.java:402)
>>
>> at java.net.Socket.<init>(Socket.java:309)
>>
>> at java.net.Socket.<init>(Socket.java:124)
>>
>> at
>> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
>>
>> at
>> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
>>
>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
>>
>> ... 17 more
>>
>>
>>
>>
>> I dont know what to do? Is this group right for this kind of questions?
>>
>>
>>
>
>


Samir Nigam Posted on 2007-12-18 00:29:16.0Z
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47658e8f$1@forums-1-dub> <4766d0d0$1@forums-1-dub> <4766e41b$1@forums-1-dub>
Subject: Re: Connecting to Sevice Container
Lines: 167
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: snigamxp.sybase.com
X-Original-NNTP-Posting-Host: snigamxp.sybase.com
Message-ID: <4767145c$1@forums-1-dub>
Date: 17 Dec 2007 16:29:16 -0800
X-Trace: forums-1-dub 1197937756 10.22.85.206 (17 Dec 2007 16:29:16 -0800)
X-Original-Trace: 17 Dec 2007 16:29:16 -0800, snigamxp.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:556
Article PK: 1088240

Matko,

Have you looked in the Jaguar startup/boot log files (in EAServer\bin
directory) for clues? I am just guessing - sometimes the server doesn't
start when there is a problem with the hostname or port; sometimes path is
the problem.

This generally requires someone to work with you to get all the details. The
best option would be to call Sybase tech. support and get them to look into
it.

Regards,
Samir

"Klaic Matko" <mklaic@foi.hr> wrote in message
news:4766e41b$1@forums-1-dub...
> Thans for response.
>
> When I click Start UO shortcut I get Windows error message:
>
> Jaguar CTS - Component Transaction Server has encountered a problem and
> needs to close. We are sorry for the inconvenience.
>
> Then I clicked on error details. Which said:
>
> AppName: jagsrv.exe AppVer: 5.3.0.16 ModName: msvcrt.dll
>
> ModVer: 7.0.2600.2180 Offset: 000378c0
>
> I there possibility that some Workspace components are not installed well?
>
>
>
> Thanks Samir.
>
> Matko
>
> "Samir Nigam" <samir_dot_nigam@sybase.com> wrote in message
> news:4766d0d0$1@forums-1-dub...
>>
>> First, to make sure - how did you start the server?
>>
>> After you install service container from the WorkSpace Developer Edition
>> runtimes installer (separate installer from WorkSpace installer), the
>> service container can be started using Programs|Sybase|WorkSpace|UO|Start
>> UO shortcut. That should start EAServer, SybAgent, Quartz, and UO runtime
>> DB processes.
>>
>> If those servers start up ok, then you should be able to connect using
>> MyServiceContainer connection profile in WorkSpace.
>>
>> Regards,
>> Samir
>>
>> "Klaic Matko" <mklaic@foi.hr> wrote in message
>> news:47658e8f$1@forums-1-dub...
>>>I unable to connect to default Service Container in Worspace(I working on
>>>XP). When i select Connect I get error message:
>>>
>>> Could not connect to MyServiceContainer.
>>> Error connecting to the "JMX Server" extension on profile
>>> "MyServiceContainer" (Error: null)
>>>
>>> When i select Ping I get this error message:
>>>
>>> javax.naming.ServiceUnavailableException [Root exception is
>>> java.rmi.ConnectException: Connection refused to host: amd; nested
>>> exception is:
>>> java.net.ConnectException: Connection refused: connect]
>>>
>>> at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:92)
>>>
>>> at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:98)
>>>
>>> at javax.naming.InitialContext.lookup(InitialContext.java:347)
>>>
>>> at mx4j.connector.rmi.RMIConnector.connect(RMIConnector.java:123)
>>>
>>> at
>>> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:102)
>>>
>>> at
>>> com.sybase.management.jmx.util.MX4JRMIConnectorServerLocator.getMBeanServer(MX4JRMIConnectorServerLocator.java:163)
>>>
>>> at
>>> com.sybase.io.admin.eas.profiles.IOServerConnection.<init>(IOServerConnection.java:61)
>>>
>>> at
>>> com.sybase.io.admin.eas.profiles.IOServerConnectionFactory.createConnection(IOServerConnectionFactory.java:31)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:76)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:60)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:298)
>>>
>>> at
>>> com.sybase.stf.servers.internal.ui.actions.PingAction$PingJob.run(PingAction.java:127)
>>>
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
>>>
>>> Caused by: java.rmi.ConnectException: Connection refused to host: amd;
>>> nested exception is:
>>> java.net.ConnectException: Connection refused: connect
>>>
>>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
>>>
>>> at
>>> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
>>>
>>> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
>>>
>>> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
>>>
>>> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>>>
>>> at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:88)
>>>
>>> ... 12 more
>>>
>>> Caused by: java.net.ConnectException: Connection refused: connect
>>>
>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>>
>>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
>>>
>>> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
>>>
>>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
>>>
>>> at java.net.Socket.connect(Socket.java:452)
>>>
>>> at java.net.Socket.connect(Socket.java:402)
>>>
>>> at java.net.Socket.<init>(Socket.java:309)
>>>
>>> at java.net.Socket.<init>(Socket.java:124)
>>>
>>> at
>>> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
>>>
>>> at
>>> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
>>>
>>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
>>>
>>> ... 17 more
>>>
>>>
>>>
>>>
>>> I dont know what to do? Is this group right for this kind of questions?
>>>
>>>
>>>
>>
>>
>
>