i need the help in the following issues, which stoped my work.
i have written java service and trying to compile it, and it is giving me following
error while running the service. Actually when the java service is save it will
compile the java code, but at run time it is saying need to recompile the code.
The error is like this…
Could not run “Myservice”.
Com.wn.app.b2b.server.ServiceException:[ISS.0026.9102]
Service ‘Test.JavaServices:Myservice’ is not operational. To run this service,
first recompile the java source.
How get solve this…
here is information regarding Java from “About Page” from integration server…
webMethods Integration Server
Version 6.1
Updates IS_6-1_FP2
IS_6-1_SP1
TNS_6-1_Fix15
Build Number 132
SSL Strong (128-bit)
Server Environment
Java Version 1.3.1 (46.0)
Java Vendor IBM Corporation
Java Home C:\Program Files\webMethods6\IntegrationServer\jvm
Java Classpath C:\Program Files\webMethods6\IntegrationServer\jvm\lib\rt.jar
C:\Program Files\webMethods6\IntegrationServer\jvm\lib\i18n.jar
C:\Program Files\webMethods6\IntegrationServer\lib\proxy.jar
Try setting this in your extended settings of you IS.It worked for me
watt.serever.compile=c:<the> {0} -d {1}{2}
watt.server.compile.unicode=c:<path> -encoding Unicode
I had no problems upgrading to the Sun 1.4.2 JVM from IBM’s 1.3.1 on Windows 2000 Server. There’s a discussion of this topic in an earlier thread from this forum: [url=“wmusers.com”]wmusers.com
I basically just installed the new JVM, shut down the IS and modified the Windows batch files under the Integration Server directory (server.bat, jcode.bat, etc.) to point to the new JVM directories. You can restart the IS and go to the “About” page to verify which JVM version you’re now running.
Actually, i installed J2RE 1.4.2_10 in another directory like C:\Program Files\Java\JRE1.4.2_10 and then i copied that JRE1.4.2_10 to C:\Program Files\webMethods6\IntegrationServer\jvm\j2re1.4.2_10
Here is the About Page after Upgrading to SUN 1.4.2_10 JVM.
Product webMethods Integration Server
Version 6.1
Updates IS_6-1_FP2
IS_6-1_SP1
TNS_6-1_Fix15
Build Number 132
SSL Strong (128-bit)
Server Environment
Java Version 1.4.2_10 (48.0)
Java Vendor Sun Microsystems Inc.
Java Home C:\Program Files\webMethods6\IntegrationServer\jvm\j2re1.4.2_10
Java Classpath C:\Program Files\webMethods6\IntegrationServer\jvm\j2re1.4.2_10\lib\rt.jar
C:\Program Files\webMethods6\IntegrationServer\jvm\j2re1.4.2_10\lib\i18n.jar
C:\Program Files\webMethods6\IntegrationServer\lib\proxy.jar
Hi all
Here me again, i m getting now very peculiar problem.
i m connected to SQL SERVER 2000 Database and i have created 4 JDBC Connections to that SQL SERVER 2000 in which 2 are connected to “x” Database and 2 are connected to “Y” database.
Now the problem which i m getting is , i can able to enable the connection to “x” databse it is working fine and when i try to enable the both the connections related to “y” Database, i m getting following error…
Error encountered
[ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource HHCGPIntegration.AdapterConnection:GP_CustonInsert_Invoice_Conn.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
[ADA.1.204] Cannot connect to the database with DataSource class “com.microsoft.jdbcx.sqlserver.SQLServerDataSource”.
[Microsoft][SQLServer 2000 Driver for JDBC]Unsupported VM encoding Cp1256.
what is this error… and y i m not getting for other 2 connections. because recently i have upgraded my JVM From IBM’s 1.3.0 TO Sun 1.4.2_10
The error messages seems to indicate that your JDBC driver is having a problem with the character collation (Cp1256) in use by your JVM or in use by the database. Is it possible that the second database uses a different charset collation than the first? If so, this might explain why some connections work and others do not.
Check for available updates for your JDBC driver that might address this or use a JDBC driver from another vendor such as the open source jTDS driver that works with SQL Server.
Hi Mark,
Thanks a Lot for help. Things got solved. Yeah it was the problem of JVM , Actually i upgrade my JVM from 1.3.1 TO 1.4.2_10. and later i upgrade my JDBC Drivers, and things going fine.